[
https://jira.jboss.org/jira/browse/JBAS-6865?page=com.atlassian.jira.plug...
]
Remy Maucherat resolved JBAS-6865.
----------------------------------
Fix Version/s: JBossAS-6.0.0.M2
Resolution: Rejected
Servlet 3.0 provides many pluggability options (ServletContainerInitializer, etc) that
give the library access to the ServletContext. OTOH, attemping to mix the application and
the JBoss deployers looks like a bad proposition to me, they are run before the
application exists in the Servlet container (so no Servlet context can be retrieved).
Make the servletcontext and contextpath available to deployers.
---------------------------------------------------------------
Key: JBAS-6865
URL:
https://jira.jboss.org/jira/browse/JBAS-6865
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployers
Environment: JBoss AS5
Reporter: Matt Wringe
Assignee: Remy Maucherat
Fix For: JBossAS-6.0.0.M2
Some deployers may need to access information about deployed web applications. For a
portlet deployer this would mean having to have access to the servletcontext and
contextpath of the deployed web application. This information is not readily available to
deployers right now and requires using some interesting tricks to get at this information
which is stored in an mbean.
To further complicate things, the Tomcat deployer is using the older mbean deployments,
which means that other deployers can't get access to its unit attachments. The
current unit attachments still wouldn't give direct access to the servletcontext so it
would need to be added.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira