You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Rajiv K Nistala <ra...@fiorano.com> on 2005/08/31 15:57:54 UTC
RE: Changing Sandesha client port - programmatically - BUG NOT COMPLETELY FIXED
Hi Chamikara Jayalath,
The bug is not completely fixed as there is reference to the
PropertyLoader.getClientSideListenerPort() in the URL generation also which
has not been corrected
sourceURL = Constants.HTTP + Constants.COLON + Constants.SLASH +
Constants.SLASH + addr.getHostAddress() +
Constants.COLON +
PropertyLoader.getClientSideListenerPort() +
Constants.URL_RM_SERVICE;
This is inside the following functions
private String initialize(Call call, String targetUrl, String action, short
MEP)
throws AxisFault
Regards,
Rajiv
_____
From: Chamikara Jayalath [mailto:chamikaramj@gmail.com]
Sent: Wednesday, August 31, 2005 4:15 PM
To: Rajiv K Nistala
Cc: sandesha-dev@ws.apache.org
Subject: Re: Changing Sandesha client port - programmatically
Hi Rajiv,
This was a bug and I fixed it. Now u can set the client side listner port as
given below,
SandeshaContext ctx = new SandeshaContext(new Integer(9091));
(could't go for constructor SaneshaContext(int) since there already was
one:-) ).
Please get the latest source code from
On 8/30/05, Rajiv K Nistala <ra...@fiorano.com> wrote:
Hi,
I am using Sandesha to invoke a the RM sample provided. I realise, that
there is a client listener port that is set which defaults to 9090. This I
know can be edited from the sandesha.properties file. But If I have to run
multiple instances of the sandesha client on the same machine, won't this
create a problem for me as all will be using 9090? Thus I was thinking
whether it is possible to programmatically change the client listener port
(if I can capture that as a command line argument). I saw that everything
related to that is private in the SandeshaContext and PropertyLoader
classes. Any suggestions if this is possible?
Also since sandesha.properties file is within the jar file, I can't even
overwrite the file. Please help.
Regards,
Rajiv K Nistala
Re: Changing Sandesha client port - programmatically - BUG NOT COMPLETELY FIXED
Posted by Chamikara Jayalath <ch...@gmail.com>.
Done. Please take an update.
Chamikara
On 8/31/05, Rajiv K Nistala <ra...@fiorano.com> wrote:
>
> Hi Chamikara Jayalath,
> The bug is not completely fixed as there is reference to the
> PropertyLoader.getClientSideListenerPort() in the URL generation also
> which has not been corrected
> sourceURL = Constants.HTTP + Constants.COLON + Constants.SLASH +
> Constants.SLASH + addr.getHostAddress() + Constants.COLON +
> PropertyLoader.getClientSideListenerPort() + Constants.URL_RM_SERVICE;
> This is inside the following functions
> private String initialize(Call call, String targetUrl, String action,
> short MEP)
> throws AxisFault
> Regards,
> Rajiv
>
> ------------------------------
> *From:* Chamikara Jayalath [mailto:chamikaramj@gmail.com]
> *Sent:* Wednesday, August 31, 2005 4:15 PM
> *To:* Rajiv K Nistala
> *Cc:* sandesha-dev@ws.apache.org
> *Subject:* Re: Changing Sandesha client port - programmatically
>
> Hi Rajiv,
> This was a bug and I fixed it. Now u can set the client side listner port
> as given below,
> SandeshaContext ctx = new SandeshaContext(new Integer(9091));
>
> (could't go for constructor SaneshaContext(int) since there already was
> one:-) ).
> Please get the latest source code from
>
>
>
> On 8/30/05, Rajiv K Nistala <ra...@fiorano.com> wrote:
> >
> > Hi,
> >
> > I am using Sandesha to invoke a the RM sample provided. I realise, that
> > there is a client listener port that is set which defaults to 9090. This I
> > know can be edited from the sandesha.properties file. But If I have to
> > run multiple instances of the sandesha client on the same machine, won't
> > this create a problem for me as all will be using 9090? Thus I was thinking
> > whether it is possible to programmatically change the client listener port
> > (if I can capture that as a command line argument). I saw that everything
> > related to that is private in the SandeshaContext and PropertyLoader
> > classes. Any suggestions if this is possible?
> >
> > Also since sandesha.properties file is within the jar file, I can't even
> > overwrite the file. Please help.
> >
> > Regards,
> > Rajiv K Nistala
> >
>
>
Re: Changing Sandesha client port - programmatically - BUG NOT COMPLETELY FIXED
Posted by Chamikara Jayalath <ch...@gmail.com>.
Done. Please take an update.
Chamikara
On 8/31/05, Rajiv K Nistala <ra...@fiorano.com> wrote:
>
> Hi Chamikara Jayalath,
> The bug is not completely fixed as there is reference to the
> PropertyLoader.getClientSideListenerPort() in the URL generation also
> which has not been corrected
> sourceURL = Constants.HTTP + Constants.COLON + Constants.SLASH +
> Constants.SLASH + addr.getHostAddress() + Constants.COLON +
> PropertyLoader.getClientSideListenerPort() + Constants.URL_RM_SERVICE;
> This is inside the following functions
> private String initialize(Call call, String targetUrl, String action,
> short MEP)
> throws AxisFault
> Regards,
> Rajiv
>
> ------------------------------
> *From:* Chamikara Jayalath [mailto:chamikaramj@gmail.com]
> *Sent:* Wednesday, August 31, 2005 4:15 PM
> *To:* Rajiv K Nistala
> *Cc:* sandesha-dev@ws.apache.org
> *Subject:* Re: Changing Sandesha client port - programmatically
>
> Hi Rajiv,
> This was a bug and I fixed it. Now u can set the client side listner port
> as given below,
> SandeshaContext ctx = new SandeshaContext(new Integer(9091));
>
> (could't go for constructor SaneshaContext(int) since there already was
> one:-) ).
> Please get the latest source code from
>
>
>
> On 8/30/05, Rajiv K Nistala <ra...@fiorano.com> wrote:
> >
> > Hi,
> >
> > I am using Sandesha to invoke a the RM sample provided. I realise, that
> > there is a client listener port that is set which defaults to 9090. This I
> > know can be edited from the sandesha.properties file. But If I have to
> > run multiple instances of the sandesha client on the same machine, won't
> > this create a problem for me as all will be using 9090? Thus I was thinking
> > whether it is possible to programmatically change the client listener port
> > (if I can capture that as a command line argument). I saw that everything
> > related to that is private in the SandeshaContext and PropertyLoader
> > classes. Any suggestions if this is possible?
> >
> > Also since sandesha.properties file is within the jar file, I can't even
> > overwrite the file. Please help.
> >
> > Regards,
> > Rajiv K Nistala
> >
>
>