That means we should avoid using the global context in the JMS transport? Danushka
On Thu, Mar 17, 2011 at 12:51 PM, Paul Fremantle <[email protected]> wrote: > So let's be clear about JNDI here: > > JNDI will be used to by the JMS client to access queues in two scenarios: > > 1) ESB is using JMS. Normally we provide our own JNDI settings to the Axis2 > JMS transport. Maybe this needs improving, but this is the way. > > 2) If I use JMS in a webapp. So far we haven't really looked at this > scenario. I want to improve this, but at the moment it is lower on the > priority list to the ESB. > > Basically we are not using a global JNDI at this point, except for data > sources. > > Paul > > > On 16 March 2011 20:14, Paul Fremantle <[email protected]> wrote: > >> Senaka >> >> I agree having a single JNDI across webapps and within OSGi is useful. But >> its not completely necessary I believe. >> >> I don't know enough about JNDI to answer to part 2 I'm afraid! >> >> Paul >> >> >> On 16 March 2011 19:20, Senaka Fernando <[email protected]> wrote: >> >>> Hi Paul, >>> >>> On Thu, Mar 17, 2011 at 12:37 AM, Paul Fremantle <[email protected]> wrote: >>> >>>> Senaka >>>> >>>> Can't we have our own "Carbon" JNDI which is just used within Carbon? I >>>> don't see why we need to have a single JNDI that spans across both. >>>> >>> >>> There were two reasons. >>> >>> 1. According to older discussions with Azeez et al, JNDI spanning across >>> both webapps and carbon, is useful for having shared datasources, and its >>> required for having a single-LDAP. Use of JNDI is so broad, to locally solve >>> the problems WRT JMS. >>> >>> 2. By design, JNDI can be taken control of only by getting hold of the >>> InitialContextFactoryBuilder in the NamingManager. There can only be one >>> instance of these. Therefore, eventhough we isolate, Carbon-JNDI from >>> webapp-JNDI, we will still need to have the classes on a single classpath to >>> avoid classloader constraints. So, we don't have an option when it comes to >>> placing libraries, AFAIU. >>> >>> Thanks, >>> Senaka. >>> >>>> >>>> Paul >>>> >>>> >>>> On 16 March 2011 18:46, Senaka Fernando <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> 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: <%2B1%20408%20754%207388> >>>>> <%2B1%20408%20754%207388><%2B1%20408%20754%207388>+1 >>>>> 408 754 7388; ext: 51736*; *M: >>>>> <%2B94%2077%20322%201818><%2B94%2077%20322%201818><%2B94%2077%20322%201818>+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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Paul Fremantle >>>> CTO and Co-Founder, WSO2 >>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse >>>> >>>> Office: <%2B44%20844%20484%208143> >>>> <%2B44%20844%20484%208143><%2B44%20844%20484%208143>+44 >>>> 844 484 8143 >>>> Cell: <%2B44%20798%20447%204618> >>>> <%2B44%20798%20447%204618><%2B44%20798%20447%204618>+44 >>>> 798 447 4618 >>>> >>>> blog: http://pzf.fremantle.org >>>> twitter.com/pzfreo >>>> [email protected] >>>> >>>> wso2.com Lean Enterprise Middleware >>>> >>>> Disclaimer: This communication may contain privileged or other >>>> confidential information and is intended exclusively for the addressee/s. >>>> If >>>> you are not the intended recipient/s, or believe that you may have received >>>> this communication in error, please reply to the sender indicating that >>>> fact >>>> and delete the copy you received and in addition, you should not print, >>>> copy, retransmit, disseminate, or otherwise use the information contained >>>> in >>>> this communication. Internet communications cannot be guaranteed to be >>>> timely, secure, error or virus-free. The sender does not accept liability >>>> for any errors or omissions. >>>> >>> >>> >>> >>> -- >>> *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: <%2B1%20408%20754%207388> <%2B1%20408%20754%207388>+1 408 754 7388; >>> ext: 51736*; *M: <%2B94%2077%20322%201818> <%2B94%2077%20322%201818>+94 >>> 77 322 1818 >>> Linked-In: http://www.linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, VP, Apache Synapse >> >> Office: +44 844 484 8143 >> Cell: +44 798 447 4618 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> [email protected] >> >> wso2.com Lean Enterprise Middleware >> >> Disclaimer: This communication may contain privileged or other >> confidential information and is intended exclusively for the addressee/s. If >> you are not the intended recipient/s, or believe that you may have received >> this communication in error, please reply to the sender indicating that fact >> and delete the copy you received and in addition, you should not print, >> copy, retransmit, disseminate, or otherwise use the information contained in >> this communication. Internet communications cannot be guaranteed to be >> timely, secure, error or virus-free. The sender does not accept liability >> for any errors or omissions. >> > > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > [email protected] > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other confidential > information and is intended exclusively for the addressee/s. If you are not > the intended recipient/s, or believe that you may have received this > communication in error, please reply to the sender indicating that fact and > delete the copy you received and in addition, you should not print, copy, > retransmit, disseminate, or otherwise use the information contained in this > communication. Internet communications cannot be guaranteed to be timely, > secure, error or virus-free. The sender does not accept liability for any > errors or omissions. > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
