On Tue, Dec 14, 2010 at 7:24 AM, Danushka Menikkumbura <[email protected]>wrote:
> For an example if you take connection factories, in ActiveMQ, you just have > the JNDI name whereas in Qpid you have the format "connectionfactory.[JNDI > Name]". > In that case isn't it the user's responsibility to provide a complete, fully qualified JNDI object name? We can of course make it easier by providing some recommendations in the UI depending on the selected JMS provider. For instance when Qpid is stated as the broker, we can provide a text field partially filled with "connectionfactory." to specify the connection factory name. If we stick to the current approach, please change the url name parameter to something more meaningful like "JNDI Object Name Prefix". Thanks, Hiranya > > Danushka > > > On Tue, Dec 14, 2010 at 6:49 AM, Hiranya Jayathilaka <[email protected]>wrote: > >> Hi, >> >> On Tue, Dec 14, 2010 at 5:54 AM, Danushka Menikkumbura <[email protected] >> > wrote: >> >>> Hiranya, >>> >>> Actually Manjula's concern is how we deal with provider specific JNDI >>> name formats. >>> >> >> I'm still not getting it :( All we need to connect to a JMS provider is >> the initial context factory, provider URL and connection factory name. What >> are the other provider specific stuff that we should worry about? >> >> Thanks, >> Hiranya >> >> >>> >>> Danushka >>> >>> On Tue, Dec 14, 2010 at 12:21 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>>> >>>> >>>> On Mon, Dec 13, 2010 at 5:34 PM, Manjula Rathnayake >>>> <[email protected]>wrote: >>>> >>>>> Hi all, >>>>> >>>>> Here is how we can configure Qpid broker and ActiveMQ broker in broker >>>>> component. >>>>> >>>>> Qpid broker configuration: >>>>> >>>>> >>>>> java.naming.factory.initial = >>>>> org.apache.qpid.jndi.PropertiesFileInitialContextFactory >>>>> connectionfactory.Connection_Factory_Lookup_Name = >>>>> amqp://guest:gu...@clientid/test?brokerlist='tcp://localhost:5672' >>>>> Connection_Factory_Lookup_Name = any name >>>>> >>>>> *connectionfactory.*Connection_Factory_Lookup_Name; here * >>>>> connectionfactory.* is an essential part. >>>>> >>>>> >>>>> ActiveMQ broker configuration: >>>>> >>>>> >>>>> java.naming.factory.initial = >>>>> org.apache.activemq.jndi.ActiveMQInitialContextFactory >>>>> java.naming.provider.url = tcp://localhost:61616 >>>>> Connection_Factory_Lookup_Name = connectionFactory, >>>>> queueConnectionFactory, topicConnectionFactory >>>>> >>>>> So in broker component, we are going to provide UI for entering those >>>>> values. So are we providing any jms broker(Qpid, ActiveMQ, RabbitMQ...) to >>>>> be configured in broker component? >>>>> >>>> >>>> I guess we are going to ship Qpid? >>>> >>>> >>>>> >>>>> we can ask user to provide following properties to capture above >>>>> details. >>>>> factoryInitial >>>>> providerUrlName >>>>> providerUrlValue >>>>> connectionFactoryLookupName >>>>> >>>> >>>> I still don't get what provider URL name is. Can you please elaborate >>>> bit more on that. And why do we need that? As far as JMS/JNDI is concerned >>>> we should be able to use any JMS broker by using the same set of >>>> parameters. >>>> The JMS transport already does that. Also instead of the custom names given >>>> above, can we use the real names as specified in the JNDI specification? >>>> >>>> Thanks, >>>> Hiranya >>>> >>>> >>>>> >>>>> In current implementation, I have done as above. >>>>> >>>>> >>>>> Another option is to let user to select provider as ActiveMQ or Qpid, >>>>> then ask specific details. >>>>> >>>>> Any suggestions or ideas how to continue with this. >>>>> >>>>> Thank you. >>>>> >>>>> -- >>>>> Manjula Rathnayaka >>>>> Software Engineer >>>>> WSO2, Inc. >>>>> Mobile:+94 77 743 1987 >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Senior Software Engineer; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
