Hi,
i'm used JAX-WS 2.0 for my client so far. The client artifacts are
generated from my WSDL(doc/lit wrapped). My WebService is using the
WS-Security UsernameToken Policy.
It has been working fine so far.
I want to change to JAX-WS 2.1 EA3 at client side and i replaced the
libraries with new ones.
I created again all artifacts and started my client application. But the
WS-Security header isn't added anymore to the outgoing messages. Any
idea what's wrong?
I also see that my SecurityEnvironmentHandler (Callback) isn't called
anymore.
********************************
That's my clientSecurity Policy:
<?xml version="1.0" encoding="UTF-8"?>
<xwss:JAXRPCSecurity xmlns:xwss="
http://java.sun.com/xml/ns/xwss/config">
<xwss:Service conformance="bsp">
<xwss:SecurityConfiguration dumpMessages="false" >
<xwss:UsernameToken digestPassword="false" useNonce="false" />
</xwss:SecurityConfiguration>
</xwss:Service>
<xwss:SecurityEnvironmentHandler>de.cas.eim.SecurityEnvironmentHandler</xwss:SecurityEnvironmentHandler>
</xwss:JAXRPCSecurity>
********************************
That's my client init code:
service = new MyService().getMyServiceHttpPort();
FileInputStream f = new FileInputStream(MyClient.class.getResource("/
clientSecurityPolicy.xml").getFile());
XWSSecurityConfiguration config =
SecurityConfigurationFactory.newXWSSecurityConfiguration(f);
((BindingProvider)service).getRequestContext().put(XWSSecurityConfiguration.MESSAGE_SECURITY_CONFIGURATION,
config);
String echo = service.echo("Test echo");
********************************
That's all i needed to to in JAX-WS 2.0. Why isn't it working with
JAX-WS 2.1 EA anymore?
I would welcome every help. I also added an bug report at
https://jax-ws.dev.java.net/issues/show_bug.cgi?id=139
Cheers,
Ingo
--
CRM Products Development - New Technologies
CAS Software AG
Well informed. Always and everywhere.
www.cas.de