[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-c-user
Subject: Re: Client configuration without axiscpp.conf?
From: Tim Bartley <tbartley () au1 ! ibm ! com>
Date: 2005-02-10 23:23:36
Message-ID: OFAF8495EF.9B97E580-ON4A256FA4.007E5C08-4A256FA4.0080811B () au1 ! ibm ! com
[Download RAW message or body]
This is a multipart message in MIME format.
--=_alternative 0080809B4A256FA4_=
Content-Type: text/plain; charset="US-ASCII"
I was going to suggest that simply being able to specify the location of
the config file programatically would be enough for me for now but that's
not quite right. The other requirement I have is really to have multiple
independent instances of the Axis client in a single process.
I.e. I'd like the class defined in Axis.hpp to be a real class and not a
namespace for the initialize method. This must be a useful thing anyway -
how can an Axis C++ server also act as a client?
I couldn't work out how to edit the wish list - it alsways told me I
wasn't permitted - even after creating a profile etc so I've opened a
couple of JIRA issues.
Thanks,
Tim
--
IBM Tivoli Access Manager Development
Gold Coast Development Lab, Australia
+61-7-5552-4001 phone
+61-7-5571-0420 fax
Samisa Abeysinghe <samisa.abeysinghe@gmail.com> wrote on 10/02/2005
20:09:49:
> Hi John,
> Going throuhg AXISCPP-388, I get the feeling that the need is to
> set transport properties either from handlers or at Stub level.
> I feel it is differrent from setting axiscpp.conf like settings
> programatically.
> Could you please clarify.
>
> Thanks,
> Samisa...
>
>
>
>
>
> On Thu, 10 Feb 2005 08:38:06 +0000, John Hawkins <HAWKINSJ@uk.ibm.com>
wrote:
> >
> > We already have a JIRA that discusses the setting of handlers
> > programmatically (AXISCPP-388). It would appear to be a good thing
that we
> > can allow this too. Perhaps a new JIRA for this referring to that JIRA
and
> > then put it on the release candidate list for 1.6 ?
> >
> >
> >
> >
> >
> > "sanjaya singharage" <sanjayas@opensource.lk>
> >
> > 10/02/2005 04:46
> >
> > Please respond to
> > "Apache AXIS C User List"
> >
> >
> > To "Apache AXIS C User List" <axis-c-user@ws.apache.org>, "Samisa
> > Abeysinghe" <samisa.abeysinghe@gmail.com>
> >
> > cc
> >
> >
> > Subject Re: Client configuration without axiscpp.conf?
> >
> >
> >
> >
> >
> > Is this a wish? May be it should go in to the wish list at
> > http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/WishList
> >
> > sanjaya.
> >
> > ----- Original Message -----
> > From: "Samisa Abeysinghe" <samisa.abeysinghe@gmail.com>
> > To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
> > Sent: Thursday, February 10, 2005 9:38 AM
> > Subject: Re: Client configuration without axiscpp.conf?
> >
> >
> > > > Is it possible to specify the configuration parameters to the
Axis C++
> > > > client without using axiscpp.conf.
> > >
> > > No. The only way is to have c conf file :-(
> > >
> > > >
> > > > I am concerned that multiple clients on the same machine are
forced to
> > share
> > > > the same /etc/axiscpp.conf file. Also I am concerned that
multiple
> > clients
> > > > within the same application are forced to share the same
configuration
> > file.
> > > > My application is likely to have 3rd party Web service clients
pluged
> > in
> > to
> > > > it - I do not want them to interfere with my configuration and
vice
> > versa.
> > >
> > > There is a workaround though - assuming you are using Linux: you
can
> > > have multiple shells open and define fifferent AXISCPP_DEPLOY
setting
> > > in each shell and have different axiscpp.conf files in different
> > > locations pointed to by different AXISCPP_DEPLOY variables. (May be
> > > the same would work on Windows with multiple command prompts)
> > >
> > >
> > > >
> > > > While I appreciate the flexibility provided by the configuration
file
> > I'd
> > > > prefer to specify the client configuration parameters
programatically.
> > Is
> > > > this possible?
> > >
> > > There is no way that you can specify the settings at stub level
> > programatically.
> > > It would be a good idea to support this in view of multiple clients
in
> > > the same envioronment.
> > >
> > > Thanks,
> > > Samisa...
> > >
> > > >
> > > > Thanks,
> > > >
> > > > Tim
> > > > --
> > > > IBM Tivoli Access Manager Development
> > > > Gold Coast Development Lab, Australia
> > > > +61-7-5552-4001 phone
> > > > +61-7-5571-0420 fax
> > >
> >
> >
> >
> >
--=_alternative 0080809B4A256FA4_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">I was going to suggest that simply being
able to specify the location of the config file programatically would be
enough for me for now but that's not quite right. The other requirement
I have is really to have multiple independent instances of the Axis client
in a single process.</font>
<br>
<br><font size=2 face="sans-serif">I.e. I'd like the class defined in Axis.hpp
to be a real class and not a namespace for the initialize method. This
must be a useful thing anyway - how can an Axis C++ server also act as
a client?</font>
<br>
<br><font size=2 face="sans-serif">I couldn't work out how to edit the
wish list - it alsways told me I wasn't permitted - even after creating
a profile etc so I've opened a couple of JIRA issues.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br>
<br><font size=2 face="sans-serif">Tim<br>
--<br>
IBM Tivoli Access Manager Development<br>
Gold Coast Development Lab, Australia<br>
+61-7-5552-4001 phone<br>
+61-7-5571-0420 fax</font>
<br>
<br><font size=2><tt>Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
wrote on 10/02/2005 20:09:49:<br>
<br>
> Hi John,<br>
> Going throuhg AXISCPP-388, I get the feeling that the
need is to<br>
> set transport properties either from handlers or at Stub level.<br>
> I feel it is differrent from setting axiscpp.conf like
settings<br>
> programatically.<br>
> Could you please clarify.<br>
> <br>
> Thanks,<br>
> Samisa...<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On Thu, 10 Feb 2005 08:38:06 +0000, John Hawkins <HAWKINSJ@uk.ibm.com>
wrote:<br>
> > <br>
> > We already have a JIRA that discusses the setting of handlers<br>
> > programmatically (AXISCPP-388). It would appear to be a good
thing that we<br>
> > can allow this too. Perhaps a new JIRA for this referring to
that JIRA and<br>
> > then put it on the release candidate list for 1.6 ? <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > "sanjaya singharage" <sanjayas@opensource.lk>
<br>
> > <br>
> > 10/02/2005 04:46 <br>
> > <br>
> > Please respond to<br>
> > "Apache AXIS C User List" <br>
> > <br>
> > <br>
> > To "Apache AXIS C User List" <axis-c-user@ws.apache.org>,
"Samisa<br>
> > Abeysinghe" <samisa.abeysinghe@gmail.com> <br>
> > <br>
> > cc<br>
> > <br>
> > <br>
> > Subject Re: Client configuration without axiscpp.conf? <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Is this a wish? May be it should go in to the wish list at<br>
> > http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/WishList<br>
> > <br>
> > sanjaya.<br>
> > <br>
> > ----- Original Message -----<br>
> > From: "Samisa Abeysinghe" <samisa.abeysinghe@gmail.com><br>
> > To: "Apache AXIS C User List" <axis-c-user@ws.apache.org><br>
> > Sent: Thursday, February 10, 2005 9:38 AM<br>
> > Subject: Re: Client configuration without axiscpp.conf?<br>
> > <br>
> > <br>
> > > > Is it possible to specify the configuration parameters
to the Axis C++<br>
> > > > client without using axiscpp.conf.<br>
> > ><br>
> > > No. The only way is to have c conf file :-(<br>
> > ><br>
> > > ><br>
> > > > I am concerned that multiple clients on the same
machine are forced to<br>
> > share<br>
> > > > the same /etc/axiscpp.conf file. Also I am concerned
that multiple<br>
> > clients<br>
> > > > within the same application are forced to share
the same configuration<br>
> > file.<br>
> > > > My application is likely to have 3rd party Web
service clients pluged<br>
> > in<br>
> > to<br>
> > > > it - I do not want them to interfere with my
configuration and vice<br>
> > versa.<br>
> > ><br>
> > > There is a workaround though - assuming you are using
Linux: you can<br>
> > > have multiple shells open and define fifferent AXISCPP_DEPLOY
setting<br>
> > > in each shell and have different axiscpp.conf files
in different<br>
> > > locations pointed to by different AXISCPP_DEPLOY variables.
(May be<br>
> > > the same would work on Windows with multiple command
prompts)<br>
> > ><br>
> > ><br>
> > > ><br>
> > > > While I appreciate the flexibility provided by
the configuration file<br>
> > I'd<br>
> > > > prefer to specify the client configuration parameters
programatically.<br>
> > Is<br>
> > > > this possible?<br>
> > ><br>
> > > There is no way that you can specify the settings
at stub level<br>
> > programatically.<br>
> > > It would be a good idea to support this in view of
multiple clients in<br>
> > > the same envioronment.<br>
> > ><br>
> > > Thanks,<br>
> > > Samisa...<br>
> > ><br>
> > > ><br>
> > > > Thanks,<br>
> > > ><br>
> > > > Tim<br>
> > > > --<br>
> > > > IBM Tivoli Access Manager Development<br>
> > > > Gold Coast Development Lab, Australia<br>
> > > > +61-7-5552-4001 phone<br>
> > > > +61-7-5571-0420 fax<br>
> > ><br>
> > <br>
> > <br>
> > <br>
> ><br>
</tt></font>
--=_alternative 0080809B4A256FA4_=--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic