[jboss-user] [JBossWS] - Re: Specify WS-Security Handler using JEE standards

2009-04-17 Thread ivlcic
I've been looking for the same sollution and found this workaround: I replaced standard client conf with secure one so everything in your app will be under WS-Security. (If you dont need everything encrypted use the wiki instructions) Write your own "endpoint-config" and place it in war META-

[jboss-user] [JBossWS] - Re: Specify WS-Security Handler using JEE standards

2009-03-27 Thread alessio.sold...@jboss.com
"vdurbha" wrote : But the server side endpoint still does not work if I use @HandlerChain annotation instead of @EndpointConfig to set the security handler. After digging into the source code of JBossWS and the log files for a few hours, I understood that for the WS-Security handler to work corr

[jboss-user] [JBossWS] - Re: Specify WS-Security Handler using JEE standards

2009-03-06 Thread vdurbha
After trying various options, I finally figured out a way to write a completely generic client by removing the StubExt dependency. This was achieved by using the @HandlerChain annotation on the Service class. This may also work if we use the annotation on the SEI. And then I defined the handler