Hi, as a general suggestion, I first of all suggest you to try using some more recent
versions of both JBoss AS and JBossWS.
This said:
"timeagentess" wrote :
| anonymous wrote : ERROR [SOAPFaultHelperJAXWS] SOAP request exception
| | javax.xml.ws.addressing.AddressingException: Required element
{http://www.w3.org/2005/08/addressing}Action is missing
| |
| | at
org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.getRequiredHeaderContent(SOAPAddressingPropertiesImpl.java:71)
| | at
org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.readHeaders(SOAPAddressingPropertiesImpl.java:141)
| | at
org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleInbound(WSAddressingServerHandler.java:82)
| | [...]
| |
You get this message because you're using WS-Addressing and the Action header is
missing in your SOAP message. This is not related to WS-Security.
anonymous wrote :
|
@HandlerChain(file="resource://META-INF/standard-jaxws-endpoint-config.xml")
| @EndpointConfig(configName = "Standard WSSecurity Endpoint")
|
Since you're using the standard endpoint configuration, you should try simplifying
your configuration a bit (to better track down what's happening), i.e. remove the
@HandlerChain annotation and forget about the standard-jaxws-endpoint-config.xml file (you
already have the "Standard WSSecurity Endpoint" in the configuration that is
automatically loaded by jbossws).
Regarding this:
anonymous wrote :
| Endpoint {http://localhost:8080/atb}WSTwoServiceBeanPort does not contain operation
meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
|
under which conditions you got this? Try looking at the log and verify the security
handler on server side is configured (the ws-security conf is selected).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161434#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...