Re: [petals-users] eip se Loop ?

["Jérémie Doucy" <jdoucy@xxxxxxxxx>]

For the moment I'm going to wrote something a bit static, pending the bpel SE.

Thanks for all.

2007/11/8, Marc Dutoo <marc.dutoo@xxxxxxxxxxx >:

Hello

With the POJO SE you only have to write a mere Java class compared to a
full SE. Have a look at the doc. However I hope you have a good idea of
what you want to write and how to use xpath in java code, otherwise
you'd be better off using my provided solution.

Regards
Marc

Jérémie Doucy a écrit :
> Hello,
> ode install hisself but won't start for the moment ....
> I think i'm going to use, for the moment, my own SE. You said I should
> use the POJO engine, what's sort of benefit can it bring to me compare
> to developing my own SE (with the CDK)?
>
> 2007/11/7, Marc Dutoo <marc.dutoo@xxxxxxxxxxx
> <mailto:marc.dutoo@xxxxxxxxxxx >>:
>
>     Hello
>
>     I know some petals components have been successfully tested on other
>     ESBs like Sun OpenESB, but I don't know if anyone has done the opposite
>     - said petals components successful tests seem to be the exception
>     rather than the rule in the world of JBI components, whatever the
>     standard would it like to be...
>
>     Regards
>     Marc
>
>     Jérémie Doucy a écrit :
>      > Hello marc,
>      >
>      > I agree with you what I need is a bpel integration...
>      >
>      > I wait since 7 month for the bpel integration, I'm curently try to
>      > deploy ode-jbi-se on PEtALS, but it's not working (for the moment)..
>      >
>      > Do you know if somenone has already deploy a jbi engine from
>     another ESB ?
>      >
>      > 2007/11/7, Marc Dutoo < marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>
>      > <mailto:marc.dutoo@xxxxxxxxxxx <mailto: marc.dutoo@xxxxxxxxxxx>>>:
>      >
>      >     Hello Jérémie
>      >
>      >     Note that you may prefer to write it in java/POJO or wait a
>     little bit
>      >     for the BPEL/Orchestra engine integration.
>      >
>      >     I agree it is complex, but a splitter pattern in itself is
>     not trivial.
>      >
>      >     We did not include variable handling among the EIP features
>     because we
>      >     felt it was a kind of limit where, when you cross it, you'd
>     be better
>      >     off with heavier orchestration solutions like BPEL - but this
>     is subject
>      >     to discussion.
>      >
>      >     Endpoints may be specified through different ways, including
>     using
>      >     get-cells-by-xpath. What other missing feature are thinking
>     about ?
>      >
>      >     Regards
>      >     Marc
>      >
>      >     Jérémie Doucy a écrit :
>      >      > Thanks, I'm going to try this.
>      >      > But it seems to be very complex for something that look
>     simple...
>      >      > In fact I think that the EIP problem is that we are unable
>     to add
>      >      > variable, and to specify the endpoint argument.
>      >      >
>      >      >
>      >      > 2007/11/7, Marc Dutoo <marc.dutoo@xxxxxxxxxxx
>     <mailto: marc.dutoo@xxxxxxxxxxx>
>      >     <mailto: marc.dutoo@xxxxxxxxxxx <mailto:marc.dutoo@xxxxxxxxxxx>>
>      >      > <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx> <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>>>>:
>      >      >
>      >      >     Hello
>      >      >
>      >      >     The short answer is yes, please find how I would
>     implement such a
>      >      >     splitter pattern below.
>      >      >
>      >      >     However you may find this way a bit complex (needs 4
>      >     additional SUs) and
>      >      >     you might prefer doing it in java the POJO way.
>      >      >     Note that we plan in the next version of the EIP to allow
>      >      >     <get-calls-by-service> to return any kind of EIP
>      >     orchestration and not
>      >      >     only "flat" calls, which will make this case simpler.
>      >      >
>      >      >     Your main EIP configuration will be :
>      >      >     <chain>
>      >      >        <!-- the following returns
>      >      >     <uris><uri>foo</uri><uri>bar</uri></uris> -->
>      >      >        <call service="uriService" operation="getUris"/>
>      >      >        <!-- the following sends this return message to all
>      >     services returned
>      >      >     by the XSL transformation  -->
>      >      >        <aggregate>
>      >      >          <get-calls-by-service
>      >      >            service="{
>      >     http://petals.objectweb.org/}UriToCallXsltService "
>      >      >            operation="xmlString"/>
>      >      >        </aggregate>
>      >      >     </chain>
>      >      >     NB. if you don't need to return an aggregate of all
>     messages
>      >      >     returned by
>      >      >       the target service, you may replace the subtop
>     <aggregate> by a
>      >      >     <dispatch> here.
>      >      >
>      >      >     for this you also need to deploy an XSLT SU at
>      >      >     { http://petals.objectweb.org/}UriToCallXsltService
>     < http://petals.objectweb.org/}UriToCallXsltService>
>      >      >     <http://petals.objectweb.org/}UriToCallXsltService>
>     that will
>      >      >     specify the
>      >      >     number of service calls (iterations) by transforming
>      >      >     <uris>
>      >      >        <uri>foo</uri>
>      >      >        <uri>bar</uri>
>      >      >        ...
>      >      >     </uris>
>      >      >     in
>      >      >     <calls>
>      >      >        <call
>      >      >
>      >
>     service="{http://petals.objectweb.org/}SingleIterationCallEipService
>     <http://petals.objectweb.org/}SingleIterationCallEipService>"
>      >      >     operation="process"/>
>      >      >        <call
>      >      >     service="{
>      >     http://petals.objectweb.org/}SingleIterationCallEipService
>      >     <http://petals.objectweb.org/}SingleIterationCallEipService>"
>      >      >     operation="process"/>
>      >      >        ...
>      >      >     </calls>
>      >      >
>      >      >     and to deploy another EIP SU at
>      >      >     {
>     http://petals.objectweb.org/}SingleIterationCallEipService
>      >     that has the
>      >      >     following configuration, which will literally execute one
>      >     iteration of
>      >      >     the service call loop :
>      >      >     <dispatch>
>      >      >        <chain><!-- This chain gets the CURRENT first
>      >     <uri>foo</uri> and
>      >      >     calls the target service with it -->
>      >      >          <call
>      >      >     service="{
>     http://petals.objectweb.org/}GetFirstUriXsltService"
>      >      >     operation="process"/>
>      >      >          <call service="myService" operation="myOperation"/>
>      >      >        </chain>
>      >      >        <!-- The following call returns the uri list
>     WITHOUT the
>      >     first one,
>      >      >     ex. <uris><uri>bar</uri></uris> -->
>      >      >        <call
>      >      >     service="{
>      >     http://petals.objectweb.org/}DeleteFirstUriXsltService "
>      >      >     operation="process"/>
>      >      >     </dispatch>
>      >      >
>      >      >     and to deploy two other XSLT transformations, one  at
>      >      >     { http://petals.objectweb.org/}GetFirstUriXsltService
>      >      >     < http://petals.objectweb.org/}GetFirstUriXsltService
>      >     <http://petals.objectweb.org/}GetFirstUriXsltService>> that will
>      >      >     transform
>      >      >     <uris>
>      >      >        <uri>foo</uri>
>      >      >        <uri>bar</uri>
>      >      >        ...
>      >      >     </uris>
>      >      >     to
>      >      >     <uri>foo</uri>
>      >      >
>      >      >     and another one at
>      >      >     {
>     http://petals.objectweb.org/}DeleteFirstUriXsltServic
>     < http://petals.objectweb.org/}DeleteFirstUriXsltServic> that will
>      >      >     transform
>      >      >     <uris>
>      >      >        <uri>foo</uri>
>      >      >        <uri>bar</uri>
>      >      >        ...
>      >      >     </uris>
>      >      >     to
>      >      >     <uris>
>      >      >        <uri>bar</uri>
>      >      >        ...
>      >      >     </uris>
>      >      >
>      >      >     Regards,
>      >      >     Marc Dutoo
>      >      >     Open Wide
>      >      >
>      >      >     Jérémie Doucy a écrit :
>      >      >      > My problem is this one :
>      >      >      >
>      >      >      > My first endpoint respond something like :
>      >      >      > <uri>foo</uri><uri>bar</uri>
>      >      >      >
>      >      >      > And I want to call another endpoint with
>     <uri>foo</uri> as
>      >      >     parameter a
>      >      >      > first time and <uri>bar</uri> a second time.
>      >      >      >
>      >      >      > In fact my chain is something like :
>      >      >      > call service1 returns list of uri
>      >      >      > for each uri
>      >      >      > call service2
>      >      >      >
>      >      >      >
>      >      >      > Is the EIP component with XSL transformation able
>     to do this ?
>      >      >      >
>      >      >      > Thanks in advance
>      >      >      >
>      >      >      > 2007/11/7, Marc Dutoo < marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>
>      >     <mailto:marc.dutoo@xxxxxxxxxxx <mailto: marc.dutoo@xxxxxxxxxxx>>
>      >      >     <mailto:marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx > <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>>>
>      >      >      > <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>
>      >     <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto:marc.dutoo@xxxxxxxxxxx>> <mailto: marc.dutoo@xxxxxxxxxxx
>     <mailto: marc.dutoo@xxxxxxxxxxx>
>      >     <mailto:marc.dutoo@xxxxxxxxxxx
>     <mailto: marc.dutoo@xxxxxxxxxxx>>>>>:
>      >      >      >
>      >      >      >     Hi Jeremie
>      >      >      >
>      >      >      >     You can use either get-calls-by-service or
>      >     get-calls-by-xpath
>      >      >     , that
>      >      >      >     will execute the <calls> element that is specified
>      >     either in
>      >      >     the message
>      >      >      >     returned by the service call (for
>      >     get-calls-by-service) or in an
>      >      >      >     xpath-specified part of the input message
>     content (for
>      >      >      >     get-calls-by-xpath). If the service return
>     message or
>      >     the message
>      >      >      >     content have not the right shape (i.e . <calls>...
>      >     </calls>),
>      >      >     you may
>      >      >      >     typically chain an XSL transformation.
>      >      >      >
>      >      >      >     If you chain an XSL transformation where you
>     use the full
>      >      >     power (looping
>      >      >      >     etc.) of xpath to output dynamically the right
>     list of
>      >     calls, and
>      >      >      >     integrate it either as a service by
>      >     get-calls-by-service or as a
>      >      >      >     chained
>      >      >      >     content transformation by get-calls-by-xpath,
>     you will be
>      >      >     able to build
>      >      >      >     any complex (loops etc.) orchestration that you
>     may need.
>      >      >      >
>      >      >      >     Regards
>      >      >      >     Marc Dutoo
>      >      >      >     Open Wide
>      >      >      >
>      >      >      >     Doucy Jeremie a écrit :
>      >      >      >      > Hello,
>      >      >      >      >
>      >      >      >      > I use petals-se-eip and it works fine for me.
>      >      >      >      >
>      >      >      >      > Is there any way to loop in this service
>     Engine,
>      >     something
>      >      >      >     like  a while ?
>      >      >      >      >
>      >      >      >      > Thanks in advance
>      >      >      >      >
>      >      >      >
>      >      >      >
>      >      >      >
>      >      >      >     --
>      >      >      >     You receive this message as a subscriber of the
>      >      >     petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>
>     <mailto:petals-users@xxxxxxx <mailto: petals-users@xxxxxxx>>
>      >     <mailto:petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>
>     <mailto: petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>>>
>      >      >      >     <mailto: petals-users@xxxxxxx
>     <mailto:petals-users@xxxxxxx>
>      >     <mailto:petals-users@xxxxxxx <mailto: petals-users@xxxxxxx> >
>     <mailto: petals-users@xxxxxxx <mailto:petals-users@xxxxxxx >
>      >     <mailto:petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>>>>
>      >      >     mailing list.
>      >      >      >     To unsubscribe:
>      >     mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>
>      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>>
>      >      >     <mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>
>      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>>>
>      >      >      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>
>      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>>
>      >      >     <mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>
>      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto: petals-users-unsubscribe@xxxxxxx>>>>
>      >      >      >     For general help: mailto: sympa@xxxxxxx
>     <mailto: sympa@xxxxxxx>
>      >     <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx>> <mailto:
>     sympa@xxxxxxx <mailto:sympa@xxxxxxx> <mailto:sympa@xxxxxxx
>     <mailto:sympa@xxxxxxx>>>
>      >      >      >     <mailto: sympa@xxxxxxx <mailto:sympa@xxxxxxx>
>     <mailto: sympa@xxxxxxx <mailto:sympa@xxxxxxx>>
>      >     <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx >
>     <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx>>>>?subject=help
>      >      >      >     OW2 mailing lists service home page:
>      >     http://www.ow2.org/wws
>      >      >      >
>      >      >      >
>      >      >
>      >      >
>      >      >
>      >      >     --
>      >      >     You receive this message as a subscriber of the
>      >     petals-users@xxxxxxx <mailto: petals-users@xxxxxxx>
>     <mailto:petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>>
>      >      >     <mailto: petals-users@xxxxxxx
>     <mailto:petals-users@xxxxxxx> <mailto:petals-users@xxxxxxx
>     <mailto:petals-users@xxxxxxx>>>
>      >     mailing list.
>      >      >     To unsubscribe: mailto:
>     petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>
>      >     <mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>>
>      >      >     <mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>
>      >     <mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>>>
>      >      >     For general help: mailto: sympa@xxxxxxx
>     <mailto:sympa@xxxxxxx> <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx>>
>      >      >     <mailto: sympa@xxxxxxx <mailto:sympa@xxxxxxx>
>     <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx> >>?subject=help
>      >      >     OW2 mailing lists service home page:
>     http://www.ow2.org/wws
>      >      >
>      >      >
>      >
>      >
>      >
>      >     --
>      >     You receive this message as a subscriber of the
>     petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>
>      >     <mailto:petals-users@xxxxxxx <mailto:petals-users@xxxxxxx>>
>     mailing list.
>      >     To unsubscribe: mailto: petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>
>      >     <mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>>
>      >     For general help: mailto: sympa@xxxxxxx <mailto: sympa@xxxxxxx>
>      >     <mailto:sympa@xxxxxxx <mailto:sympa@xxxxxxx>>?subject=help
>      >     OW2 mailing lists service home page: http://www.ow2.org/wws
>      >
>      >
>
>
>
>     --
>     You receive this message as a subscriber of the petals-users@xxxxxxx
>     <mailto:petals-users@xxxxxxx> mailing list.
>     To unsubscribe: mailto:petals-users-unsubscribe@xxxxxxx
>     <mailto:petals-users-unsubscribe@xxxxxxx>
>     For general help: mailto:sympa@xxxxxxx
>     <mailto: sympa@xxxxxxx>?subject=help
>     OW2 mailing lists service home page: http://www.ow2.org/wws
>
>



--
You receive this message as a subscriber of the petals-users@xxxxxxx mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@xxxxxxx
For general help: mailto: sympa@xxxxxxx?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws