While i'm adding the multiple post handler in the standalone-full .xml , i'm getting the error as "value is already set for this injector error".
XML Extract:
<subsystem xmlns="urn:jboss:domain:webservices:1.2">
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
<endpoint-config name="Standard-Endpoint-Config"/>
<endpoint-config name="Recording-Endpoint-Config">
<post-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
<handler name="RecordingHandle_1r" class="org.jboss.ws.common.invocation.RecordingServerHandler_1"/>
<handler name="RecordingHandler_2" class="org.jboss.ws.common.invocation.RecordingServerHandler_2"/>
<handler name="RecordingHandler_3" class="org.jboss.ws.common.invocation.RecordingServerHandler_3"/>
</post-handler-chain>
</endpoint-config>
<client-config name="Standard-Client-Config"/>
</subsystem>
Please suggest what is the structure to add multiple post handlers in standalone-full.xml on eap 6.3
However jboss 5.2 supports the below but not the eap 6.3
<endpoint-config>
<config-name>Standard Endpoint</config-name>
<post-handler-chains>
<javaee:handler-chain>
<javaee:protocol-bindings>##SOAP11_HTTP ##SOAP11_HTTP_MTOM</javaee:protocol-bindings>
<javaee:handler>
<javaee:handler-name>WSSecurity Handler</javaee:handler-name>
<javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
</javaee:handler>
<javaee:handler>
<javaee:handler-name>Recording Handler</javaee:handler-name>
<javaee:handler-class>org.jboss.wsf.framework.invocation.RecordingServerHandler</javaee:handler-class>
</javaee:handler>
<javaee:handler>
<!-- YOUR OWN HANDLERS IN POST CHAIN -->
<javaee:handler-name>Encrypted Request Logger</javaee:handler-name>
<javaee:handler-class>org.dropchop.mpg.ws.RequestLogger</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</post-handler-chains>
</endpoint-config
I suggest you to check with your customer support contact. I think I remember there was a bug affecting this which could be already solved on more recent EAP versions.