Is there any reason to keep using JNDI? It seems to tie us to using Java based MQs.
On Wed, Apr 16, 2014 at 6:02 PM, Nirmal Fernando <[email protected]> wrote: > Hi Chris, > > I think it's mainly due to the fact that all Stratos components are Java > based. > > > On Wed, Apr 16, 2014 at 10:27 PM, chris snow <[email protected]> wrote: >> >> Why are we using JNDI to connect to AMQP? Is JNDI not just a legacy >> from how we had to connect to JMS? >> >> >> On Wed, Apr 16, 2014 at 2:23 PM, Nirmal Fernando <[email protected]> >> wrote: >> > Dinesh, >> > >> > I too thought of that, but then the problem is we should use that in all >> > the >> > places, like for an example it's not right to have activemq configs hard >> > coded if we introduce a mb_type. >> > >> > This is quite easy for a user, you can keep the jndi.properties file >> > where >> > you want. >> > >> > >> > On Wed, Apr 16, 2014 at 1:48 PM, Dinesh Bandara <[email protected]> >> > wrote: >> >> >> >> Hi Nirmal, >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando >> >> <[email protected]> >> >> wrote: >> >>> >> >>> Hi All, >> >>> >> >>> Identified following usability issues when setting up Stratos in a >> >>> distributed manner in a single machine. >> >>> >> >>> 1. All the packs getting extracted to one path, unless you change in >> >>> the >> >>> setup.conf each time you start a new profile. >> >>> >> >>> - fix is to append the profile name as a suffix to the extracted >> >>> folder's >> >>> name >> >>> >> >>> 2. Port offset also has to be configured using setup.conf each time >> >>> you >> >>> start a new server in the same machine. >> >>> >> >>> - fix is to take port offset as an argument to the setup.sh, so if you >> >>> prefer that you can use that instead of editing setup.conf each time. >> >>> >> >>> 3. MB jndi properties file should be taken from setup.conf instead of >> >>> hard coding. >> >>> >> >>> - fix is to introduce a new variable in setup.conf. By default it is >> >>> set >> >>> to activemq default jndi.properties file. >> >>> >> >> Instead of adding full path to jndi.properties in setup.conf, shall we >> >> introduce MB type or name which we are going to use. As an example >> >> "activemq". If so we can simply copy relevant jndi.properties from >> >> <setup_path>/config/all/repository/conf/<mb-type>/jndi.properties >> >> >> >>> 4. Copy MB client libs, if user would like to provide a path to client >> >>> libs. (important if you plug in a different MB) >> >>> >> >>> - fix is to prompt a question asking for a folder path to MB client >> >>> libs, >> >>> in non-silent mode. >> >>> >> >>> Let me know, if there's any objections. >> >>> >> >>> -- >> >>> Best Regards, >> >>> Nirmal >> >>> >> >>> Nirmal Fernando. >> >>> PPMC Member & Committer of Apache Stratos, >> >>> Senior Software Engineer, WSO2 Inc. >> >>> >> >>> Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> >> >> >> >> >> >> -- >> >> Dinesh Bandara >> >> Software Engineer >> >> WSO2 Inc.; http://wso2.com >> >> lean.enterprise.middleware >> >> >> > >> > >> > >> > -- >> > Best Regards, >> > Nirmal >> > >> > Nirmal Fernando. >> > PPMC Member & Committer of Apache Stratos, >> > Senior Software Engineer, WSO2 Inc. >> > >> > Blog: http://nirmalfdo.blogspot.com/ >> >> >> >> -- >> Check out my professional profile and connect with me on LinkedIn. >> http://lnkd.in/cw5k69 > > > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
