[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-7902:
--------------------------------------
The main difference is probably that for non .war, the shared metadata will not get added.
But did you really need it in the first place ? Right now, it likely does a lot more than
what you need (default and JSP servlets, JSF, zillions of mime mappings, welcome files,
session config). Personally, I think you could use that opportunity to design your own
shared metadata that should be used for your specialized WS webapps (if you really need
anything), and that you could define programmatically.
So you actually only need some context params ?
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