You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Eric Dofonsou <ew...@yahoo.com> on 2006/04/27 19:50:22 UTC

Servicemix-http additionnal info

Hello guys

I've got a question on how to configure
servixemix-http endpoints in the xml files (for
servicemix.xml and xbean.xml).

I've noticed that the way endpoints are defined in the
xml files is not same when using servicemix.xml or
xbean.xml.

In the case servicemix.xml The service value (on the
endpoint element) HAS to be same in both endpoint
(producer and provider). However in the case of the
xbean.xml that you put in serviceunit the service
value CANNOT be the same.

I was just wondering if some one could help me out
better understand this ?  Why is it like this ?

Thx in advance.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Servicemix-http additionnal info

Posted by Eric Dofonsou <ew...@yahoo.com>.
Thx

--- Guillaume Nodet <gn...@gmail.com> wrote:

> The servicemix-http component configuration is the
> same, using
> servicemix.xml or the SU deployment (xbean.xml).
> 
> I guess the confusion comes from the service /
> endpoint and
> targetService / targetEndpoint attributes.  The
> service and endpoint
> attributes are used to create an external JBI
> endpoint (that may be
> refered to by other components as described in the
> JBI spec).  If the
> targetService / targetEndpoint are not set, they
> will also be used as
> the target for the JBI exchange.
> 
> Cheers,
> Guillaume Nodet
> 
> On 4/27/06, Eric Dofonsou <ew...@yahoo.com>
> wrote:
> > Hello guys
> >
> > I've got a question on how to configure
> > servixemix-http endpoints in the xml files (for
> > servicemix.xml and xbean.xml).
> >
> > I've noticed that the way endpoints are defined in
> the
> > xml files is not same when using servicemix.xml or
> > xbean.xml.
> >
> > In the case servicemix.xml The service value (on
> the
> > endpoint element) HAS to be same in both endpoint
> > (producer and provider). However in the case of
> the
> > xbean.xml that you put in serviceunit the service
> > value CANNOT be the same.
> >
> > I was just wondering if some one could help me out
> > better understand this ?  Why is it like this ?
> >
> > Thx in advance.
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Servicemix-http additionnal info

Posted by Guillaume Nodet <gn...@gmail.com>.
The servicemix-http component configuration is the same, using
servicemix.xml or the SU deployment (xbean.xml).

I guess the confusion comes from the service / endpoint and
targetService / targetEndpoint attributes.  The service and endpoint
attributes are used to create an external JBI endpoint (that may be
refered to by other components as described in the JBI spec).  If the
targetService / targetEndpoint are not set, they will also be used as
the target for the JBI exchange.

Cheers,
Guillaume Nodet

On 4/27/06, Eric Dofonsou <ew...@yahoo.com> wrote:
> Hello guys
>
> I've got a question on how to configure
> servixemix-http endpoints in the xml files (for
> servicemix.xml and xbean.xml).
>
> I've noticed that the way endpoints are defined in the
> xml files is not same when using servicemix.xml or
> xbean.xml.
>
> In the case servicemix.xml The service value (on the
> endpoint element) HAS to be same in both endpoint
> (producer and provider). However in the case of the
> xbean.xml that you put in serviceunit the service
> value CANNOT be the same.
>
> I was just wondering if some one could help me out
> better understand this ?  Why is it like this ?
>
> Thx in advance.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>