Next steps in the JSP saga?

[sgwood]

Juilen,

I have been working on getting my JSP based module packaged and deployed. The only way I can get it to work right now is to have everything - JSPs and supporting code - in the nukes.ear. As I said in a previous post, a WAR in a module EAR doesn't work for context changing reasons. Module JSPs deployed into an exploded nukes.ear/war cannot access classes etc in the module EAR.

I gather from recent postings you are working in this area. Has your thinking changed lately on the approach? Is there something you want to try out?

Thanks,


Sherman

[julien1]

I am working on having nukes.xml in a war/WEB-INF abd have module use a request dispatcher to these JSP.

Is that good for you ?

[sgwood]

Having the request dispatcher forwarding to JSPs in a module EAR/WAR is fine. There is some of this already in the code base. Is there much more to do?

Also, what about:

* Sharing sessions between nukes.ear and the module EARs

* A standard way to package the module WAR and EAR so that the JSPs work.

* What is the context root for the module WAR? And thus, what is the URL for a JSP in a module WAR?

Thanks,


Sherman