By the way, I tried switching from the AsyncWeb transports back to the
commons-http (I edited my axis2.xml)

I still got the same errors. I think this must be something to do with
how we are enabling RM on outflow, or maybe in the Sandesha2 code.

Anyway I'll try and trace it through, I just thought I'd keep you updated.

Paul

On 10/23/06, Paul Fremantle <[EMAIL PROTECTED]> wrote:
So I've run up against a bug in the <enableRM/> (or at least it isn't
working for me).

So this is the JMS->RM case.

Here is my Synapse.xml

 <proxies>
      <proxy name="JMSProxy" transports="jms" description="A simple
JMS listener">
       <target sequence="soap"/>
       <property name="transport.jms.ConnectionFactory" value="simpleQCF"/>
       <property name="transport.jms.Destination"
value="dynamicQueues/something.TestQueue"/>
     </proxy>
   </proxies>

  <definitions>
        <sequence name="soap">
                <rest value="false"/>
                <header name="ReplyTo"
value="http://www.w3.org/2005/08/addressing/anonymous"/>
                <header name="Action"
value="http://dgme.finances.gouv.fr/presto/submitOneWay"/>
                <send>
                        <endpoint ref="rx"/>
                </send>
        </sequence>


        <endpoint name="rx" address="http://localhost:9000/soap/PrestoService";>
                <enableAddressing/>
                <enableRM/>
        </endpoint>
        <endpoint name="jms"
address="jms:/dynamicQueues/something.TestQueue2?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616"/>
  </definitions>

When I remove the <enableRM/> the system works fine. When I put
<enableRM/> back in, the replyTo goes wrong:
<wsa:ReplyTo>
          
<wsa:Address>jms:/__RM_AND_ADDR__?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.provider.url=tcp://localhost:61616</wsa:Address>
         </wsa:ReplyTo>

This is true for both the CreateSequence and the actual business
messages. Because the ReplyTo is wrong, so is the AcksTo.

I really can't figure out why the ReplyTo is getting reset back to the JMS one!

Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com



--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to