RE: Basic Auth using the 1.0 release (not nightlies)
I looked in org.apache.axis2.transport.http and I do not see HttpTransportProperties.BasicAuthentication. I did find HttpTransportProperties.Authenticator, but I am not entirely sure how to use it. Assuming I am to create an instance of HttpTransportProperties.Authenticator and set the username and password values, then what do I do with that instance? As per my original question, is it possible to do this with the 1.0 release? While I understand the 1.0 release is undergoing many bug fixes right now, the client libraries have been working quite well for us and we are a little apprehensive to switch to something that is undergoing change on a daily basis. Thanks, Mark From: Charak, Vikas [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2006 9:18 AM To: axis-user@ws.apache.org Subject: RE: Basic Auth using the 1.0 release (not nightlies) I guess look in to MessageContext and HttpTransportProperties.BasicAuthentication in nightly builds. From: Mark McCall [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2006 8:35 AM To: axis-user@ws.apache.org Subject: RE: Basic Auth using the 1.0 release (not nightlies) OK – I guess the resounding silence means “no”. Is there a way to do this WITH the nightly builds? Thanks, Mark From: Mark McCall Sent: Monday, October 02, 2006 1:16 PM To: 'axis-user@ws.apache.org' Subject: Basic Auth using the 1.0 release (not nightlies) I have not found any documentation or samples showing how to programmatically set Basic Auth information in an Axis2 generated client. I am using the 1.0 release, not the nightly builds. Can somebody point me in the right direction? Thanks, Mark The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
RE: Basic Auth using the 1.0 release (not nightlies)
OK – I guess the resounding silence means “no”. Is there a way to do this WITH the nightly builds? Thanks, Mark From: Mark McCall Sent: Monday, October 02, 2006 1:16 PM To: 'axis-user@ws.apache.org' Subject: Basic Auth using the 1.0 release (not nightlies) I have not found any documentation or samples showing how to programmatically set Basic Auth information in an Axis2 generated client. I am using the 1.0 release, not the nightly builds. Can somebody point me in the right direction? Thanks, Mark The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Basic Auth using the 1.0 release (not nightlies)
I have not found any documentation or samples showing how to programmatically set Basic Auth information in an Axis2 generated client. I am using the 1.0 release, not the nightly builds. Can somebody point me in the right direction? Thanks, Mark The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
RE: Setting HTTP request parameters from a client stub
I do not see this constant in the 1.0 release. Is it only available from the nightly releases? -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 4:21 PM To: axis-user@ws.apache.org Subject: Re: Setting HTTP request parameters from a client stub http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters #HTTP_HEADERS On 9/22/06, Mark McCall <[EMAIL PROTECTED]> wrote: > > > > > I am using an Axis 2 generated client stub (using the 1.0 release) to invoke > a web service over HTTP. I need to be able to send some arbitrary parameter > values in the Http Request, i.e. separate from the SOAP envelope. How do I > do this? > > > > Thanks, > > Mark > > > > > > > > > > The information contained in this e-mail message is intended only > for the personal and confidential use of the recipient(s) named > above. This message may be an attorney-client communication and/or > work product and as such is privileged and confidential. If the > reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are > hereby notified that you have received this document in error and > that any review, dissemination, distribution, or copying of this > message is strictly prohibited. If you have received this > communication in error, please notify us immediately by e-mail, and > delete the original message. > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Setting HTTP request parameters from a client stub
I am using an Axis 2 generated client stub (using the 1.0 release) to invoke a web service over HTTP. I need to be able to send some arbitrary parameter values in the Http Request, i.e. separate from the SOAP envelope. How do I do this? Thanks, Mark The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Rampart UsernameToken (setting user id programmatically)
I found Ruchith’s presentation "Secure Web Services with Apache Rampart" from http://www.wso2.net/presentations and I downloaded the samples. While these have been extremely helpful, I noticed for all examples with a "UsernameToken" action, the client.axis.xml has the user id hard coded, where the password can be obtained using a callback. How can my client code programmatically set the user id? My client is invoking the service using a wsdl2java generated stub (public class MyClient extends org.apache.axis2.client.Stub) and I am using the axis2/rampart 1.0 releases. Thanks, Mark The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
