[JBoss-dev] [Nukes Development] - Re: Understanding JSP module changes

[cooper <nu...@jb...>]

here is what I did :

It is possible now to embed a nukes-web.xml in a war. The goal is to intercept calls made to the war and decorated it with Nukes.

If a war is deployed, this must be done after nukes.ear is deployed, so it is a good idea to put it in the nukes directory. This is because war are deployed before ear. In the future we will switch nukes.ear to nukes.sar and it will work in the deploy directory.

It is possible to intercept whatever you want, you have to use the syntax :


  | <?xml version="1.0"?>
  | <!DOCTYPE nukes-web PUBLIC "-//JBoss//DTD Nukes Web 1.0//EN" "http://www.jboss.org/nukes/nukes-web_1_0.dtd">
  | <nukes-web>
  |    <nukes-mapping>
  |       <url-pattern>*.jsp</url-pattern>
  |       <servlet-name>MyServlet</servler-name>
  |    </nukes-mapping>
  | </nukes-web>
  | 

The problem is that the sessions are not shared, unless you put that in the same war the Nukes servlet are. This is how JSPWiki is integrated in Nukes.

In the future, we will use war to have Nukes components with a nukes.xml that will be located in the war. This will allow :


  | * a clean separation between resources (pictures, etc...) and code (class files)
  | * the possibility to dispatch view to JSP with a request dispatcher, it could be the same for nukes templates, something like :
  | 
  |   | page.getRequestDispatcher("/module.tpl/details").include(page);
  |   | 
  | 

I am ready to make the changes but I would need some help to morph the existing packages. Of course that would require a good amount of changes in the codebase (deployment stuff mostly).

Do you think I should add that feature soon and modify all existing stuff, or should we wait until 1.x are done ? Jae, Sherman, I need your position on that. 

<a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3825053#3825053">View the original post</a>

<a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3825053>Reply to the post</a>