Hi Alessio,
today I was investigating why our JBWS-1792 test is failing on JBoss
AS 4.2.3
(see e.g.:
http://jbws.dyndns.org:8180/hudson/job/Native-Core-AS-4.2.3/29/testReport/)
I discovered, that this problem is caused by your commit in JBoss AS
4.2.3 branch:
Index:
src/main/org/jboss/wsf/container/jboss42/JSEArchiveMetaDataAdapter.java
===================================================================
---
src/main/org/jboss/wsf/container/jboss42/JSEArchiveMetaDataAdapter.java
(revision 68729)
+++
src/main/org/jboss/wsf/container/jboss42/JSEArchiveMetaDataAdapter.java
(revision 68730)
@@ -81,6 +81,11 @@
webMetaData.setServletClassNames(getServletClassMap(wmd));
webMetaData.setConfigName(wmd.getConfigName());
webMetaData.setConfigFile(wmd.getConfigFile());
+ Map contextParams = wmd.getContextParams();
+ if (contextParams.containsKey("jbossws-config-name"))
+
webMetaData.setConfigName((String)contextParams.get("jbossws-config-name"));
+ if (contextParams.containsKey("jbossws-config-file"))
+
webMetaData.setConfigFile((String)contextParams.get("jbossws-config-file"));
webMetaData.setSecurityDomain(wmd.getSecurityDomain());
webMetaData.setPublishLocationAdapter(getPublishLocationAdpater(wmd));
webMetaData.setSecurityMetaData(getSecurityMetaData(wmd.getSecurityContraints()));
I created conditional statement there to do this stuff for JAX-WS
endpoints only on JBoss AS 4.2.3.
However this needs further investigation and allows JAX-RPC endpoints to
work properly
on JBoss AS 4.2.3 as well with your fix.
Just for your information this JAX-RPC test passes on JBoss AS 5.0.0.
--
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat
Mobile: +420 731 186 942
Mail: ropalka(a)redhat.com