On Wed, Mar 16, 2011 at 4:18 PM, Danushka Menikkumbura <[email protected]>wrote:
> Hi, > > The requirement is to install the Qpid (client) feature and configure JMS > transport as usual to work with the MB. The issue here is that if you > install it as a feature the libs get install into > repository/components/plugin so that classes will not be visible to the > CarbonContext. > > Senaka, do we have a fix for this?. It is not an issue anymore?. > As discussed today, we cannot install this into plugins, and must install it into the webapp classpath. The reason is that JMS is based on JNDI, and JNDI is a top-level concept spanning across OSGi and non-OSGi (webapps) portions of the Carbon platform. Due to this reason, in order to avoid class-loading issues, we need to copy the libs into the carbon webapp's classpath. Unless we follow this approach, we cannot achieve proper MT in the JNDI/JMS layers. Now, having said that, I believe that it is possible to write features that will install jars into the webapp classpath. Also, not all of the jars required by the MB component need to be on the webapp classpath, and it will be only those that provide APIs, or ones containing classes that will be dynamically loaded. HTH. Thanks, Senaka. > > Thanks, > Danushka > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
