You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Cwik, Jan" <Ja...@sabre-holdings.com> on 2007/12/12 14:51:22 UTC
JbiConstants.SENDER_ENDPOINT property not set on MEX
Hi,
It seems that upon invoking a service from within the bpel the property
JbiConstants.SENDER_ENDPOINT ("org.apache.servicemix.senderEndpoint") is
not set on MEX.
I have a servicemix exchange listener and when messages comes to this
listener I'm not able to say from where it is. Please advise what to do
? Is it a bug or I need to do something to make ODE setting this
property.
regards
jan
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Guillaume Nodet <gn...@gmail.com>.
Well, Alex may comment on this, but there is no simple way to pass
informations from an input exchange to an output exchange. At least, all
JBI properties are lost in the process. We have already talked about that
on this list some time ago ...
But I agree, that a simple solution that only works in 90% is better than
nothing at all imho. We just need to discuss the problem and have the
limitations stated clearly.
On Dec 17, 2007 4:54 PM, Wielek, Lukasz <Lu...@sabre-holdings.com>
wrote:
>
> Guillaume ,
>
> What about using correlationId/senderEndpoint
> from the last MEX received ?
>
> In case of single receive (our case), it would be always proper values.
> In case of multiple receives, I think, it would not spoil anything,
> And, in my opinion, some information would be better than no information
> at all.
>
>
> Regards,
> Lukasz Wielek
>
> -----Original Message-----
> From: Guillaume Nodet [mailto:gnodet@gmail.com]
> Sent: Monday, December 17, 2007 2:20 PM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> There is a small problem though as how to build the needed value. The
> problem will be the exact same as with correlationIds.
> Let me explain: usually in ServiceMix, a given endpoint represents a
> service
> and can act as a provider and/or a consumer, but there is only one
> endpoint. In a bpel process, the process instance can receive multiple
> exchanges, so there may be multiple provider endpoints. In such a case,
> there is no simple way to create the needed value afaik.
> I would imagine that when there is a single receive with a
> createInstance="true", that the corresponding endpoint would be used.
> In
> more complicated cases, it don't see any simple solution.
>
> On Dec 17, 2007 9:18 AM, Wielek, Lukasz
> <Lu...@sabre-holdings.com>
> wrote:
>
> >
> > Alex,
> >
> > (I'm speaking on behalf of Jan.)
> >
> > Probably what you are looking for is
> >
> org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> > oint).
> > The endpoint passed to the getKey method should be the
> > endpoint which performs invoke.
> >
> > Regards,
> > Lukasz Wielek
> >
> > -----Original Message-----
> > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > Sent: Saturday, December 15, 2007 1:25 AM
> > To: dev@ode.apache.org
> > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> >
> > Do you know what should be the value associated with the
> SENDER_ENDPOINT
> > property? I looked around the ServiceMix code and it's assumed to be
> a
> > short String identifier but I can't figure out what the format of the
> > string
> > value should be. I was initially expecting to place the EPR (
> > org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> > doesn't
> > seem to fit the model here.
> >
> > alex
> >
> >
> > On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > >
> > > Hi,
> > >
> > > It would be good to have suche a feature, it's not critical but very
> > > nice to have. It would let track the message flow better in our
> > project.
> > >
> > > Could you please take care of it ?
> > >
> > > best regards
> > > jan
> > >
> > > -----Original Message-----
> > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > Sent: Thursday, December 13, 2007 6:38 PM
> > > To: dev@ode.apache.org
> > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > >
> > > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > >
> > > > It seems that upon invoking a service from within the bpel the
> > > property
> > > > JbiConstants.SENDER_ENDPOINT
> > ("org.apache.servicemix.senderEndpoint")
> > > is
> > > > not set on MEX.
> > > >
> > > > I have a servicemix exchange listener and when messages comes to
> > this
> > > > listener I'm not able to say from where it is. Please advise what
> to
> > > do
> > > > ? Is it a bug or I need to do something to make ODE setting this
> > > > property.
> > >
> > >
> > > Hi Jan,
> > >
> > > It isn't a bug per se, since the property isn't mandated by the JBI
> > > spec. I
> > > would qualify it as an improvement of our ServiceMix integration.
> Is
> > > this
> > > something you feel qualified to work on and submit a patch? If not,
> I
> > > can
> > > take care of it.
> > >
> > > alex
> > >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
RE: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by "Wielek, Lukasz" <Lu...@sabre-holdings.com>.
Guillaume ,
What about using correlationId/senderEndpoint
from the last MEX received ?
In case of single receive (our case), it would be always proper values.
In case of multiple receives, I think, it would not spoil anything,
And, in my opinion, some information would be better than no information
at all.
Regards,
Lukasz Wielek
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: Monday, December 17, 2007 2:20 PM
To: dev@ode.apache.org
Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
There is a small problem though as how to build the needed value. The
problem will be the exact same as with correlationIds.
Let me explain: usually in ServiceMix, a given endpoint represents a
service
and can act as a provider and/or a consumer, but there is only one
endpoint. In a bpel process, the process instance can receive multiple
exchanges, so there may be multiple provider endpoints. In such a case,
there is no simple way to create the needed value afaik.
I would imagine that when there is a single receive with a
createInstance="true", that the corresponding endpoint would be used.
In
more complicated cases, it don't see any simple solution.
On Dec 17, 2007 9:18 AM, Wielek, Lukasz
<Lu...@sabre-holdings.com>
wrote:
>
> Alex,
>
> (I'm speaking on behalf of Jan.)
>
> Probably what you are looking for is
>
org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> oint).
> The endpoint passed to the getKey method should be the
> endpoint which performs invoke.
>
> Regards,
> Lukasz Wielek
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Saturday, December 15, 2007 1:25 AM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> Do you know what should be the value associated with the
SENDER_ENDPOINT
> property? I looked around the ServiceMix code and it's assumed to be
a
> short String identifier but I can't figure out what the format of the
> string
> value should be. I was initially expecting to place the EPR (
> org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> doesn't
> seem to fit the model here.
>
> alex
>
>
> On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> >
> > Hi,
> >
> > It would be good to have suche a feature, it's not critical but very
> > nice to have. It would let track the message flow better in our
> project.
> >
> > Could you please take care of it ?
> >
> > best regards
> > jan
> >
> > -----Original Message-----
> > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > Sent: Thursday, December 13, 2007 6:38 PM
> > To: dev@ode.apache.org
> > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> >
> > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > >
> > > It seems that upon invoking a service from within the bpel the
> > property
> > > JbiConstants.SENDER_ENDPOINT
> ("org.apache.servicemix.senderEndpoint")
> > is
> > > not set on MEX.
> > >
> > > I have a servicemix exchange listener and when messages comes to
> this
> > > listener I'm not able to say from where it is. Please advise what
to
> > do
> > > ? Is it a bug or I need to do something to make ODE setting this
> > > property.
> >
> >
> > Hi Jan,
> >
> > It isn't a bug per se, since the property isn't mandated by the JBI
> > spec. I
> > would qualify it as an improvement of our ServiceMix integration.
Is
> > this
> > something you feel qualified to work on and submit a patch? If not,
I
> > can
> > take care of it.
> >
> > alex
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Guillaume Nodet <gn...@gmail.com>.
As I said, this leads to a problem when the BPEL process has multiple
<provides/> tags, which is allowed.
IMHO, it seems the info we are really missing is a way to know, for a given
bpel process, the list of <provides/> and <consumes/> elements. If we can
retrieve this list at runtime, we could draw the link between the jbi
provider endpoint activated by Ode for the <provides/> element and the
partner link that is used when sending the JBI exchange.
Another way would be to activate an external endpoint to represent this
"consumer endpoint" and associate it with the EPR of the partnerlink /
myRole. But still, the relationship between the two JBI endpoints can't
really be known without an additional metadata.
On Dec 17, 2007 4:32 PM, Wielek, Lukasz <Lu...@sabre-holdings.com>
wrote:
> Alex,
>
> The string is in format:
> {service_namespace}Service:endpoint
>
> Example:
> The deploy.xml contains:
>
> <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
> xmlns:sws="https://webservices.sabre.com/websvc">
> <process name="sws:Enhanced_AirBookProcess1.0.1">
> <in-memory>true</in-memory>
> <active>true</active>
>
> <provide partnerLink="Enhanced_AirBookRQPL">
> <service name="sws:Enhanced_AirBookRQ1.0.1" port="sws" />
> </provide>
>
> <invoke ....
> ...
>
> When some other service is invoked from bpel, the
> SENDER_ENDPOINT property value should be:
> {https://webservices.sabre.com/websvc}Enhanced_AirBookRQ1.0.1:sws<https://webservices.sabre.com/websvc%7DEnhanced_AirBookRQ1.0.1:sws>
>
>
>
> Regards,
> Lukasz Wielek
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Monday, December 17, 2007 3:50 PM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> I think it's different than the correlationId case, which is meant to
> track
> the end-to-end processing of a given request.
>
> In this case, I was thinking about sending the partnerLink's myRole
> endpoint
> (if any). My only issue is the encoding of the endpoint as a String.
> I'm
> not sure how ServiceMix treats the String.
>
> What do you think?
>
> alex
>
>
> On 12/17/07, Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > There is a small problem though as how to build the needed value. The
> > problem will be the exact same as with correlationIds.
> > Let me explain: usually in ServiceMix, a given endpoint represents a
> > service
> > and can act as a provider and/or a consumer, but there is only one
> > endpoint. In a bpel process, the process instance can receive
> multiple
> > exchanges, so there may be multiple provider endpoints. In such a
> case,
> > there is no simple way to create the needed value afaik.
> > I would imagine that when there is a single receive with a
> > createInstance="true", that the corresponding endpoint would be used.
> In
> > more complicated cases, it don't see any simple solution.
> >
> > On Dec 17, 2007 9:18 AM, Wielek, Lukasz
> <Lu...@sabre-holdings.com>
> > wrote:
> >
> > >
> > > Alex,
> > >
> > > (I'm speaking on behalf of Jan.)
> > >
> > > Probably what you are looking for is
> > >
> org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> > > oint).
> > > The endpoint passed to the getKey method should be the
> > > endpoint which performs invoke.
> > >
> > > Regards,
> > > Lukasz Wielek
> > >
> > > -----Original Message-----
> > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > Sent: Saturday, December 15, 2007 1:25 AM
> > > To: dev@ode.apache.org
> > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > >
> > > Do you know what should be the value associated with the
> SENDER_ENDPOINT
> > > property? I looked around the ServiceMix code and it's assumed to
> be a
> > > short String identifier but I can't figure out what the format of
> the
> > > string
> > > value should be. I was initially expecting to place the EPR (
> > > org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> > > doesn't
> > > seem to fit the model here.
> > >
> > > alex
> > >
> > >
> > > On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > It would be good to have suche a feature, it's not critical but
> very
> > > > nice to have. It would let track the message flow better in our
> > > project.
> > > >
> > > > Could you please take care of it ?
> > > >
> > > > best regards
> > > > jan
> > > >
> > > > -----Original Message-----
> > > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > > Sent: Thursday, December 13, 2007 6:38 PM
> > > > To: dev@ode.apache.org
> > > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > > >
> > > > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > > >
> > > > > It seems that upon invoking a service from within the bpel the
> > > > property
> > > > > JbiConstants.SENDER_ENDPOINT
> > > ("org.apache.servicemix.senderEndpoint")
> > > > is
> > > > > not set on MEX.
> > > > >
> > > > > I have a servicemix exchange listener and when messages comes to
> > > this
> > > > > listener I'm not able to say from where it is. Please advise
> what to
> > > > do
> > > > > ? Is it a bug or I need to do something to make ODE setting this
> > > > > property.
> > > >
> > > >
> > > > Hi Jan,
> > > >
> > > > It isn't a bug per se, since the property isn't mandated by the
> JBI
> > > > spec. I
> > > > would qualify it as an improvement of our ServiceMix integration.
> Is
> > > > this
> > > > something you feel qualified to work on and submit a patch? If
> not, I
> > > > can
> > > > take care of it.
> > > >
> > > > alex
> > > >
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
RE: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by "Wielek, Lukasz" <Lu...@sabre-holdings.com>.
Alex,
The string is in format:
{service_namespace}Service:endpoint
Example:
The deploy.xml contains:
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"
xmlns:sws="https://webservices.sabre.com/websvc">
<process name="sws:Enhanced_AirBookProcess1.0.1">
<in-memory>true</in-memory>
<active>true</active>
<provide partnerLink="Enhanced_AirBookRQPL">
<service name="sws:Enhanced_AirBookRQ1.0.1" port="sws" />
</provide>
<invoke ....
...
When some other service is invoked from bpel, the
SENDER_ENDPOINT property value should be:
{https://webservices.sabre.com/websvc}Enhanced_AirBookRQ1.0.1:sws
Regards,
Lukasz Wielek
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Monday, December 17, 2007 3:50 PM
To: dev@ode.apache.org
Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
I think it's different than the correlationId case, which is meant to
track
the end-to-end processing of a given request.
In this case, I was thinking about sending the partnerLink's myRole
endpoint
(if any). My only issue is the encoding of the endpoint as a String.
I'm
not sure how ServiceMix treats the String.
What do you think?
alex
On 12/17/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> There is a small problem though as how to build the needed value. The
> problem will be the exact same as with correlationIds.
> Let me explain: usually in ServiceMix, a given endpoint represents a
> service
> and can act as a provider and/or a consumer, but there is only one
> endpoint. In a bpel process, the process instance can receive
multiple
> exchanges, so there may be multiple provider endpoints. In such a
case,
> there is no simple way to create the needed value afaik.
> I would imagine that when there is a single receive with a
> createInstance="true", that the corresponding endpoint would be used.
In
> more complicated cases, it don't see any simple solution.
>
> On Dec 17, 2007 9:18 AM, Wielek, Lukasz
<Lu...@sabre-holdings.com>
> wrote:
>
> >
> > Alex,
> >
> > (I'm speaking on behalf of Jan.)
> >
> > Probably what you are looking for is
> >
org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> > oint).
> > The endpoint passed to the getKey method should be the
> > endpoint which performs invoke.
> >
> > Regards,
> > Lukasz Wielek
> >
> > -----Original Message-----
> > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > Sent: Saturday, December 15, 2007 1:25 AM
> > To: dev@ode.apache.org
> > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> >
> > Do you know what should be the value associated with the
SENDER_ENDPOINT
> > property? I looked around the ServiceMix code and it's assumed to
be a
> > short String identifier but I can't figure out what the format of
the
> > string
> > value should be. I was initially expecting to place the EPR (
> > org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> > doesn't
> > seem to fit the model here.
> >
> > alex
> >
> >
> > On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > >
> > > Hi,
> > >
> > > It would be good to have suche a feature, it's not critical but
very
> > > nice to have. It would let track the message flow better in our
> > project.
> > >
> > > Could you please take care of it ?
> > >
> > > best regards
> > > jan
> > >
> > > -----Original Message-----
> > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > Sent: Thursday, December 13, 2007 6:38 PM
> > > To: dev@ode.apache.org
> > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > >
> > > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > >
> > > > It seems that upon invoking a service from within the bpel the
> > > property
> > > > JbiConstants.SENDER_ENDPOINT
> > ("org.apache.servicemix.senderEndpoint")
> > > is
> > > > not set on MEX.
> > > >
> > > > I have a servicemix exchange listener and when messages comes to
> > this
> > > > listener I'm not able to say from where it is. Please advise
what to
> > > do
> > > > ? Is it a bug or I need to do something to make ODE setting this
> > > > property.
> > >
> > >
> > > Hi Jan,
> > >
> > > It isn't a bug per se, since the property isn't mandated by the
JBI
> > > spec. I
> > > would qualify it as an improvement of our ServiceMix integration.
Is
> > > this
> > > something you feel qualified to work on and submit a patch? If
not, I
> > > can
> > > take care of it.
> > >
> > > alex
> > >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Guillaume Nodet <gn...@gmail.com>.
On Dec 17, 2007 3:50 PM, Alex Boisvert <bo...@intalio.com> wrote:
> I think it's different than the correlationId case, which is meant to
> track
> the end-to-end processing of a given request.
Yeah. The purpose is really different, but I meant the problem is related
to the fact that BPEL often have multiple provider endpoints so that they
receive exchanges from different consumers.
>
>
> In this case, I was thinking about sending the partnerLink's myRole
> endpoint
> (if any). My only issue is the encoding of the endpoint as a String.
> I'm
> not sure how ServiceMix treats the String.
>
> What do you think?
This information is used to be able to draw some diagrams (as in
http://servicemix.apache.org/visualisation.html) or such tasks related to
the flow of information inside ServiceMix. If the value sent is not the
same as the one that receives the JBI exchange, the whole flow won't be
viewed. The information can still be used by a router of something like
that, so there is still some value in it.
Jan, can you comment on your exact need ? What would you use this value for
?
>
> alex
>
>
> On 12/17/07, Guillaume Nodet <gn...@gmail.com> wrote:
> >
> > There is a small problem though as how to build the needed value. The
> > problem will be the exact same as with correlationIds.
> > Let me explain: usually in ServiceMix, a given endpoint represents a
> > service
> > and can act as a provider and/or a consumer, but there is only one
> > endpoint. In a bpel process, the process instance can receive multiple
> > exchanges, so there may be multiple provider endpoints. In such a case,
> > there is no simple way to create the needed value afaik.
> > I would imagine that when there is a single receive with a
> > createInstance="true", that the corresponding endpoint would be used.
> In
> > more complicated cases, it don't see any simple solution.
> >
> > On Dec 17, 2007 9:18 AM, Wielek, Lukasz <
> Lukasz.Wielek@sabre-holdings.com>
> > wrote:
> >
> > >
> > > Alex,
> > >
> > > (I'm speaking on behalf of Jan.)
> > >
> > > Probably what you are looking for is
> > > org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey
> (ServiceEndp
> > > oint).
> > > The endpoint passed to the getKey method should be the
> > > endpoint which performs invoke.
> > >
> > > Regards,
> > > Lukasz Wielek
> > >
> > > -----Original Message-----
> > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > Sent: Saturday, December 15, 2007 1:25 AM
> > > To: dev@ode.apache.org
> > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > >
> > > Do you know what should be the value associated with the
> SENDER_ENDPOINT
> > > property? I looked around the ServiceMix code and it's assumed to be
> a
> > > short String identifier but I can't figure out what the format of the
> > > string
> > > value should be. I was initially expecting to place the EPR (
> > > org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> > > doesn't
> > > seem to fit the model here.
> > >
> > > alex
> > >
> > >
> > > On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > It would be good to have suche a feature, it's not critical but very
> > > > nice to have. It would let track the message flow better in our
> > > project.
> > > >
> > > > Could you please take care of it ?
> > > >
> > > > best regards
> > > > jan
> > > >
> > > > -----Original Message-----
> > > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > > Sent: Thursday, December 13, 2007 6:38 PM
> > > > To: dev@ode.apache.org
> > > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > > >
> > > > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > > >
> > > > > It seems that upon invoking a service from within the bpel the
> > > > property
> > > > > JbiConstants.SENDER_ENDPOINT
> > > ("org.apache.servicemix.senderEndpoint")
> > > > is
> > > > > not set on MEX.
> > > > >
> > > > > I have a servicemix exchange listener and when messages comes to
> > > this
> > > > > listener I'm not able to say from where it is. Please advise what
> to
> > > > do
> > > > > ? Is it a bug or I need to do something to make ODE setting this
> > > > > property.
> > > >
> > > >
> > > > Hi Jan,
> > > >
> > > > It isn't a bug per se, since the property isn't mandated by the JBI
> > > > spec. I
> > > > would qualify it as an improvement of our ServiceMix integration.
> Is
> > > > this
> > > > something you feel qualified to work on and submit a patch? If not,
> I
> > > > can
> > > > take care of it.
> > > >
> > > > alex
> > > >
> > >
> >
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Alex Boisvert <bo...@intalio.com>.
I think it's different than the correlationId case, which is meant to track
the end-to-end processing of a given request.
In this case, I was thinking about sending the partnerLink's myRole endpoint
(if any). My only issue is the encoding of the endpoint as a String. I'm
not sure how ServiceMix treats the String.
What do you think?
alex
On 12/17/07, Guillaume Nodet <gn...@gmail.com> wrote:
>
> There is a small problem though as how to build the needed value. The
> problem will be the exact same as with correlationIds.
> Let me explain: usually in ServiceMix, a given endpoint represents a
> service
> and can act as a provider and/or a consumer, but there is only one
> endpoint. In a bpel process, the process instance can receive multiple
> exchanges, so there may be multiple provider endpoints. In such a case,
> there is no simple way to create the needed value afaik.
> I would imagine that when there is a single receive with a
> createInstance="true", that the corresponding endpoint would be used. In
> more complicated cases, it don't see any simple solution.
>
> On Dec 17, 2007 9:18 AM, Wielek, Lukasz <Lu...@sabre-holdings.com>
> wrote:
>
> >
> > Alex,
> >
> > (I'm speaking on behalf of Jan.)
> >
> > Probably what you are looking for is
> > org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> > oint).
> > The endpoint passed to the getKey method should be the
> > endpoint which performs invoke.
> >
> > Regards,
> > Lukasz Wielek
> >
> > -----Original Message-----
> > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > Sent: Saturday, December 15, 2007 1:25 AM
> > To: dev@ode.apache.org
> > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> >
> > Do you know what should be the value associated with the SENDER_ENDPOINT
> > property? I looked around the ServiceMix code and it's assumed to be a
> > short String identifier but I can't figure out what the format of the
> > string
> > value should be. I was initially expecting to place the EPR (
> > org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> > doesn't
> > seem to fit the model here.
> >
> > alex
> >
> >
> > On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > >
> > > Hi,
> > >
> > > It would be good to have suche a feature, it's not critical but very
> > > nice to have. It would let track the message flow better in our
> > project.
> > >
> > > Could you please take care of it ?
> > >
> > > best regards
> > > jan
> > >
> > > -----Original Message-----
> > > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > > Sent: Thursday, December 13, 2007 6:38 PM
> > > To: dev@ode.apache.org
> > > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> > >
> > > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > > >
> > > > It seems that upon invoking a service from within the bpel the
> > > property
> > > > JbiConstants.SENDER_ENDPOINT
> > ("org.apache.servicemix.senderEndpoint")
> > > is
> > > > not set on MEX.
> > > >
> > > > I have a servicemix exchange listener and when messages comes to
> > this
> > > > listener I'm not able to say from where it is. Please advise what to
> > > do
> > > > ? Is it a bug or I need to do something to make ODE setting this
> > > > property.
> > >
> > >
> > > Hi Jan,
> > >
> > > It isn't a bug per se, since the property isn't mandated by the JBI
> > > spec. I
> > > would qualify it as an improvement of our ServiceMix integration. Is
> > > this
> > > something you feel qualified to work on and submit a patch? If not, I
> > > can
> > > take care of it.
> > >
> > > alex
> > >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Guillaume Nodet <gn...@gmail.com>.
There is a small problem though as how to build the needed value. The
problem will be the exact same as with correlationIds.
Let me explain: usually in ServiceMix, a given endpoint represents a service
and can act as a provider and/or a consumer, but there is only one
endpoint. In a bpel process, the process instance can receive multiple
exchanges, so there may be multiple provider endpoints. In such a case,
there is no simple way to create the needed value afaik.
I would imagine that when there is a single receive with a
createInstance="true", that the corresponding endpoint would be used. In
more complicated cases, it don't see any simple solution.
On Dec 17, 2007 9:18 AM, Wielek, Lukasz <Lu...@sabre-holdings.com>
wrote:
>
> Alex,
>
> (I'm speaking on behalf of Jan.)
>
> Probably what you are looking for is
> org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
> oint).
> The endpoint passed to the getKey method should be the
> endpoint which performs invoke.
>
> Regards,
> Lukasz Wielek
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Saturday, December 15, 2007 1:25 AM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> Do you know what should be the value associated with the SENDER_ENDPOINT
> property? I looked around the ServiceMix code and it's assumed to be a
> short String identifier but I can't figure out what the format of the
> string
> value should be. I was initially expecting to place the EPR (
> org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
> doesn't
> seem to fit the model here.
>
> alex
>
>
> On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> >
> > Hi,
> >
> > It would be good to have suche a feature, it's not critical but very
> > nice to have. It would let track the message flow better in our
> project.
> >
> > Could you please take care of it ?
> >
> > best regards
> > jan
> >
> > -----Original Message-----
> > From: Alex Boisvert [mailto:boisvert@intalio.com]
> > Sent: Thursday, December 13, 2007 6:38 PM
> > To: dev@ode.apache.org
> > Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
> >
> > On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> > >
> > > It seems that upon invoking a service from within the bpel the
> > property
> > > JbiConstants.SENDER_ENDPOINT
> ("org.apache.servicemix.senderEndpoint")
> > is
> > > not set on MEX.
> > >
> > > I have a servicemix exchange listener and when messages comes to
> this
> > > listener I'm not able to say from where it is. Please advise what to
> > do
> > > ? Is it a bug or I need to do something to make ODE setting this
> > > property.
> >
> >
> > Hi Jan,
> >
> > It isn't a bug per se, since the property isn't mandated by the JBI
> > spec. I
> > would qualify it as an improvement of our ServiceMix integration. Is
> > this
> > something you feel qualified to work on and submit a patch? If not, I
> > can
> > take care of it.
> >
> > alex
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
RE: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by "Wielek, Lukasz" <Lu...@sabre-holdings.com>.
Alex,
(I'm speaking on behalf of Jan.)
Probably what you are looking for is
org.apache.servicemix.jbi.servicedesc.EndpointSupport.getKey(ServiceEndp
oint).
The endpoint passed to the getKey method should be the
endpoint which performs invoke.
Regards,
Lukasz Wielek
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Saturday, December 15, 2007 1:25 AM
To: dev@ode.apache.org
Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Do you know what should be the value associated with the SENDER_ENDPOINT
property? I looked around the ServiceMix code and it's assumed to be a
short String identifier but I can't figure out what the format of the
string
value should be. I was initially expecting to place the EPR (
org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that
doesn't
seem to fit the model here.
alex
On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> Hi,
>
> It would be good to have suche a feature, it's not critical but very
> nice to have. It would let track the message flow better in our
project.
>
> Could you please take care of it ?
>
> best regards
> jan
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Thursday, December 13, 2007 6:38 PM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> >
> > It seems that upon invoking a service from within the bpel the
> property
> > JbiConstants.SENDER_ENDPOINT
("org.apache.servicemix.senderEndpoint")
> is
> > not set on MEX.
> >
> > I have a servicemix exchange listener and when messages comes to
this
> > listener I'm not able to say from where it is. Please advise what to
> do
> > ? Is it a bug or I need to do something to make ODE setting this
> > property.
>
>
> Hi Jan,
>
> It isn't a bug per se, since the property isn't mandated by the JBI
> spec. I
> would qualify it as an improvement of our ServiceMix integration. Is
> this
> something you feel qualified to work on and submit a patch? If not, I
> can
> take care of it.
>
> alex
>
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Alex Boisvert <bo...@intalio.com>.
Do you know what should be the value associated with the SENDER_ENDPOINT
property? I looked around the ServiceMix code and it's assumed to be a
short String identifier but I can't figure out what the format of the string
value should be. I was initially expecting to place the EPR (
org.w3c.dom.DocumentFragment) of the partnerLink's myRole but that doesn't
seem to fit the model here.
alex
On 12/14/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> Hi,
>
> It would be good to have suche a feature, it's not critical but very
> nice to have. It would let track the message flow better in our project.
>
> Could you please take care of it ?
>
> best regards
> jan
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Thursday, December 13, 2007 6:38 PM
> To: dev@ode.apache.org
> Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
>
> On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
> >
> > It seems that upon invoking a service from within the bpel the
> property
> > JbiConstants.SENDER_ENDPOINT ("org.apache.servicemix.senderEndpoint")
> is
> > not set on MEX.
> >
> > I have a servicemix exchange listener and when messages comes to this
> > listener I'm not able to say from where it is. Please advise what to
> do
> > ? Is it a bug or I need to do something to make ODE setting this
> > property.
>
>
> Hi Jan,
>
> It isn't a bug per se, since the property isn't mandated by the JBI
> spec. I
> would qualify it as an improvement of our ServiceMix integration. Is
> this
> something you feel qualified to work on and submit a patch? If not, I
> can
> take care of it.
>
> alex
>
RE: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by "Cwik, Jan" <Ja...@sabre-holdings.com>.
Hi,
It would be good to have suche a feature, it's not critical but very
nice to have. It would let track the message flow better in our project.
Could you please take care of it ?
best regards
jan
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Thursday, December 13, 2007 6:38 PM
To: dev@ode.apache.org
Subject: Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> It seems that upon invoking a service from within the bpel the
property
> JbiConstants.SENDER_ENDPOINT ("org.apache.servicemix.senderEndpoint")
is
> not set on MEX.
>
> I have a servicemix exchange listener and when messages comes to this
> listener I'm not able to say from where it is. Please advise what to
do
> ? Is it a bug or I need to do something to make ODE setting this
> property.
Hi Jan,
It isn't a bug per se, since the property isn't mandated by the JBI
spec. I
would qualify it as an improvement of our ServiceMix integration. Is
this
something you feel qualified to work on and submit a patch? If not, I
can
take care of it.
alex
Re: JbiConstants.SENDER_ENDPOINT property not set on MEX
Posted by Alex Boisvert <bo...@intalio.com>.
On 12/12/07, Cwik, Jan <Ja...@sabre-holdings.com> wrote:
>
> It seems that upon invoking a service from within the bpel the property
> JbiConstants.SENDER_ENDPOINT ("org.apache.servicemix.senderEndpoint") is
> not set on MEX.
>
> I have a servicemix exchange listener and when messages comes to this
> listener I'm not able to say from where it is. Please advise what to do
> ? Is it a bug or I need to do something to make ODE setting this
> property.
Hi Jan,
It isn't a bug per se, since the property isn't mandated by the JBI spec. I
would qualify it as an improvement of our ServiceMix integration. Is this
something you feel qualified to work on and submit a patch? If not, I can
take care of it.
alex