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. 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
