Changes to target containers on JBossWS trunk
by Alessio Soldano
Folks,
FYI, I've just committed a bunch of changes to make JBossWS-CXF trunk
consume jbossws-spi 3.0.0-SNAPSHOT and jbossws-common 3.0.0-SNAPSHOT.
The AS720 and WFLY800 integration layers have been updated accordingly
and 5.0.0-SNAPSHOT versions of them are consumed by the stack.
I've also modified the wilfly810 target, which currently uses the
WildFly 8.0.0.CR2 release (will change that to 8.0.0.Final once that's
released too).
Finally, a new wildfly900 target is available: due to the above
mentioned changes to jbossws-spi, the wildfly master is not usable as
is, so for now my fork here can be used:
https://github.com/asoldano/wildfly/commits/jbossws5
Tomorrow I'll update the Hudson instance on jbossws-qa.jboss.org.
Cheers
Alessio
--
Alessio Soldano
Web Service Lead, JBoss
12 years
- 1
- 1
JXM bean, ServerConfig access question
by Rebecca Searls
I'm adding a new property to ServerConfig. I have confirmed that my sample
app works properly. I've hit a snag when adding a test to (https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls)
modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150TestCaseForked.java
The exiting test updates a like property as follows
Attribute attr = new Attribute("WebServiceHost", value);
getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, attr);
On the server side org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer is being
called.
In JBWS2150TestCaseForked I am setting my property in a like manner.
Attribute attr = new Attribute("WebServicePath", value);
getServer().setAttribute(SERVER_CONFIG_OBJECT_NAME, at
However it fails, "WebServicePath" is not found.
This seems to be a JMX bean setup issues.
Any advise as to how to resolve would be appreciated.
12 years
- 3
- 4
- ← Newer
- 1
- Older →