[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBAS-7902:
---------------------------------------
Should we move this to the forum?
Sure, I can most probably solve this differently, but generally speaking it still seems to
me a reasonable and valid use case to have changes to the JBossWebMetaData being
considered regardless of the name of the deployment unit (jbossws is just an example of
dynamic generation of web app during deployment, right?). is that if
(!unit.getSimpleName().endsWith(".war")) saving a lot of time at deployment?
WS stack context properties not propagated to servlet context
-------------------------------------------------------------
Key: JBAS-7902
URL:
https://jira.jboss.org/jira/browse/JBAS-7902
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service, Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: JBossAS-6.0.0.M3
This is a consequence of
http://fisheye.jboss.org/changelog/JBossAS/trunk?cs=103485
JBossWS-CXF stack depends on context params being propagate to servlet context for lazily
loading the bus when the endpoint servlet is initialized. The params are propagate to
jbossweb metadata at deployment time.
--
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