FW: [axis2] questions...

[Tony Dean <To...@sas.com>]

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

Re: FW: [axis2] questions...

[Ruchith Fernando <ru...@gmail.com>]

Hi Tony,

> 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?
>

Nope.. Actually you can configure rampart programatically, Please have
a look at the integration test cases here : [1]

Note that testInteropWithDynamicConfig in the InteropTestBase class
calls the getOutflowConfiguration() and getInflowConfiguration()
methods to get hold of the configuration parameters to add to the
options object. Each of the different classes that extends
InteropTestBase creates the different OutflowConfiguration and
InflowConfiguration objects as required.

Thanks,
Ruchith

-- 
www.ruchith.org

[1] https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/security

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