Ok I figured this out.
It would seem that you cannot use a skeleton based server deploy if you
want to break down the service into individual operaitons within the server
and client config wsdd's.
I have got this to work with a server deploy however you have to set
skeletondeploy to false when generating via WSDL2Java, hence, all request
will be directed by Axis server to the impl directly. I'm not sure why you
cannot do this with a skeleton based server deployment however this seems
to be the only way to get this to work.
In any case, once I successfully deployed an operation-based wsdd I
discovered that you cannot specify request and response flows at the
operational level anyway, which was the whole point of this in the first
place - you can only specify these flows per service...
It may be worthwhile putting these details into the user guide guys ......
[EMAIL PROTECTED]
ltech.co.in To:
[email protected]
cc:
26/10/2006 06:53 PM Subject: RE: web service
operation deployment question
Please respond to
axis-user
Phillips,
Have you tried deleting the old generated files with (skeletonDeploy=true)
and running the WSDL2Java and refreshing the folder structure, if you are
using some editor??
Thanks,
Srinivas N
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, October 26, 2006 1:51 PM
To: [email protected]
Subject: web service operation deployment question
Hi all,
I have used Axis 1.4 to successfully deploy the multiple-operation web
service. In my environment I have deployed both the client and server stubs
as i need to emulate a test environment, hence I need the client stubs to
call my test server impl.
The "deploy.wsdd" generated by WSDL2Java (skeletonDeploy=true) does not
specify either of the individual operations. Rather, AXIS treats the
service as a single entity and somehow reconciles the required operation
internally. Deploying this wsdd results in a working web service, and the
server config is attached as "server-config.wsdd".
As I need to give each operation a different request/response flow
combination by requirements, I need to define each operation independently
in either the client-config.wsdd or server-config.wsdd.
Generating the deploy.wsdd via WSDL2Java (skeletonDeploy=false) results in
indivual operation definitions in the deploy.wsdd (deploy-ops.wsdd).
However, after deploying this deploy.wsdd (see server-config-ops.wsdd) and
still using the skeleton classes generated above, I cannot get these client
stubs to reconcile with the server stubs as I continuously recieve the
error message
"The OperationDesc for uploadFinancialStatementFile was not synchronized to
a method of
au.com.objectconsulting.webservice.fsm.service.externalmarket.ExternalMarket
InterfaceSkeleton."
Does anyone know how to configure the client and server wsdd's to
synchronize the request with the skeleton method? A clear answer here
would help prevent the same question appearing quite reguarly.
Thanks in advance,
Damian Phillips
(See attached file: server-config-ops.wsdd)(See attached file:
deploy-ops.wsdd)(See attached file: server-config.wsdd)(See attached file:
deploy.wsdd)
---------------------------------------------------------------------
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]
