[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBAS-7902:
---------------------------------------
JBossWS has a deployer that add data to the context params of JBossWebMetaData. You moved
the jbosswebmetadata processing to the SharedJBossWebMetaDataDeployer which had a check on
the deployed archive filename extension that early returned for non-war archives.
Considering you can have ".jar" with ws endpoints, for which we ask jbossweb to
create a web app... our adds on JBossWebMetaData context params were not picked up
anymore. At least this is my analysis.
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