I was using Native for server (EJB) and client (Java SE / jax-ws dipatch mainly) with encryptation but without signing.
Recently, I rewrote just the client with CXF using the same approach (dispatch), but an issue break me!
Without signing, WSS4J (used by CXF for encrypting) didn't set 'wsu:Id' for 'body' tag and Native reject the message (in class RequireTargetableOperation).
Commenting the test where Native require 'wsu:Id' in RequireTargetableOperation makes CXF encrypted message …
[View More]acceptable and correct.
Using signing makes WSS4J set 'wsu:Id' for 'body' tag, so no issues this way.
I don't know if this issue is a CXF (WSS4J) issue or a Native issue, but here seems to be the right place to report.
(CXF 2.2.3 and Native 3.0.5/JBoss 4.2.3 or Native 3.1.2/JBoss 5.1)
Thanks,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252675#4252675
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252675
[View Less]
We use "ConnectionFactory" to create the connection factory which is defined as:
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=ConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends optional-attribute-name="Connector">jboss.messaging:service=…
[View More]Connector,transport=bisocket</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="JNDIBindings">
| <bindings>
| <binding>/ConnectionFactory</binding>
| <binding>/XAConnectionFactory</binding>
| <binding>java:/ConnectionFactory</binding>
| <binding>java:/XAConnectionFactory</binding>
| </bindings>
| </attribute>
| </mbean>
|
Thanks for your quick response.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252665#4252665
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252665
[View Less]