4:40 a.m.
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
8:47 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-7902) WS stack context properties not propagated to servlet context
[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Alessio Soldano resolved JBAS-7902.
-----------------------------------
Resolution: Done
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
9:03 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-7902:
--------------------------------------
Me not understand. (translation: Can you explain ?)
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
9:14 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
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
9:22 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
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
9:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
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
3:17 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-7902:
--------------------------------------
It's not very expensive obviously ;) But if you don't need all the config for a
regular webapp, there is now is an opportunity to use a leaner configuration.
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
9:08 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7902) WS stack context properties not propagated to servlet context
[
https://jira.jboss.org/jira/browse/JBAS-7902?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBAS-7902:
---------------------------------------
ok, as a consequence of other development, next version of jbossws-cxf will not need to
add context params to JBossWebMetaData any more
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
5295
days inactive
5296
days old
7 comments
2 participants
participants (2)
-
Alessio Soldano (JIRA) -
Remy Maucherat (JIRA)