3 Replies Latest reply on Dec 7, 2009 11:35 AM by philip.eisenhardt

    XPath in Riftsaw2.0 M2?

      I worked with glassfish/openESB, now I have to move to jboss+riftsaw.
      I modified one of the samples
      In my existing BPEL scripts I have this syntax

      test
      $CreateItemIn.createItem/arg0/@transactionId

      as a result I´d expect that my soap body contains something like this:
      <ns1:createItem>
      <arg0 transactionId="test" ...>
      ...
      but the soap body is this (on M1, M2 is the same message)
      <soapenv:Body>test</soapenv:Body>

      WS-BPEL 2.0 should be capable of interpreting the given syntax.

      I also tried this syntax
      arg0/@transactionId
      but this doesn´t help..

      If I generate the BPEL from the scratch (with Eclipse+JBoss Tool) the BPEL editor generates something like this:
      <bpel:to part="createItem" variable="CreateItemIn">
      <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[arg0/@transactionId]]></bpel:query>
      </bpel:to>

      I have tried two different environments
      JBoss 5.1.0+riftsaw 2.0 M1
      JBoss 5.1.0+riftsaw 2.0 M2

      Am I missing something? I assume I just have to use a slightly different syntax in my BPEL...

      Phil

        • 1. Re: XPath in Riftsaw2.0 M2?

          sorry, I didn't see the code tag, just posting the code snippet and the soap message again.

          that is the bpel syntax I have

          <copy>
          <from><literal>test</literal></from>
          <to>$CreateItemIn.createItem/arg0/@transactionId</to>
          </copy>


          alternate syntax
          <copy>
           <from><literal>transaction</literal></from>
           <to variable="CreateItemIn" part="createItem">arg0/@transactionId</to>
           </copy>
          


          the soap message look like this
          <createItem><createItem xmlns="...">test</createItem></createItem>




          • 2. Re: XPath in Riftsaw2.0 M2?
            objectiser

            Looks like an ODE problem. Interesting point is if the same behaviour occurs in RiftSaw M1 and M2, then the same issue exists in ODE2.0 aswell as ODE1.3.3.

            If you could create a jira and attach your example we will take a look.

            Regards
            Gary

            • 3. Re: XPath in Riftsaw2.0 M2?

              google found another possible explanation...
              with openesb the variables doesn't need to be initiated completely, as soon $CreateItemIn.createItem/arg0/@transactionId is used in a BPEL, the data structures are created down to the attribute (@transactionId)..
              ODE seems to be a bit more picky, the variables must be initialized completely (see http://www.mail-archive.com/user@ode.apache.org/msg02659.html//www.mail-archive.com/user@ode.apache.org/msg02659.html for more information)
              alternate way seems to be to work with extensions (e.g. insert-as-last-into()).