You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Nirmal Fernando <ni...@gmail.com> on 2014/04/15 01:42:22 UTC
Fixing few usability issues with setting up Stratos
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.
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/
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
Jira: https://issues.apache.org/jira/browse/STRATOS-612
On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando <ni...@gmail.com>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.
>
> 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/
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
Thanks Nirmal - I've raised the JIRA for this.
On Wed, Apr 16, 2014 at 6:57 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Absolutely. On top of my head, all you have to change is the code at
> https://github.com/apache/incubator-stratos/tree/master/components/org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/broker
>
>
> On Wed, Apr 16, 2014 at 11:19 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Will do. It also sounds like a good one for me to work on :)
>>
>> On Wed, Apr 16, 2014 at 6:44 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > Ok.. and if it's license compatible we should try that out.
>> >
>> > Thanks Chris for the finding... you mind creating a jira and tag it to a
>> > future release?
>> >
>> >
>> > On Wed, Apr 16, 2014 at 11:10 PM, chris snow <ch...@gmail.com>
>> > wrote:
>> >>
>> >> RabbitMQ looks promising:
>> >>
>> >> > The RabbitMQ Java client library allows Java code to interface to
>> >> > AMQP
>> >> > servers. The library is platform neutral;
>> >> > ...
>> >> > The library is open-source, and is dual-licensed under the Mozilla
>> >> > Public License v1.1 and the GNU General Public License, v2.
>> >> > ...
>> >> > You will need an AMQP server, such as our very own RabbitMQ server,
>> >> > to
>> >> > use with the client library.
>> >>
>> >> Source: http://www.rabbitmq.com/java-client.html
>> >>
>> >> On Wed, Apr 16, 2014 at 6:37 PM, Nirmal Fernando
>> >> <ni...@gmail.com>
>> >> wrote:
>> >> > We need to find one it seems.
>> >> >
>> >> >
>> >> > On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> I was hoping there would be an opensource alternative to this:
>> >> >>
>> >> >> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP
>> >> >> > 1.0
>> >> >> > specification in Java and can be used to connect to any AMQP 1.0
>> >> >> > capable
>> >> >> > endpoints such as a SwiftMQ Router.
>> >> >>
>> >> >> Source:
>> >> >>
>> >> >>
>> >> >> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
>> >> >>
>> >> >> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando
>> >> >> <ni...@gmail.com>
>> >> >> wrote:
>> >> >> > Hi Chris,
>> >> >> >
>> >> >> >
>> >> >> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hi Nirmal, I agree that this is a future consideration.
>> >> >> >>
>> >> >> >> Do you mean what alternatives do we have for connecting to a AMQP
>> >> >> >> MQ,
>> >> >> >
>> >> >> >
>> >> >> > I meant the above.
>> >> >> >>
>> >> >> >> or what alternative MQ's we can use?
>> >> >> >>
>> >> >> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando
>> >> >> >> <ni...@gmail.com>
>> >> >> >> wrote:
>> >> >> >> > Hi Chris,
>> >> >> >> >
>> >> >> >> > That is possibly something to consider in a future release. If
>> >> >> >> > we
>> >> >> >> > avoid
>> >> >> >> > JNDI, what alternatives we have?
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow
>> >> >> >> > <ch...@gmail.com>
>> >> >> >> > wrote:
>> >> >> >> >>
>> >> >> >> >> 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
>> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> 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
>> >> >> >> >> > <ch...@gmail.com>
>> >> >> >> >> > 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
>> >> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> >> 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
>> >> >> >> >> >> > <di...@wso2.com>
>> >> >> >> >> >> > wrote:
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Hi Nirmal,
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> >> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> >> >> 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
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > 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
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > 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
>
>
>
>
> --
> 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
Absolutely. On top of my head, all you have to change is the code at
https://github.com/apache/incubator-stratos/tree/master/components/org.apache.stratos.messaging/src/main/java/org/apache/stratos/messaging/broker
On Wed, Apr 16, 2014 at 11:19 PM, chris snow <ch...@gmail.com> wrote:
> Will do. It also sounds like a good one for me to work on :)
>
> On Wed, Apr 16, 2014 at 6:44 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
> > Ok.. and if it's license compatible we should try that out.
> >
> > Thanks Chris for the finding... you mind creating a jira and tag it to a
> > future release?
> >
> >
> > On Wed, Apr 16, 2014 at 11:10 PM, chris snow <ch...@gmail.com>
> wrote:
> >>
> >> RabbitMQ looks promising:
> >>
> >> > The RabbitMQ Java client library allows Java code to interface to AMQP
> >> > servers. The library is platform neutral;
> >> > ...
> >> > The library is open-source, and is dual-licensed under the Mozilla
> >> > Public License v1.1 and the GNU General Public License, v2.
> >> > ...
> >> > You will need an AMQP server, such as our very own RabbitMQ server, to
> >> > use with the client library.
> >>
> >> Source: http://www.rabbitmq.com/java-client.html
> >>
> >> On Wed, Apr 16, 2014 at 6:37 PM, Nirmal Fernando <
> nirmal070125@gmail.com>
> >> wrote:
> >> > We need to find one it seems.
> >> >
> >> >
> >> > On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com>
> >> > wrote:
> >> >>
> >> >> I was hoping there would be an opensource alternative to this:
> >> >>
> >> >> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP
> 1.0
> >> >> > specification in Java and can be used to connect to any AMQP 1.0
> >> >> > capable
> >> >> > endpoints such as a SwiftMQ Router.
> >> >>
> >> >> Source:
> >> >>
> >> >>
> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
> >> >>
> >> >> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando
> >> >> <ni...@gmail.com>
> >> >> wrote:
> >> >> > Hi Chris,
> >> >> >
> >> >> >
> >> >> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> Hi Nirmal, I agree that this is a future consideration.
> >> >> >>
> >> >> >> Do you mean what alternatives do we have for connecting to a AMQP
> >> >> >> MQ,
> >> >> >
> >> >> >
> >> >> > I meant the above.
> >> >> >>
> >> >> >> or what alternative MQ's we can use?
> >> >> >>
> >> >> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando
> >> >> >> <ni...@gmail.com>
> >> >> >> wrote:
> >> >> >> > Hi Chris,
> >> >> >> >
> >> >> >> > That is possibly something to consider in a future release. If
> we
> >> >> >> > avoid
> >> >> >> > JNDI, what alternatives we have?
> >> >> >> >
> >> >> >> >
> >> >> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <
> chsnow123@gmail.com>
> >> >> >> > wrote:
> >> >> >> >>
> >> >> >> >> 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
> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> 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
> >> >> >> >> > <ch...@gmail.com>
> >> >> >> >> > 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
> >> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> >> 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
> >> >> >> >> >> > <di...@wso2.com>
> >> >> >> >> >> > wrote:
> >> >> >> >> >> >>
> >> >> >> >> >> >> Hi Nirmal,
> >> >> >> >> >> >>
> >> >> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
> >> >> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> >> >> 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
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> > --
> >> >> >> > 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
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > 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
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
Will do. It also sounds like a good one for me to work on :)
On Wed, Apr 16, 2014 at 6:44 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Ok.. and if it's license compatible we should try that out.
>
> Thanks Chris for the finding... you mind creating a jira and tag it to a
> future release?
>
>
> On Wed, Apr 16, 2014 at 11:10 PM, chris snow <ch...@gmail.com> wrote:
>>
>> RabbitMQ looks promising:
>>
>> > The RabbitMQ Java client library allows Java code to interface to AMQP
>> > servers. The library is platform neutral;
>> > ...
>> > The library is open-source, and is dual-licensed under the Mozilla
>> > Public License v1.1 and the GNU General Public License, v2.
>> > ...
>> > You will need an AMQP server, such as our very own RabbitMQ server, to
>> > use with the client library.
>>
>> Source: http://www.rabbitmq.com/java-client.html
>>
>> On Wed, Apr 16, 2014 at 6:37 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > We need to find one it seems.
>> >
>> >
>> > On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com>
>> > wrote:
>> >>
>> >> I was hoping there would be an opensource alternative to this:
>> >>
>> >> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP 1.0
>> >> > specification in Java and can be used to connect to any AMQP 1.0
>> >> > capable
>> >> > endpoints such as a SwiftMQ Router.
>> >>
>> >> Source:
>> >>
>> >> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
>> >>
>> >> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando
>> >> <ni...@gmail.com>
>> >> wrote:
>> >> > Hi Chris,
>> >> >
>> >> >
>> >> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi Nirmal, I agree that this is a future consideration.
>> >> >>
>> >> >> Do you mean what alternatives do we have for connecting to a AMQP
>> >> >> MQ,
>> >> >
>> >> >
>> >> > I meant the above.
>> >> >>
>> >> >> or what alternative MQ's we can use?
>> >> >>
>> >> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando
>> >> >> <ni...@gmail.com>
>> >> >> wrote:
>> >> >> > Hi Chris,
>> >> >> >
>> >> >> > That is possibly something to consider in a future release. If we
>> >> >> > avoid
>> >> >> > JNDI, what alternatives we have?
>> >> >> >
>> >> >> >
>> >> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> 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
>> >> >> >> <ni...@gmail.com>
>> >> >> >> 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
>> >> >> >> > <ch...@gmail.com>
>> >> >> >> > 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
>> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> 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
>> >> >> >> >> > <di...@wso2.com>
>> >> >> >> >> > wrote:
>> >> >> >> >> >>
>> >> >> >> >> >> Hi Nirmal,
>> >> >> >> >> >>
>> >> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> >> 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
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > 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
>> >
>> >
>> >
>> >
>> > --
>> > 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
Ok.. and if it's license compatible we should try that out.
Thanks Chris for the finding... you mind creating a jira and tag it to a
future release?
On Wed, Apr 16, 2014 at 11:10 PM, chris snow <ch...@gmail.com> wrote:
> RabbitMQ looks promising:
>
> > The RabbitMQ Java client library allows Java code to interface to AMQP
> servers. The library is platform neutral;
> > ...
> > The library is open-source, and is dual-licensed under the Mozilla
> Public License v1.1 and the GNU General Public License, v2.
> > ...
> > You will need an AMQP server, such as our very own RabbitMQ server, to
> use with the client library.
>
> Source: http://www.rabbitmq.com/java-client.html
>
> On Wed, Apr 16, 2014 at 6:37 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
> > We need to find one it seems.
> >
> >
> > On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com>
> wrote:
> >>
> >> I was hoping there would be an opensource alternative to this:
> >>
> >> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP 1.0
> >> > specification in Java and can be used to connect to any AMQP 1.0
> capable
> >> > endpoints such as a SwiftMQ Router.
> >>
> >> Source:
> >>
> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
> >>
> >> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando <
> nirmal070125@gmail.com>
> >> wrote:
> >> > Hi Chris,
> >> >
> >> >
> >> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Hi Nirmal, I agree that this is a future consideration.
> >> >>
> >> >> Do you mean what alternatives do we have for connecting to a AMQP MQ,
> >> >
> >> >
> >> > I meant the above.
> >> >>
> >> >> or what alternative MQ's we can use?
> >> >>
> >> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando
> >> >> <ni...@gmail.com>
> >> >> wrote:
> >> >> > Hi Chris,
> >> >> >
> >> >> > That is possibly something to consider in a future release. If we
> >> >> > avoid
> >> >> > JNDI, what alternatives we have?
> >> >> >
> >> >> >
> >> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> 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
> >> >> >> <ni...@gmail.com>
> >> >> >> 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 <
> chsnow123@gmail.com>
> >> >> >> > 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
> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> 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
> >> >> >> >> > <di...@wso2.com>
> >> >> >> >> > wrote:
> >> >> >> >> >>
> >> >> >> >> >> Hi Nirmal,
> >> >> >> >> >>
> >> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
> >> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> >> 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
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > 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
> >
> >
> >
> >
> > --
> > 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/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
RabbitMQ looks promising:
> The RabbitMQ Java client library allows Java code to interface to AMQP servers. The library is platform neutral;
> ...
> The library is open-source, and is dual-licensed under the Mozilla Public License v1.1 and the GNU General Public License, v2.
> ...
> You will need an AMQP server, such as our very own RabbitMQ server, to use with the client library.
Source: http://www.rabbitmq.com/java-client.html
On Wed, Apr 16, 2014 at 6:37 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> We need to find one it seems.
>
>
> On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com> wrote:
>>
>> I was hoping there would be an opensource alternative to this:
>>
>> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP 1.0
>> > specification in Java and can be used to connect to any AMQP 1.0 capable
>> > endpoints such as a SwiftMQ Router.
>>
>> Source:
>> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
>>
>> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > Hi Chris,
>> >
>> >
>> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Nirmal, I agree that this is a future consideration.
>> >>
>> >> Do you mean what alternatives do we have for connecting to a AMQP MQ,
>> >
>> >
>> > I meant the above.
>> >>
>> >> or what alternative MQ's we can use?
>> >>
>> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando
>> >> <ni...@gmail.com>
>> >> wrote:
>> >> > Hi Chris,
>> >> >
>> >> > That is possibly something to consider in a future release. If we
>> >> > avoid
>> >> > JNDI, what alternatives we have?
>> >> >
>> >> >
>> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> 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
>> >> >> <ni...@gmail.com>
>> >> >> 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 <ch...@gmail.com>
>> >> >> > 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
>> >> >> >> <ni...@gmail.com>
>> >> >> >> 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
>> >> >> >> > <di...@wso2.com>
>> >> >> >> > wrote:
>> >> >> >> >>
>> >> >> >> >> Hi Nirmal,
>> >> >> >> >>
>> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> >> >> >> <ni...@gmail.com>
>> >> >> >> >> 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
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > 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
>
>
>
>
> --
> 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
We need to find one it seems.
On Wed, Apr 16, 2014 at 11:03 PM, chris snow <ch...@gmail.com> wrote:
> I was hoping there would be an opensource alternative to this:
>
> > The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP 1.0
> specification in Java and can be used to connect to any AMQP 1.0 capable
> endpoints such as a SwiftMQ Router.
>
> Source:
> http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
>
> On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
> > Hi Chris,
> >
> >
> > On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com>
> wrote:
> >>
> >> Hi Nirmal, I agree that this is a future consideration.
> >>
> >> Do you mean what alternatives do we have for connecting to a AMQP MQ,
> >
> >
> > I meant the above.
> >>
> >> or what alternative MQ's we can use?
> >>
> >> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando <
> nirmal070125@gmail.com>
> >> wrote:
> >> > Hi Chris,
> >> >
> >> > That is possibly something to consider in a future release. If we
> avoid
> >> > JNDI, what alternatives we have?
> >> >
> >> >
> >> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
> >> > wrote:
> >> >>
> >> >> 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
> >> >> <ni...@gmail.com>
> >> >> 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 <ch...@gmail.com>
> >> >> > 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
> >> >> >> <ni...@gmail.com>
> >> >> >> 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 <
> dineshb@wso2.com>
> >> >> >> > wrote:
> >> >> >> >>
> >> >> >> >> Hi Nirmal,
> >> >> >> >>
> >> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
> >> >> >> >> <ni...@gmail.com>
> >> >> >> >> 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
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > 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
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
I was hoping there would be an opensource alternative to this:
> The SwiftMQ AMQP 1.0 Java Client is an implementation of the AMQP 1.0 specification in Java and can be used to connect to any AMQP 1.0 capable endpoints such as a SwiftMQ Router.
Source: http://www.swiftmq.com/products/router/swiftlets/sys_amqp/client/index.html
On Wed, Apr 16, 2014 at 6:29 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Hi Chris,
>
>
> On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com> wrote:
>>
>> Hi Nirmal, I agree that this is a future consideration.
>>
>> Do you mean what alternatives do we have for connecting to a AMQP MQ,
>
>
> I meant the above.
>>
>> or what alternative MQ's we can use?
>>
>> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>> > Hi Chris,
>> >
>> > That is possibly something to consider in a future release. If we avoid
>> > JNDI, what alternatives we have?
>> >
>> >
>> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
>> > wrote:
>> >>
>> >> 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
>> >> <ni...@gmail.com>
>> >> 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 <ch...@gmail.com>
>> >> > 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
>> >> >> <ni...@gmail.com>
>> >> >> 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 <di...@wso2.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hi Nirmal,
>> >> >> >>
>> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> >> >> <ni...@gmail.com>
>> >> >> >> 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
>> >
>> >
>> >
>> >
>> > --
>> > 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Chris,
On Wed, Apr 16, 2014 at 10:57 PM, chris snow <ch...@gmail.com> wrote:
> Hi Nirmal, I agree that this is a future consideration.
>
> Do you mean what alternatives do we have for connecting to a AMQP MQ,
>
I meant the above.
> or what alternative MQ's we can use?
>
> On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
> > Hi Chris,
> >
> > That is possibly something to consider in a future release. If we avoid
> > JNDI, what alternatives we have?
> >
> >
> > On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com>
> wrote:
> >>
> >> 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 <
> nirmal070125@gmail.com>
> >> 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 <ch...@gmail.com>
> >> > 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
> >> >> <ni...@gmail.com>
> >> >> 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 <di...@wso2.com>
> >> >> > wrote:
> >> >> >>
> >> >> >> Hi Nirmal,
> >> >> >>
> >> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
> >> >> >> <ni...@gmail.com>
> >> >> >> 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
> >
> >
> >
> >
> > --
> > 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/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
Hi Nirmal, I agree that this is a future consideration.
Do you mean what alternatives do we have for connecting to a AMQP MQ,
or what alternative MQ's we can use?
On Wed, Apr 16, 2014 at 6:22 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Hi Chris,
>
> That is possibly something to consider in a future release. If we avoid
> JNDI, what alternatives we have?
>
>
> On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com> wrote:
>>
>> 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 <ni...@gmail.com>
>> 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 <ch...@gmail.com>
>> > 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
>> >> <ni...@gmail.com>
>> >> 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 <di...@wso2.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi Nirmal,
>> >> >>
>> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> >> <ni...@gmail.com>
>> >> >> 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
>
>
>
>
> --
> 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Chris,
That is possibly something to consider in a future release. If we avoid
JNDI, what alternatives we have?
On Wed, Apr 16, 2014 at 10:45 PM, chris snow <ch...@gmail.com> wrote:
> 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 <ni...@gmail.com>
> 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 <ch...@gmail.com>
> 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 <
> nirmal070125@gmail.com>
> >> 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 <di...@wso2.com>
> >> > wrote:
> >> >>
> >> >> Hi Nirmal,
> >> >>
> >> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
> >> >> <ni...@gmail.com>
> >> >> 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
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
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 <ni...@gmail.com> 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 <ch...@gmail.com> 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 <ni...@gmail.com>
>> 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 <di...@wso2.com>
>> > wrote:
>> >>
>> >> Hi Nirmal,
>> >>
>> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando
>> >> <ni...@gmail.com>
>> >> 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
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 <ch...@gmail.com> 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 <ni...@gmail.com>
> 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 <di...@wso2.com>
> wrote:
> >>
> >> Hi Nirmal,
> >>
> >> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando <
> nirmal070125@gmail.com>
> >> 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/
Re: Fixing few usability issues with setting up Stratos
Posted by chris snow <ch...@gmail.com>.
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 <ni...@gmail.com> 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 <di...@wso2.com> wrote:
>>
>> Hi Nirmal,
>>
>> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando <ni...@gmail.com>
>> 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
Re: Fixing few usability issues with setting up Stratos
Posted by Nirmal Fernando <ni...@gmail.com>.
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 <di...@wso2.com> wrote:
> Hi Nirmal,
>
> On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando <ni...@gmail.com>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/
Re: Fixing few usability issues with setting up Stratos
Posted by Dinesh Bandara <di...@wso2.com>.
Hi Nirmal,
On Tue, Apr 15, 2014 at 5:12 AM, Nirmal Fernando <ni...@gmail.com>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