On Sun, Jan 16, 2011 at 12:20 PM, Afkham Azeez <[email protected]> wrote:
> > > On Sun, Jan 16, 2011 at 10:18 AM, Hiranya Jayathilaka <[email protected]>wrote: > >> Hi, >> >> On Sun, Jan 16, 2011 at 12:06 AM, Danushka Menikkumbura < >> [email protected]> wrote: >> >>> But the Axis2 JMS transport has nothing to do with Carbon or >>>> CarbonContext. Why do we have to force the users to go through this? As I >>>> said this is going to break a lot of existing stuff :( >>>> >>> >>> Hiranya, >>> >>> There was a long thread regarding this when it was first introduced but >>> it looks as if most of the folks still have not understood the fact that it >>> has not changed anything in the Axis2 JMS transport. >>> >> >> My concern is why the JMS transport is not working in the ESB with >> ActiveMQ? It should just work with the OOTB JMS configuration. If it's a >> matter of placing the ActiveMQ jars in a different location as Azeez has >> mentioned, then it is ok. >> >> > Why don't we make JMS transport a default one, and include it with Carbon > core so that all products automatically get it? > This will not solve the problem of getting JMS transport working with various JMS providers as Hiranya pointed out. Rajika
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
