12 Replies Latest reply on Jan 5, 2009 6:54 AM by Kevin Conner

    Wrong EPR-to in message routed by StaticRouter

    Roy Kiesler Newbie

      I'm implementing an InputOutputFilter class, and using the quickstarts\invm_transport1 example as my test. This example uses the StaticRouter action on service #1 to route the message to Service #2.

      I noticed that when the process() method for Service #2's println action is implemented, the EPR-to in the message header is set to that of Service #1, as opposed to Service #2. The following debug output confirms this, as you can see the following:

      1. When Service #1 processes the message, the EPR URI is invm://48656c6c6f576f726c645365727669636531 ("531" hereafter)
      2. When the ServiceInvoker processes the message, the EPR URI points to invm://48656c6c6f576f726c645365727669636532 ("532" hereafter)
      3. When Service #2 processes the message, the EPR URI still points to "531"

      Is this by design?

      Thanks,
      --
      Roy

      15:52:37,854 DEBUG [JAXRRegistryImpl] Going to query the registry for name pattern [Service1]
      15:52:40,400 DEBUG [ActionProcessingPipeline] pipeline process for message: header: [ To: InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636531?false#10000/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
      15:52:40,400 DEBUG [ActionProcessingPipeline] executing processor 0 org.jboss.soa.esb.actions.SystemPrintln@cc6798 header: [ To: InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636531?false#10000/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
      15:52:40,400 INFO [STDOUT] - > Service 1:
      15:52:40,416 INFO [STDOUT] [Hello InVM Transport!!].
      15:52:40,416 DEBUG [ActionProcessingPipeline] executing processor 1 org.jboss.soa.esb.actions.StaticRouter@12062da header: [ To: InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636531?false#10000/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
      15:52:40,494 DEBUG [JAXRRegistryImpl] Going to query the registry for name pattern [Service2]
      15:52:40,619 DEBUG [JAXRRegistryImpl] Going to query the registry for name pattern [Service2]
      15:52:40,619 DEBUG [ServiceInvoker] EPR=InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636532?false#10000/> > ] XML=<wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"><wsa:Address>invm://48656c6c6f576f726c645365727669636532?false#10000</wsa:Address><wsa:ReferenceProperties><jbossesb:type xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb">urn:jboss/esb/epr/type/invm</jbossesb:type></wsa:ReferenceProperties></wsa:From>
      15:52:40,635 DEBUG [ActionProcessingPipeline] pipeline process for message: header: [ To: InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636532?false#10000/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
      15:52:40,635 DEBUG [ActionProcessingPipeline] executing processor 0 org.jboss.soa.esb.actions.SystemPrintln@9bbe68 header: [ To: InVMEpr [ PortReference < <wsa:Address invm://48656c6c6f576f726c645365727669636531?false#10000/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] ]
      15:52:40,635 INFO [STDOUT] - - > Service 2:
      15:52:40,635 INFO [STDOUT] [Hello InVM Transport!!].