You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by ffrenchm <ff...@gmail.com> on 2009/06/30 11:52:50 UTC

JBI JMS component and LW JMS component

Hello,

I discovered that there is two JMS BC (JBI and LW) and I'm not sure to
understand the reasons of these two differents implementations from a JMS /
JBI exchange point of view. Are these two implementations achieving the same
goals ? Could you explain me the reasons of LW components ? Is that just a
question of configuration and deployment ? Are the JBI components not enough
?

Thanks for all.
-- 
View this message in context: http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24269118.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: JBI JMS component and LW JMS component

Posted by ffrenchm <ff...@gmail.com>.
Hello,

thanks for your answers... I've another questions about the jms provider
endpoint : does it manage transaction ? As far as I read the source code
I've the impression there is no transaction managed by this endpoint... Am I
false ? 

Thanks for all


Gert Vanthienen wrote:
> 
> L.S.,
> 
> You're right, the lightweight components have been deprecated in favor
> of the full JBI-compliant components.  The servicemix-lwcontainer
> component is no longer supported in ServiceMix 4 and any new
> development is going into the servicemix-jms component, so I would
> definitely recommend you to start using that one.  A few versions ago,
> this component got a new set of consumer/provider endpoints (cfr.
> http://servicemix.apache.org/servicemix-jms-new-endpoints.html). A bit
> more work has been done for the latest release to even better support
> the different kinds of MEPs, transactional behavior and integration
> with SMX4/OSGi (cfr.
> http://servicemix.apache.org/servicemix-jms-200901.html)
> 
> Regards,
> 
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
> 
> 
> 
> 2009/6/30 ffrenchm <ff...@gmail.com>:
>>
>> After some research I discovered that LW components are deprecated.
>> Anyway I
>> try to check the differences between JBI JMS BC and LW JMS BC and I've
>> the
>> impression there are greats improvements in the JBI JMS BC considering
>> the
>> JMS exchange <-> JMS flow implementations. I would like to know if there
>> is
>> some release note which summarize these kind of changes ...
>>
>> Thanks
>>
>>
>> ffrenchm wrote:
>>>
>>> Hello,
>>>
>>> I discovered that there is two JMS BC (JBI and LW) and I'm not sure to
>>> understand the reasons of these two differents implementations from a
>>> JMS
>>> / JBI exchange point of view. Are these two implementations achieving
>>> the
>>> same goals ? Could you explain me the reasons of LW components ? Is that
>>> just a question of configuration and deployment ? Are the JBI components
>>> not enough ?
>>>
>>> Thanks for all.
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24273123.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> ---
> Gert Vanthienen
> http://gertvanthienen.blogspot.com
> 

-- 
View this message in context: http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24323848.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: JBI JMS component and LW JMS component

Posted by ffrenchm <ff...@gmail.com>.
Another question :) For the jms basic consumer endpoint and the jms soap
consumer you define a parameter to set the transaction type. In the case I
want XA transaction with this kind of endpoint what will be the resource
adapter used by this endpoint ? 

Thanks 


Gert Vanthienen wrote:
> 
> L.S.,
> 
> You're right, the lightweight components have been deprecated in favor
> of the full JBI-compliant components.  The servicemix-lwcontainer
> component is no longer supported in ServiceMix 4 and any new
> development is going into the servicemix-jms component, so I would
> definitely recommend you to start using that one.  A few versions ago,
> this component got a new set of consumer/provider endpoints (cfr.
> http://servicemix.apache.org/servicemix-jms-new-endpoints.html). A bit
> more work has been done for the latest release to even better support
> the different kinds of MEPs, transactional behavior and integration
> with SMX4/OSGi (cfr.
> http://servicemix.apache.org/servicemix-jms-200901.html)
> 
> Regards,
> 
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
> 
> 
> 
> 2009/6/30 ffrenchm <ff...@gmail.com>:
>>
>> After some research I discovered that LW components are deprecated.
>> Anyway I
>> try to check the differences between JBI JMS BC and LW JMS BC and I've
>> the
>> impression there are greats improvements in the JBI JMS BC considering
>> the
>> JMS exchange <-> JMS flow implementations. I would like to know if there
>> is
>> some release note which summarize these kind of changes ...
>>
>> Thanks
>>
>>
>> ffrenchm wrote:
>>>
>>> Hello,
>>>
>>> I discovered that there is two JMS BC (JBI and LW) and I'm not sure to
>>> understand the reasons of these two differents implementations from a
>>> JMS
>>> / JBI exchange point of view. Are these two implementations achieving
>>> the
>>> same goals ? Could you explain me the reasons of LW components ? Is that
>>> just a question of configuration and deployment ? Are the JBI components
>>> not enough ?
>>>
>>> Thanks for all.
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24273123.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> ---
> Gert Vanthienen
> http://gertvanthienen.blogspot.com
> 

-- 
View this message in context: http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24324434.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: JBI JMS component and LW JMS component

Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,

You're right, the lightweight components have been deprecated in favor
of the full JBI-compliant components.  The servicemix-lwcontainer
component is no longer supported in ServiceMix 4 and any new
development is going into the servicemix-jms component, so I would
definitely recommend you to start using that one.  A few versions ago,
this component got a new set of consumer/provider endpoints (cfr.
http://servicemix.apache.org/servicemix-jms-new-endpoints.html). A bit
more work has been done for the latest release to even better support
the different kinds of MEPs, transactional behavior and integration
with SMX4/OSGi (cfr.
http://servicemix.apache.org/servicemix-jms-200901.html)

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/6/30 ffrenchm <ff...@gmail.com>:
>
> After some research I discovered that LW components are deprecated. Anyway I
> try to check the differences between JBI JMS BC and LW JMS BC and I've the
> impression there are greats improvements in the JBI JMS BC considering the
> JMS exchange <-> JMS flow implementations. I would like to know if there is
> some release note which summarize these kind of changes ...
>
> Thanks
>
>
> ffrenchm wrote:
>>
>> Hello,
>>
>> I discovered that there is two JMS BC (JBI and LW) and I'm not sure to
>> understand the reasons of these two differents implementations from a JMS
>> / JBI exchange point of view. Are these two implementations achieving the
>> same goals ? Could you explain me the reasons of LW components ? Is that
>> just a question of configuration and deployment ? Are the JBI components
>> not enough ?
>>
>> Thanks for all.
>>
>
> --
> View this message in context: http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24273123.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>

Re: JBI JMS component and LW JMS component

Posted by ffrenchm <ff...@gmail.com>.
After some research I discovered that LW components are deprecated. Anyway I
try to check the differences between JBI JMS BC and LW JMS BC and I've the
impression there are greats improvements in the JBI JMS BC considering the
JMS exchange <-> JMS flow implementations. I would like to know if there is
some release note which summarize these kind of changes ...

Thanks


ffrenchm wrote:
> 
> Hello,
> 
> I discovered that there is two JMS BC (JBI and LW) and I'm not sure to
> understand the reasons of these two differents implementations from a JMS
> / JBI exchange point of view. Are these two implementations achieving the
> same goals ? Could you explain me the reasons of LW components ? Is that
> just a question of configuration and deployment ? Are the JBI components
> not enough ?
> 
> Thanks for all.
> 

-- 
View this message in context: http://www.nabble.com/JBI-JMS-component-and-LW-JMS-component-tp24269118p24273123.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: SU using smx-mail component

Posted by Lars Heinemann <lh...@apache.org>.
Well I think some of the archetypes may be outdated a bit. We need to
track such problems and open JIRA's for them.

Regards
Lars


2009/6/30 Madesclair Vivian <vm...@sopragroup.com>:
> Ulhas,
>
> Thank you, I specified the version in the dependency (change from ${servicemix-version} to 2009.01) and the build is now successful.
>
> But then is it normal that in http components the version is ${servicemix-version} and not 2009.01 ? (maven create define this version automatically)
>
> Thanks for you help
> Vivian
>
>
> -----Message d'origine-----
> De : Ulhas Bhole [mailto:ulhas.bhole@progress.com]
> Envoyé : mardi 30 juin 2009 17:09
> À : users@servicemix.apache.org
> Objet : Re: SU using smx-mail component
>
> I think servicemix-mail component version should be 2008.01 or 2009.01 it can't be 3.2.3. Did you specify version number in you maven dependency correctly?
>
> -- Ulhas
> Madesclair Vivian wrote:
>> Hello,
>>
>> I am trying to use the mail component of servicemix, but I can't even
>> create the SU. I am using servicemix 3.3 (downloaded via FUSE 3.4)
>>
>> First, I tried the command given on the smx-mail wiki page
>> (http://servicemix.apache.org/servicemix-mail.html). This throws an
>> error (mail-mvn-error.txt) saying "Requested download does not exist.
>> Unable to determine the release version".
>>
>> Then I tried to create a sample SU with maven and adapt it for a mail
>> SU. But when I run the "install" maven command, I also get an error
>> (mail-mvn-error2.txt) saying "Failed to resolve artifact".
>>
>> I noticed on this occasion that I usually use servicemix-version=3.2.3
>> (which is the default when mvn create a new SU) in my poms while the
>> mail connector can only be used for version 3.3 and newer. But even
>> trying other versions, I couldn't install.
>>
>> Is the mail component available? On which version? Or is there
>> something wrong in my pom and/or xbean? (Which I can provide if
>> needed)
>>
>>
>> Regards,
>> Vivian
>>
>
>



-- 
http://lhein.blogspot.com

RE: SU using smx-mail component

Posted by Madesclair Vivian <vm...@sopragroup.com>.
Ulhas,

Thank you, I specified the version in the dependency (change from ${servicemix-version} to 2009.01) and the build is now successful.

But then is it normal that in http components the version is ${servicemix-version} and not 2009.01 ? (maven create define this version automatically)

Thanks for you help
Vivian


-----Message d'origine-----
De : Ulhas Bhole [mailto:ulhas.bhole@progress.com] 
Envoyé : mardi 30 juin 2009 17:09
À : users@servicemix.apache.org
Objet : Re: SU using smx-mail component

I think servicemix-mail component version should be 2008.01 or 2009.01 it can't be 3.2.3. Did you specify version number in you maven dependency correctly?

-- Ulhas
Madesclair Vivian wrote:
> Hello,
>
> I am trying to use the mail component of servicemix, but I can't even 
> create the SU. I am using servicemix 3.3 (downloaded via FUSE 3.4)
>
> First, I tried the command given on the smx-mail wiki page 
> (http://servicemix.apache.org/servicemix-mail.html). This throws an 
> error (mail-mvn-error.txt) saying "Requested download does not exist.
> Unable to determine the release version".
>
> Then I tried to create a sample SU with maven and adapt it for a mail 
> SU. But when I run the "install" maven command, I also get an error
> (mail-mvn-error2.txt) saying "Failed to resolve artifact".
>
> I noticed on this occasion that I usually use servicemix-version=3.2.3 
> (which is the default when mvn create a new SU) in my poms while the 
> mail connector can only be used for version 3.3 and newer. But even 
> trying other versions, I couldn't install.
>
> Is the mail component available? On which version? Or is there 
> something wrong in my pom and/or xbean? (Which I can provide if 
> needed)
>
>
> Regards,
> Vivian
>

Re: SU using smx-mail component

Posted by Ulhas Bhole <ul...@progress.com>.
I think servicemix-mail component version should be 2008.01 or 2009.01 
it can't be 3.2.3. Did you specify version number in you maven 
dependency correctly?

-- Ulhas
Madesclair Vivian wrote:
> Hello,
>
> I am trying to use the mail component of servicemix, but I can't even
> create the SU. I am using servicemix 3.3 (downloaded via FUSE 3.4)
>
> First, I tried the command given on the smx-mail wiki page
> (http://servicemix.apache.org/servicemix-mail.html). This throws an
> error (mail-mvn-error.txt) saying "Requested download does not exist.
> Unable to determine the release version".
>
> Then I tried to create a sample SU with maven and adapt it for a mail
> SU. But when I run the "install" maven command, I also get an error
> (mail-mvn-error2.txt) saying "Failed to resolve artifact".
>
> I noticed on this occasion that I usually use servicemix-version=3.2.3
> (which is the default when mvn create a new SU) in my poms while the
> mail connector can only be used for version 3.3 and newer. But even
> trying other versions, I couldn't install.
>
> Is the mail component available? On which version? Or is there something
> wrong in my pom and/or xbean? (Which I can provide if needed)
>
>
> Regards,
> Vivian
>

SU using smx-mail component

Posted by Madesclair Vivian <vm...@sopragroup.com>.
Hello,

I am trying to use the mail component of servicemix, but I can't even
create the SU. I am using servicemix 3.3 (downloaded via FUSE 3.4)

First, I tried the command given on the smx-mail wiki page
(http://servicemix.apache.org/servicemix-mail.html). This throws an
error (mail-mvn-error.txt) saying "Requested download does not exist.
Unable to determine the release version".

Then I tried to create a sample SU with maven and adapt it for a mail
SU. But when I run the "install" maven command, I also get an error
(mail-mvn-error2.txt) saying "Failed to resolve artifact".

I noticed on this occasion that I usually use servicemix-version=3.2.3
(which is the default when mvn create a new SU) in my poms while the
mail connector can only be used for version 3.3 and newer. But even
trying other versions, I couldn't install.

Is the mail component available? On which version? Or is there something
wrong in my pom and/or xbean? (Which I can provide if needed)


Regards,
Vivian