You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Tony Dean <To...@sas.com> on 2006/08/02 20:16:13 UTC

FW: [axis2] questions...

Does anyone have any insights on the questions listed below.

For instance setting some HTTP headers works while others do not.

These work:
options.setProperty(MessageContextConstants.HTTP_PROTOCOL_VERSION,
                    HTTPConstants.HEADER_PROTOCOL_10);
options.setProperty(HTTPConstants.PROXY, proxyProperties);
options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
                    basicAuthentication)

serviceClient.setOptions(options);

While setting options like the following seem to have not affect:
options.setProperty(HTTPConstants.HEADER_CONNECTION,
                    HTTPConstants.HEADER_CONNECTION_CLOSE);

Is there an exaustive list of options that one can use to control his/her client invocation?

Also, are there any WS-Security configuration options that can be set programatically or must all of this information be specific to InFlowSecurity/OutFlowSecurity handler configuration.  It seems logical for handlers to be responsible on the server side.  Didn't know if more flexibility once enabled on the client side.  My guess is not, but just checking.

Thanks.

-----Original Message-----
From: Tony Dean [mailto:Tony.Dean@sas.com] 
Sent: Wednesday, August 02, 2006 8:37 AM
To: axis-dev@ws.apache.org; axis-dev@ws.apache.org
Subject: FW: [axis2] questions...

Hi,

I have picked up a little more information on how Axis2 achieves statefullness just by reading email threads, but any additional more specific insight would be great.

Also, on question (2) below how do you set HTTP headers for client invocation.  What I did below did not work, please explain.  It seems as though the API is not consistent with setting client options.  Can anyone summarize the options that can be set and how to set them?

Also, regarding WS-Security options/configuration... It appears that you can only set these semantics by using OutFlowSecurity/InFlowSecurity handlers.  There is no way to set/configure these parameters programmatically, right?

Thanks for any feedback.

> ______________________________________________ 
> From: 	Tony Dean  
> Sent:	Sunday, July 30, 2006 6:09 PM
> To:	Tony Dean; 'axis-dev@ws.apache.org'
> Subject:	RE: [axis2] (easy) questions...
> 
> Resending this question...
> 
> For question #1 (are you looking at WSRF OASIS spec)?  Thanks for any insight.
> 
> -Tony
> 
> _____________________________________________ 
> From: 	Tony Dean  
> Sent:	Friday, July 21, 2006 5:57 PM
> To:	'axis-dev@ws.apache.org'
> Subject:	[axis2] (easy) questions...
> 
> Hi,
> 
> I have a couple of easy questions for you. ;-)
> 
> (1) session scope
> 
> I know how to enable a service for scope=session, but how is the actual goal achieved.  In other words how does Axis2 keep session affinity among services and their many clients?  Are clients expected to participate (be aware of session semantics)?  Do clients need to pass a session context id of some sort?  Just wandering how this process works.
> 
> (2) setting output http headers...
> 
> For instance if I want to set Connection : close
> 
> 		options.setProperty(
> 				HTTPConstants.HEADER_CONNECTION,
> 				HTTPConstants.HEADER_CONNECTION_CLOSE);
>                         ServiceClient serviceClient = new ServiceClient();
>                         serviceClient.setOptions(axisOptions);
> 
>                         serviceClient.sendReceive(payload);
> 
> This should work right?  I watched what was sent over the wire with an HTTP tracer and this header was not added like I expected.
> 
> Thanks for insight into these questions.
> 
> -Tony
> 
> 
> 
> 
> Tony Dean
> SAS Institute Inc.
> 919.531.6704
> tony.dean@sas.com
> 
> SAS... The Power to Know
> http://www.sas.com
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


Re: FW: [axis2] questions...

Posted by Eran Chinthaka <ch...@opensource.lk>.
Hi Tony,

The article on client api parameters is finally published here
(http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters).

-- Chinthaka

Eran Chinthaka wrote:
> Tony Dean wrote:
>> Does anyone have any insights on the questions listed below.
>>
>> For instance setting some HTTP headers works while others do not.
>>
>> These work:
>> options.setProperty(MessageContextConstants.HTTP_PROTOCOL_VERSION,
>>                     HTTPConstants.HEADER_PROTOCOL_10);
>> options.setProperty(HTTPConstants.PROXY, proxyProperties);
>> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
>>                     basicAuthentication)
>>
>> serviceClient.setOptions(options);
>>
>> While setting options like the following seem to have not affect:
>> options.setProperty(HTTPConstants.HEADER_CONNECTION,
>>                     HTTPConstants.HEADER_CONNECTION_CLOSE);
>>
>> Is there an exaustive list of options that one can use to control his/her client invocation?
> 
> Well, I can not wait till my article gets published on this. Thought of
> helping you by hosting it in my little space in apache itself.
> You might find this
> (http://people.apache.org/~chinthaka/articles/axis2-parameters.html)
> useful.
> (Note : This is a temp place)
> 
> -- Chinthaka
> 



Re: FW: [axis2] questions...

Posted by Eran Chinthaka <ch...@opensource.lk>.
Tony Dean wrote:
> Does anyone have any insights on the questions listed below.
> 
> For instance setting some HTTP headers works while others do not.
> 
> These work:
> options.setProperty(MessageContextConstants.HTTP_PROTOCOL_VERSION,
>                     HTTPConstants.HEADER_PROTOCOL_10);
> options.setProperty(HTTPConstants.PROXY, proxyProperties);
> options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
>                     basicAuthentication)
> 
> serviceClient.setOptions(options);
> 
> While setting options like the following seem to have not affect:
> options.setProperty(HTTPConstants.HEADER_CONNECTION,
>                     HTTPConstants.HEADER_CONNECTION_CLOSE);
> 
> Is there an exaustive list of options that one can use to control his/her client invocation?

Well, I can not wait till my article gets published on this. Thought of
helping you by hosting it in my little space in apache itself.
You might find this
(http://people.apache.org/~chinthaka/articles/axis2-parameters.html)
useful.
(Note : This is a temp place)

-- Chinthaka