Hi Kasun, AFAIK we can only explicitly disable a transport with current implementation. so user have to update each and every deployed service mentioning what he don't want.
So my point here is user should allow to select what he want on some way (it can be through a UI or services.xml file) and not to select what he don't want. On Mon, Aug 12, 2013 at 10:47 AM, Kasun Gajasinghe <[email protected]> wrote: > > > > On Mon, Aug 12, 2013 at 10:30 AM, Ishara Premadasa <[email protected]>wrote: > >> Hi, >> >> >> On Fri, Aug 9, 2013 at 7:09 PM, Kasun Gajasinghe <[email protected]> wrote: >> >>> hi Asanka, >>> >>> If you enable a transport globally via axis2.xml, then all services >>> inherit that. I thinm this is by design. We can't force the user to >>> re-enable needed transports per service after enabling it globally. >>> >>> You can explicitly set the transports exposed by a service via its >>> services.xml. Further, in the case of JMS, I think user have to define a >>> jndi property per service to map jndi name to jms queue via >>> repo/conf/jndi.properties. If you did not set this property, then the JMS >>> transport is effectively disabled for that service. That was the case at >>> least in previous releases in both AS and ESB. I believe this is a >>> limitation with MB since it does not support dynamic queues. >>> >> >> With the previous releases in both AS and ESB, if you do not add queue >> name into repo/conf/jndi.properties file, JMS transport will not be >> disabled for that service, instead it will try to create a queue for the >> service/proxy and throw error 'java.lang.UnsupportedOperationException: >> The new addressing based sytanx is not supported for AMQP 0-8/0-9 >> versions'since queue is not defined. But for the new releases of both >> products >> onwards, WSO2 MB now supports dynamic queues [1]. Which means you don't >> need to manually define the queue names in jndi.properties file and queues >> will be created at the server start up for each proxy or service. >> > > Cool. It's good to hear that we have dynamic queue support now. > > >> >> As i know you can't selectively enable jms transport for services >> therefore for each AS service it will dynamically create a queue named >> after that service. I have seen that this is common in other message >> brokers as well which provides dynamic queue support. >> >> > Can't we explicitly enable/disable jms via services.xml? > > >> Thanks! >> Ishara >> >> [1] >> http://isharapremadasa.blogspot.com/2013/07/providing-dynamic-queue-support-when.html >> >> >>> >>> >>> On Friday, August 9, 2013, Asanka Vithanage <[email protected]> wrote: >>> > Hi All, >>> > >>> > When enable the JMS transport on axis2.xml as specified on [1]. All >>> the deployed services enable the the JMS transport.so we can see every >>> service creating an queue on message broker. >>> > IMO this should not happen. >>> > >>> > Further suppose a situation like AS have 10 services deployed and user >>> wants to deploy a new service which needs listen to an queue. In this kind >>> of situation user needs to update all previous services, simply he has to >>> go to Tranport management (Home> Manage> Services> List> Service Dashboard> >>> Transport Management) page of each and every service and remove JMS >>> transport manually. >>> > >>> > As i see after enabled the JMS transport on global level, user should >>> allow to select required transport on each service level. As we do on ESB >>> proxy. >>> > >>> > WDYT? >>> > >>> > Note: >>> > This concern is valid for other Transports as well. >>> > >>> > >>> > >>> > [1] http://docs.wso2.org/wiki/display/MB210/Integrating+WSO2+AS >>> > >>> > -- >>> > Asanka Vithanage >>> > Senior Software Engineer -QA >>> > Mobile: +94 0716286708 >>> > Email: [email protected] >>> > WSO2 Inc. www.wso2.com >>> > >>> > >>> >>> -- >>> ~~--~~ >>> Sending this mail via my phone. Do excuse any typo or short replies >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Ishara Premasada >> Software Engineer, >> WSO2 Inc. http://wso2.com/ >> *Blog : http://isharapremadasa.blogspot.com/ >> Twitter : https://twitter.com/ishadil >> Mobile : +94 714445832* >> >> >> > > > -- > *Kasun Gajasinghe* > Software Engineer; > Development Technologies Team, WSO2 Inc.; http://wso2.com > > > , > *email: **kasung AT spamfree wso2.com > > > ** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe > > > * > * > *blog: **http://kasunbg.org* <http://kasunbg.org> > > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > > * > * > -- Asanka Vithanage Senior Software Engineer -QA Mobile: +94 0716286708 Email: [email protected] WSO2 Inc. www.wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
