You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2006/11/20 12:30:01 UTC
[jira] Created: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Support POX, Text and Binary JMS messages without requiring any additional headers
----------------------------------------------------------------------------------
Key: AXIS2-1752
URL: http://issues.apache.org/jira/browse/AXIS2-1752
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: kernel
Affects Versions: 1.1
Reporter: Asankha C. Perera
Assigned To: Asankha C. Perera
Priority: Minor
I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
Hence a simple JMS text message with the content "hello world" would be transformed into the form
<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
and a simple JMS binary message containing a byte array, as shown below
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header />
<soapenv:Body>
<axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
<xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
</axis2ns1:jmsMessage>
</soapenv:Body>
</soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
<1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=comments#action_12451729 ]
Davanum Srinivas commented on AXIS2-1752:
-----------------------------------------
sure. please go ahead.
thanks,
dims
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=all ]
Asankha C. Perera updated AXIS2-1752:
-------------------------------------
Attachment: jms_pox_fix.patch
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=all ]
Asankha C. Perera resolved AXIS2-1752.
--------------------------------------
Resolution: Fixed
fixed for 1.1.1
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch, jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=comments#action_12451321 ]
Davanum Srinivas commented on AXIS2-1752:
-----------------------------------------
Are u sure about the default operation name? is this a relic from synapse? can we leave it empty/null?
public static final QName DEFAULT_OPERATION = new QName("urn:mediate");
thanks,
dims
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=comments#action_12451694 ]
Asankha C. Perera commented on AXIS2-1752:
------------------------------------------
Dims
This applies only for *plain text* messages arriving over JMS, and I think Synapse would be using or supporting this feature almost all of the time, and hence the default set to a useful value for the common case :)
thanks
asankha
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-1752) Support POX, Text and Binary JMS
messages without requiring any additional headers
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-1752?page=all ]
Asankha C. Perera updated AXIS2-1752:
-------------------------------------
Attachment: jms_pox_fix.patch
Slight update to the patch before commit
> Support POX, Text and Binary JMS messages without requiring any additional headers
> ----------------------------------------------------------------------------------
>
> Key: AXIS2-1752
> URL: http://issues.apache.org/jira/browse/AXIS2-1752
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assigned To: Asankha C. Perera
> Priority: Minor
> Attachments: jms_pox_fix.patch, jms_pox_fix.patch
>
>
> I have updated the JMS transport to support POX, Text and Binary JMS messages without requiring any additional headers. A service could optionally provide the QName for the operation to invoke on such messages where the operation cannot be determined (i.e. pure text/binary messages with non-xml content), and this could be then specified with a parameter named "transport.jms.Operation"; this will default to urn:mediate. A service could optionally provide a QName for an element that will act as the holder of such content, and this could be specified with a parameter named "transport.jms.Wrapper" and will default to "jmsMessage" in the axis2 namespace.
> Hence a simple JMS text message with the content "hello world" would be transformed into the form
> <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header/><soapenv:Body><axis2ns1:jmsMessage xmlns:axis2ns1="axis2"><![CDATA[hello world]]></axis2ns1:jmsMessage></soapenv:Body></soapenv:Envelope>
> and a simple JMS binary message containing a byte array, as shown below
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
> <soapenv:Header />
> <soapenv:Body>
> <axis2ns1:jmsMessage xmlns:axis2ns1="http://ws.apache.org/namespaces/axis2">
> <xop:Include href="cid:1.urn:uuid:2E8CC8B0B017204A1A11611743285461@apache.org" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
> </axis2ns1:jmsMessage>
> </soapenv:Body>
> </soapenv:Envelope>--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462content-id:
> <1....@apache.org>content-type:application/octet-streamcontent-transfer-encoding:binary[[actual bytes here]]--MIMEBoundaryurn_uuid_2E8CC8B0B017204A1A11611743285462--
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org