Re: Client configuration without axiscpp.conf?
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 <[EMAIL PROTECTED]> 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 +, John Hawkins <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> > > > > 10/02/2005 04:46 > > > > Please respond to > > "Apache AXIS C User List" > > > > > > To "Apache AXIS C User List" , "Samisa > > Abeysinghe" <[EMAIL PROTECTED]> > > > > 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" <[EMAIL PROTECTED]> > > To: "Apache AXIS C User List" > > 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 > > > > > > > > > > >
Re: Client configuration without axiscpp.conf?
I read AXISCPP 188 as the ability to say programmatically that you want handler X to be used on call Y? Either way, no big deal I think the requirement still stands that we want to set handlers and conf setting programmatically. Samisa Abeysinghe <[EMAIL PROTECTED]> 10/02/2005 10:09 Please respond to "Apache AXIS C User List" To Apache AXIS C User List cc Subject Re: Client configuration without axiscpp.conf? 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 +, John Hawkins <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> > > 10/02/2005 04:46 > > Please respond to > "Apache AXIS C User List" > > > To "Apache AXIS C User List" , "Samisa > Abeysinghe" <[EMAIL PROTECTED]> > > 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" <[EMAIL PROTECTED]> > To: "Apache AXIS C User List" > 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 > > > > > >
Re: Client configuration without axiscpp.conf?
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 +, John Hawkins <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> > > 10/02/2005 04:46 > > Please respond to > "Apache AXIS C User List" > > > To "Apache AXIS C User List" , "Samisa > Abeysinghe" <[EMAIL PROTECTED]> > > 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" <[EMAIL PROTECTED]> > To: "Apache AXIS C User List" > 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 > > > > > >
Re: Client configuration without axiscpp.conf?
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" <[EMAIL PROTECTED]> 10/02/2005 04:46 Please respond to "Apache AXIS C User List" To "Apache AXIS C User List" , "Samisa Abeysinghe" <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> To: "Apache AXIS C User List" 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 >
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" <[EMAIL PROTECTED]> To: "Apache AXIS C User List" 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 >
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
Client configuration without axiscpp.conf?
Hi, Another newbie question Is it possible to specify the configuration parameters to the Axis C++ client without using axiscpp.conf. 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. While I appreciate the flexibility provided by the configuration file I'd prefer to specify the client configuration parameters programatically. Is this possible? Thanks, Tim -- IBM Tivoli Access Manager Development Gold Coast Development Lab, Australia +61-7-5552-4001 phone +61-7-5571-0420 fax
