[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37867
]
Christian Schneider commented on SM-811:
I think I have located and solved the problem.
In the jsr181 component I added a line to set the operation in the exchange.
In the jms component I use the endpoint name and the operation to set the soap
action. I am not sure this is exactly right. But something like that should be
in SoapAction.
> servicemix-jms does not set SoapAction property for SOAP jms messages
> -
>
> Key: SM-811
> URL: https://issues.apache.org/activemq/browse/SM-811
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.0, 3.0.1, 3.1
> Environment: Tested with Tibco EMS as jms server and Tibco Business
> works as system providing the service. The error should also occur with
> ActiveMQ.
>Reporter: Christian Schneider
>Priority: Critical
> Attachments: servicemix-jms-sm-811.patch,
> servicemix-jsr181-sm-811.patch
>
>
> When tibco is the client all works well but when tibco implements the service
> it rejects the soap/jms message as it wants the SoapAction jms property to be
> set.
> I have added a dummy SoapAction in StandardProviderProcessor:
> ...
> MessageProducer producer = session.createProducer(destination);
> TextMessage msg = session.createTextMessage();
> NormalizedMessage nm = exchange.getMessage("in");
> fromNMS(nm, msg);
> String soapAction = "default";
> msg.setStringProperty("SoapAction", soapAction);
> ...
> I was able to do a complete request/reply with tibco in this way. Of course
> the "default" SoapAction will only help if my service has only one method.
> From what I see in Tibco the SoapAction should at least contain the method
> name of the service being called.
> The servicemix-jms component should by default set this property to make it
> more compatible with other soap/jms compatible systems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37910
]
Guillaume Nodet commented on SM-811:
Does Tibco really cares about the content of the SoapAction property,
or does it work if you put an empty one "" for example ?
I'd rather put an empty one, until we have full support for SoapActions
(they should be retrieved from the WSDL)
> servicemix-jms does not set SoapAction property for SOAP jms messages
> -
>
> Key: SM-811
> URL: https://issues.apache.org/activemq/browse/SM-811
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.0, 3.0.1, 3.1
> Environment: Tested with Tibco EMS as jms server and Tibco Business
> works as system providing the service. The error should also occur with
> ActiveMQ.
>Reporter: Christian Schneider
>Priority: Critical
> Attachments: servicemix-jms-sm-811.patch,
> servicemix-jsr181-sm-811.patch
>
>
> When tibco is the client all works well but when tibco implements the service
> it rejects the soap/jms message as it wants the SoapAction jms property to be
> set.
> I have added a dummy SoapAction in StandardProviderProcessor:
> ...
> MessageProducer producer = session.createProducer(destination);
> TextMessage msg = session.createTextMessage();
> NormalizedMessage nm = exchange.getMessage("in");
> fromNMS(nm, msg);
> String soapAction = "default";
> msg.setStringProperty("SoapAction", soapAction);
> ...
> I was able to do a complete request/reply with tibco in this way. Of course
> the "default" SoapAction will only help if my service has only one method.
> From what I see in Tibco the SoapAction should at least contain the method
> name of the service being called.
> The servicemix-jms component should by default set this property to make it
> more compatible with other soap/jms compatible systems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37913
]
Christian Schneider commented on SM-811:
Tibco requires this field to be set. The message is rejected if there is no
SoapAction. An empty SoapAction does not work either. Will it hurt to set the
SoapAction?
You can´t really always retrieve the SoapAction from the WSDL. In my case there
is no WSDl as I go from Pojos to Soap. Perhaps the setting from the WSDL could
override the setting derived from the JBI exchange.
BTW. WSDLs from Tibco look different in some cases from those that xfire
generates.
> servicemix-jms does not set SoapAction property for SOAP jms messages
> -
>
> Key: SM-811
> URL: https://issues.apache.org/activemq/browse/SM-811
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.0, 3.0.1, 3.1
> Environment: Tested with Tibco EMS as jms server and Tibco Business
> works as system providing the service. The error should also occur with
> ActiveMQ.
>Reporter: Christian Schneider
>Priority: Critical
> Attachments: servicemix-jms-sm-811.patch,
> servicemix-jsr181-sm-811.patch
>
>
> When tibco is the client all works well but when tibco implements the service
> it rejects the soap/jms message as it wants the SoapAction jms property to be
> set.
> I have added a dummy SoapAction in StandardProviderProcessor:
> ...
> MessageProducer producer = session.createProducer(destination);
> TextMessage msg = session.createTextMessage();
> NormalizedMessage nm = exchange.getMessage("in");
> fromNMS(nm, msg);
> String soapAction = "default";
> msg.setStringProperty("SoapAction", soapAction);
> ...
> I was able to do a complete request/reply with tibco in this way. Of course
> the "default" SoapAction will only help if my service has only one method.
> From what I see in Tibco the SoapAction should at least contain the method
> name of the service being called.
> The servicemix-jms component should by default set this property to make it
> more compatible with other soap/jms compatible systems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37917
]
Guillaume Nodet commented on SM-811:
Could you rework the patch to include the needed code in
AbstractJmsProcessor#fromNMS
I guess it will need an additional parameter for the exchange.
Also, is the value of the soap action really important ? What if no operation
is defined on the exchange ?
And the current code will throw an NPE if the targetService / targetInterface
attribute
is used on the endpoint, because the exchange.getEndpoint() may return null.
Thanks !
> servicemix-jms does not set SoapAction property for SOAP jms messages
> -
>
> Key: SM-811
> URL: https://issues.apache.org/activemq/browse/SM-811
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.0, 3.0.1, 3.1
> Environment: Tested with Tibco EMS as jms server and Tibco Business
> works as system providing the service. The error should also occur with
> ActiveMQ.
>Reporter: Christian Schneider
>Priority: Critical
> Attachments: servicemix-jms-sm-811.patch,
> servicemix-jsr181-sm-811.patch
>
>
> When tibco is the client all works well but when tibco implements the service
> it rejects the soap/jms message as it wants the SoapAction jms property to be
> set.
> I have added a dummy SoapAction in StandardProviderProcessor:
> ...
> MessageProducer producer = session.createProducer(destination);
> TextMessage msg = session.createTextMessage();
> NormalizedMessage nm = exchange.getMessage("in");
> fromNMS(nm, msg);
> String soapAction = "default";
> msg.setStringProperty("SoapAction", soapAction);
> ...
> I was able to do a complete request/reply with tibco in this way. Of course
> the "default" SoapAction will only help if my service has only one method.
> From what I see in Tibco the SoapAction should at least contain the method
> name of the service being called.
> The servicemix-jms component should by default set this property to make it
> more compatible with other soap/jms compatible systems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[
https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37919
]
Christian Schneider commented on SM-811:
I will rework the patch.
Btw. There is an interesting standardization effort from Sonic, Tibco, IBM and
BEA for the jms binding:
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/raw/[EMAIL
PROTECTED]/3#soap-binding
> servicemix-jms does not set SoapAction property for SOAP jms messages
> -
>
> Key: SM-811
> URL: https://issues.apache.org/activemq/browse/SM-811
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
>Affects Versions: 3.0, 3.0.1, 3.1
> Environment: Tested with Tibco EMS as jms server and Tibco Business
> works as system providing the service. The error should also occur with
> ActiveMQ.
>Reporter: Christian Schneider
>Priority: Critical
> Attachments: servicemix-jms-sm-811.patch,
> servicemix-jsr181-sm-811.patch
>
>
> When tibco is the client all works well but when tibco implements the service
> it rejects the soap/jms message as it wants the SoapAction jms property to be
> set.
> I have added a dummy SoapAction in StandardProviderProcessor:
> ...
> MessageProducer producer = session.createProducer(destination);
> TextMessage msg = session.createTextMessage();
> NormalizedMessage nm = exchange.getMessage("in");
> fromNMS(nm, msg);
> String soapAction = "default";
> msg.setStringProperty("SoapAction", soapAction);
> ...
> I was able to do a complete request/reply with tibco in this way. Of course
> the "default" SoapAction will only help if my service has only one method.
> From what I see in Tibco the SoapAction should at least contain the method
> name of the service being called.
> The servicemix-jms component should by default set this property to make it
> more compatible with other soap/jms compatible systems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
