Re: authentication in SOAP header

2007-03-14 Thread Jesús Daniel Blázquez Carazo 

See apache wss4j project

- Original Message - 
From: [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, March 14, 2007 2:50 PM
Subject: authentication in SOAP header



Authentication in SOAP header
Anybody knows how to do it? 
Maybe tutorial exist?







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

Re: Client-side: Different Clients, different Trust-/keystore

2007-02-21 Thread Jesús Daniel Blázquez Carazo 
Try to set the JVM argument -Djavax.net.ssl.trustStore. It references to the 
filepath where your trusstore are.


- Original Message - 
From: Peter Huber [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, February 21, 2007 4:34 PM
Subject: Client-side: Different Clients, different Trust-/keystore



 Hi Axis-Users, Team,

I want to consume different WebService via Axis 1.4 and HTTPS-Access. Each
of the Services has it's own pair fo Trust-/Keystore in my setup.
But I cannot find a way to configure that! Say for instance with Axis 1.4 
I

can configure a SSLSocketFactory for a client by class name!
And then? I want to setup a SocketFactory OBJECT and such an object I want
to pass to each of the axis client-stubs.

Is this possible. How can I do it. Thanx for your help

CU,
Peter


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

Re: Shared data types between services

2007-02-07 Thread Jesús Daniel Blázquez Carazo 

The problem you describe is named web services interoperability.

I think you should consider the possibility of use a BPEL workflow engine if 
you need more interaction between web services.


- Original Message - 
From: Miguel Ferreira [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, February 07, 2007 12:52 PM
Subject: Shared data types between services




Dear all,

How can I share a message definition (i.e. object definition or data 
type) between two different web services?

The idea is the following:

I have two distinct web services: service A and service B with web 
methods method1 and method2 respectly. Both methods receive a  Parameter 
object type as argument and return the same type.


Summary:

ServiceA
- Paramenter method1(Parameter p);
ServiceB
- Paramenter method2(Parameter p);

I want to build a client that invokes method1 on ServiceA and uses  the 
response to call method2 on ServiceB. For example:


Parameter a = serviceA.method1(p);
serviceB.method2(a);

The problem is that while building the stubs (using WSDL2Java), I end  up 
with two different Parameter objects, so composition is not  possible.

I can one solve this problem from a SOA perspective using axis.

Thanks in advance.

Best regards,
Miguel


- -
Miguel Ferreira (researcher)
Department of Information Systems
University of Minho Campus de Azurém
4800-058 Guimarães, Portugal
http://www.dsi.uminho.pt/~ferreira/
Phone: +351 253 510 261 / FAX: +351 253 510 300 / Ext.: 510261



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

Re: Do you know a tool to easily visualize a wsdl file ?

2007-01-17 Thread Jesús Daniel Blázquez Carazo 

You can use XML spy

- Original Message - 
From: Samy Mechiri [EMAIL PROTECTED]

To: axis-user@ws.apache.org
Sent: Wednesday, January 17, 2007 5:38 PM
Subject: RE: Do you know a tool to easily visualize a wsdl file ?



I am on Windows/CygWin

I am not sure it is what I searching for.
I don't want a simple xml editor. What I want is really specific to wsdl
files.

The idea is to get rid of overload of all the xml grammar

An example of output would be:

configureMyThing: operation
-thingName: [xsd:string]
-thingConfig: [myns:ThingConfiguration]
-thingCount: [xsd:int]
-thingLinks: [xsd:string]
...
...


There you see all the arguments of the functions are separated with
potentially the name of the argument and it's type (when type is not a
primitive it is also recursively detailed)


regards,

Samy MECHIRI - Software Engineer
KXEN - 92158 Suresnes CEDEX
FRANCE

-Original Message-
From: ChadDavis [mailto:[EMAIL PROTECTED] 
Sent: mercredi 17 janvier 2007 17:18

To: axis-user@ws.apache.org
Subject: Re: Do you know a tool to easily visualize a wsdl file ?

What platform / os are you on?

On linux, I had trouble with several xml editors being able to handle
long wsdl's.  The best I'v found is called MLView.  I'm not sure its
what your looking for, in terms of graphical representation, but it is
super fast and represents the document as a DOM hieararchy, which makes
it very easy to see the various elements and regions of a wsdl.
Or you can view the document as the raw document but with element based
code folding which also makes it very easy to peruse lengthy
documents.



On 1/17/07, Samy Mechiri [EMAIL PROTECTED] wrote:



Hi everyone,

do you know any small, easily usable tool to visualize what operations



(and their arguments) are available on a wsd file ?

There seem to be nusoap having such a tool (i've read about it on
http://www.xml.com/lpt/a/1388) but I could not find any reference to 
it on nusoap's web page.


Ideally it would output the results as a txt or html file

Thank you for reading.


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



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Fw: Problem with axis + wss4j

2006-11-06 Thread Jesús Daniel Blázquez Carazo 



I am using axis 1.4

- Original Message - 
From: Jesús Daniel 
Blázquez Carazo 
To: axis-dev@ws.apache.org 
Sent: Monday, November 06, 2006 10:01 AM
Subject: Problem with axis + wss4j

Hello

I am trying to use the wss4j apache project to 
build a security handler. This handler must invoke to a authentication web 
service for a session token. 
I seems that it is not possible to call a web 
service inside a handler class. Some idea?

Thanks.

Re: AXIS 1.4: invoke request after web service sent response to client

2006-10-24 Thread Jesús Daniel Blázquez Carazo 



Have you think about the possibility of describe 
this web services chain as a BPEL?


  - Original Message - 
  From: 
  Stadelmann Josef 
  To: axis-user@ws.apache.org ; Martin Gainty 
  
  Sent: Tuesday, October 24, 2006 2:04 
  PM
  Subject: AW: AXIS 1.4: invoke request 
  after web service sent response to client
  
  Are you saying that the architectural concept of having a 
  CLIENTgoing to anAGENTpassing on to 
  aSERVER is bad? :-/
  In my mind an AGENT is two-fold as described by .-1
  what all about is the then CORBA? :-)
  Josef Stadelmann
  
-Ursprüngliche Nachricht-Von: Martin Gainty 
[mailto:[EMAIL PROTECTED]Gesendet: Dienstag, 24. Oktober 2006 
13:24An: axis-user@ws.apache.orgBetreff: 
Re: AXIS 1.4: invoke request after web service sent response to 
client
would be helpful if you looked at the 
definition ofatomic transactions and the principle of 
atomicityredesigning a web service that itself is a client to another 
web servicemay possiblyinvite a race condition
AxisClient1 calls AxisService1 and expects 
output from AxisService1
AxisService1 calls AxisService2 and expects 
output from AxisService2AxisService2 calls AxisService3 and expects 
output from AxisService3
AxisService3 calls AxisService1 (AxisService3 
iscontending for output for AxisService1 but so is 
AxisClient1)
therefore AxisService3 AND AxisClient1 are both vying for the same resource 
(AxisService1)
from a purelyarchitectural 
perspective this is BAD DESIGNIf you want more than 1 data item then 
your AxisSoapService should return a complex datatype which wholly contains 
all of the data points you desire

Please read this discussion of atomicity by 
svend frolund
http://www.w3.org/2001/03/WSWS-popa/paper50
Martin --
This e-mail communication and any attachments may contain confidential 
and privileged information for the use of the designated recipients 
named above. If you are not the intended recipient, you are hereby notified 
that you have receivedthis communication in error and that any review, 
disclosure, dissemination, distribution or copying of it or its 
contents

  - Original Message - 
  From: 
  Kestonas 
  JoJo 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, October 24, 2006 6:32 
  AM
  Subject: AXIS 1.4: invoke request 
  after web service sent response to client
  
  
  Hi all,I am curious is it possible to configure AXIS server to 
  invoke another web service as client after response is send to 
  client.for example Transaction like:1. Client No. 1 
  invokes method of Axis service No. 12. Axis service No 1 responses to 
  Client No. 13. Axis service No 1 invokes web service No. 2 as 
  Client No. 2 4. Axis service No 1 receives response from service No. 
  2.5. Transaction is commited.Thanks in 
  advance,Kestas

Re: AXIS 1.4: invoke request after web service sent response to client

2006-10-24 Thread Jesús Daniel Blázquez Carazo 



A BPEL is a web service workflow. You can design a 
BPEL to invoke a web service chain, deploy it in a BPEL engine to execute the 
process.

In this way the first web service pass its result 
to the second web service ... 

  - Original Message - 
  From: 
  Stadelmann Josef 
  To: axis-user@ws.apache.org 
  Sent: Tuesday, October 24, 2006 3:32 
  PM
  Subject: AW: AXIS 1.4: invoke request 
  after web service sent response to client
  
  Can you please explain me what a BPEL is (Business Process Engineering 
  Language)? What is it in your terms?
  Josef
  
-Ursprüngliche Nachricht-Von: Jesús Daniel 
Blázquez Carazo [mailto:[EMAIL PROTECTED]Gesendet: 
Dienstag, 24. Oktober 2006 14:37An: axis-user@ws.apache.orgBetreff: 
Re: AXIS 1.4: invoke request after web service sent response to 
client
Have you think about the possibility of 
describe this web services chain as a BPEL?


  - Original Message - 
  From: 
  Stadelmann Josef 
  To: axis-user@ws.apache.org ; Martin 
  Gainty 
  Sent: Tuesday, October 24, 2006 2:04 
  PM
  Subject: AW: AXIS 1.4: invoke request 
  after web service sent response to client
  
  Are you saying that the architectural concept of having a 
  CLIENTgoing to anAGENTpassing on to 
  aSERVER is bad? :-/
  In my mind an AGENT is two-fold as described by 
  .-1
  what all about is the then CORBA? :-)
  Josef Stadelmann
  
-Ursprüngliche Nachricht-Von: Martin Gainty 
[mailto:[EMAIL PROTECTED]Gesendet: Dienstag, 24. Oktober 
2006 13:24An: axis-user@ws.apache.orgBetreff: 
Re: AXIS 1.4: invoke request after web service sent response to 
client
would be helpful if you looked at the 
definition ofatomic transactions and the principle of 
atomicityredesigning a web service that itself is a client to 
another web servicemay possiblyinvite a race 
condition
AxisClient1 calls AxisService1 and expects 
output from AxisService1
AxisService1 calls AxisService2 and expects 
output from AxisService2AxisService2 calls AxisService3 and expects 
output from AxisService3
AxisService3 calls AxisService1 
(AxisService3 iscontending for output for AxisService1 but so is 
AxisClient1)
therefore AxisService3 AND AxisClient1 are both vying for the same resource 
(AxisService1)
from a purelyarchitectural 
perspective this is BAD DESIGNIf you want more than 1 data item then 
your AxisSoapService should return a complex datatype which wholly 
contains all of the data points you desire

Please read this discussion of atomicity by 
svend frolund
http://www.w3.org/2001/03/WSWS-popa/paper50
Martin --
This e-mail communication and any attachments may contain 
confidential and privileged information for the use of the 
designated recipients named above. If you are not the intended 
recipient, you are hereby notified that you have receivedthis 
communication in error and that any review, disclosure, dissemination, 
distribution or copying of it or its contents

  - Original Message - 
  From: 
  Kestonas 
  JoJo 
  To: axis-user@ws.apache.org 
  
  Sent: Tuesday, October 24, 2006 
  6:32 AM
  Subject: AXIS 1.4: invoke request 
  after web service sent response to client
  
  
  Hi all,I am curious is it possible to configure AXIS server 
  to invoke another web service as client after response is send to 
  client.for example Transaction like:1. Client No. 1 
  invokes method of Axis service No. 12. Axis service No 1 responses 
  to Client No. 13. Axis service No 1 invokes web service No. 
  2 as Client No. 2 4. Axis service No 1 receives response from 
  service No. 2.5. Transaction is commited.Thanks in 
  advance,Kestas

Re: SSL, Mutual or Client Authentication

2006-10-19 Thread Jesús Daniel Blázquez Carazo 



If you want mutual authentication between client 
and server you need first a certificate for the client and the server. To get 
them you can try use openssl.

Second you need configure SSL with Tomcat in the 
way you have explained and delete or comment from the server.xml the 
connector port="8080"

In this way Tomcat will be listening in the secure 
port 8443.

  - Original Message - 
  From: 
  VELUMMYLUM Piragash 
  To: axis-user@ws.apache.org 
  Sent: Thursday, October 19, 2006 5:28 
  PM
  Subject: SSL, Mutual or Client 
  Authentication
  
  Hi 
  All,
  
  I am 
  very new to Axis, I just installed it yesterday.
  
  I am 
  trying to use Axis over an HTTPS connection. I want to be able to use 
  SSL with mutual authentication before Axis2 even receives the request. I 
  am running Axis2 on Tomcat. I was wondering if I should let Tomcat 
  handle the SSL part or if Axis2 has its own features? CanTomcat do 
  mutual authentication, i.e. authenticating the client? If not can Axis2 
  do mutual authentication for SSL?
  
  Here 
  are 2 routes I have considered and my questions regarding both 
  possibilities:
  
  1.Configuring SSL with 
  Tomcat:
   - I have discovered that I can define a connector 
  with Tomcat under the $CATALINA_HOME/conf/server.xml
  
 !-- Define a SSL HTTP/1.1 Connector on port 
8443 --
 Connector port="8443" 
maxHttpHeaderSize="8192" 
maxThreads="150" minSpareThreads="25" 
maxSpareThreads="75" 
enableLookups="false" 
disableUploadTimeout="true" 
acceptCount="100" scheme="https" 
secure="true" 
clientAuth="false" sslProtocol="TLS" /
   - How do I specify Tomcat to use only use the secure 
  connector and not the non-SSL connector when talking to 
  Axis2?
  
  2. Configuring Axis2 to handle SSL 
  connections:
   - Can Axis2 do this? If so can it deal with mutual 
  authentication?
  
  Thank you in advance,
  
  Piragash

Using an EJB as web service

2006-10-11 Thread Jesús Daniel Blázquez Carazo 



Hi,I have deployed anEJB in JBoss 4.This 
EBJmustworkas aweb service deployed in axis2 but I want 
to know how todo this in axis2.In the previous axis version it was 
easy because there was the org.apache.axis.providers.java.EJBprovider class. 
This class read the server-config.wsdd file to get the parametersand to 
communicate with the EJB. But this new version has a different architecture and 
this is not possible. 
I need an alternative to do the same.I am retrieving in the code of 
the EJBProvider class to try do this.

Thanks in advance.

Re: Problem with session management

2005-09-08 Thread Jesús Daniel Blázquez Carazo 



I use a cliente with classes generated by 
WSDL2Java.

Code generated is:

protected org.apache.axis.client.Call 
createCall() throws java.rmi.RemoteException 
{ try 
{ 
org.apache.axis.client.Call _call = 
super._createCall(); 
if (super.maintainSessionSet) 
{ 
_call.setMaintainSession(super.maintainSession); 
 
}

  
 org.apache.axis.client.Call _call = 
createCall();
  
 _call.invoke(

Do youtalk about this part of the cliente 
code?


  - Original Message - 
  From: 
  Merten 
  Schumann 
  To: [EMAIL PROTECTED] 
  Sent: Thursday, September 08, 2005 8:12 
  AM
  Subject: RE: Problem with session 
  management
  
  Do 
  you use
  Service service=new 
  Service();
  
   // if HttpSession support is 
  needed service.setMaintainSession(true);
  in 
  your AxisClient code?
  
  cu
   Merten
  
  
  
  
  From: Jesús Daniel Blázquez Carazo 
  [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 07, 
  2005 1:31 PMTo: axis-user@ws.apache.org; axis-dev@ws.apache.orgSubject: 
  Problem with session management
  
  I am trying to session management using a servlet 
  client on jboss server.
  ...

Fw: Problem with session management

2005-09-08 Thread Jesús Daniel Blázquez Carazo 



I think problem I have is because AxisEngine is 
distinct in each call to web service and the information of this is in 
MessageContext.

Someone knows how canI doMessageContext 
contains the same AxisEngine in two call to web services?

I want to call two web services: the first call 
contains in response session_id and this session_id will be passed in the second 
call request.





- Original Message - 
From: Jesús Daniel 
Blázquez Carazo 
To: axis-user@ws.apache.org ; axis-dev@ws.apache.org 
Sent: Wednesday, September 07, 2005 1:30 PM
Subject: Problem with session management

I am trying to session management using a servlet 
client on jboss server.

The deploy.wsdd in server 


?xml version="1.0" encoding="UTF-8"?
deployment
name="TerregovService" 
xmlns="http://xml.apache.org/axis/wsdd/"
targetNamespace="http://localhost:8080/TerregovService"
xmlns:trights="http://localhost:8080/TerregovService"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
service name="Rights" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="RightsBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.RightsBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.RightsBeanLocal"/
parameter name="allowedMethods" value="checkRights getUser"/
requestFlow name="RightsRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="RightsResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

service name="Authentication" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="AuthenticationBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.AuthenticationBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.AuthenticationBeanLocal"/
parameter name="allowedMethods" value="challengeRequestX509 
challengeValidationX509 loginValidation challengeRequest challengeValidation 
"/
requestFlow name="AuthenticationRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="AuthenticationResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

service name="CAServices" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="CAServicesBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.CAServicesBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.CAServicesBeanLocal"/
parameter name="allowedMethods" value="requestNewUser requestCertificate 
getCRL getPublicKey revokeCertificate searchCertificate updateCertRequest 
"/
requestFlow name="CAServices"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="CAServices"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

/deployment

and works well because in SOAP header contains session 
value, but the client does not put session value in SOAP 
request.

The client.wsdd is generated automatically with org.apache.axis.utils.Admin client deploy.wsdd:

?xml version="1.0" encoding="UTF-8"?
deployment xmlns="http://xml.apache.org/axis/wsdd/" 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
globalConfiguration
parameter name="adminPassword" value="admin"/
parameter name="enableNamespacePrefixOptimization" value="true"/
parameter name="disablePrettyXML" value="true"/
parameter name="attachments.implementation" 
value="org.apache.axis.attachments.AttachmentsImpl"/
para

Problem with session management

2005-09-07 Thread Jesús Daniel Blázquez Carazo 



I am trying to session management using a servlet 
client on jboss server.

The deploy.wsdd in server 


?xml version="1.0" encoding="UTF-8"?
deployment
name="TerregovService" 
xmlns="http://xml.apache.org/axis/wsdd/"
targetNamespace="http://localhost:8080/TerregovService"
xmlns:trights="http://localhost:8080/TerregovService"
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
service name="Rights" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="RightsBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.RightsBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.RightsBeanLocal"/
parameter name="allowedMethods" value="checkRights getUser"/
requestFlow name="RightsRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="RightsResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

service name="Authentication" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="AuthenticationBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.AuthenticationBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.AuthenticationBeanLocal"/
parameter name="allowedMethods" value="challengeRequestX509 
challengeValidationX509 loginValidation challengeRequest challengeValidation 
"/
requestFlow name="AuthenticationRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="AuthenticationResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

service name="CAServices" provider="Handler"
parameter name="handlerClass" 
value="org.apache.axis.providers.java.EJBProvider"/
parameter name="beanJndiName" value="CAServicesBeanLocal"/
parameter name="homeInterfaceName" 
value="org.terregov.dram.WebService.interfaces.CAServicesBeanLocalHome"/
parameter name="localInterfaceName" 
value="org.terregov.dram.WebService.interfaces.CAServicesBeanLocal"/
parameter name="allowedMethods" value="requestNewUser requestCertificate 
getCRL getPublicKey revokeCertificate searchCertificate updateCertRequest 
"/
requestFlow name="CAServices"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="CAServices"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
/service

/deployment

and works well because in SOAP header contains session 
value, but the client does not put session value in SOAP 
request.

The client.wsdd is generated automatically with org.apache.axis.utils.Admin client deploy.wsdd:

?xml version="1.0" encoding="UTF-8"?
deployment xmlns="http://xml.apache.org/axis/wsdd/" 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"
globalConfiguration
parameter name="adminPassword" value="admin"/
parameter name="enableNamespacePrefixOptimization" value="true"/
parameter name="disablePrettyXML" value="true"/
parameter name="attachments.implementation" 
value="org.apache.axis.attachments.AttachmentsImpl"/
parameter name="sendXsiTypes" value="true"/
parameter name="sendMultiRefs" value="true"/
parameter name="sendXMLDeclaration" value="true"/
/globalConfiguration
requestFlow name="RightsRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="AuthenticationResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
responseFlow name="RightsResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
requestFlow name="AuthenticationRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
responseFlow name="CAServices"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/responseFlow
service name="Rights" provider="Handler"
requestFlow name="RightsRequest"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/
/requestFlow
responseFlow name="RightsResponse"
handler name="session" 
type="java:org.apache.axis.handlers.SimpleSessionHandler"/
handler type="soapmonitor"/