Hi Deepal:
Deepal Jayasinghe wrote:
Seems like a good proposal. However if you can populate your service
correctly with the schemas, message and soap actions then at the run
time when you do ?wsdl we do the right thing. And even you do not need
to worry about ?wsdl and ?wsdl2 , that's the procedure we are using for
POJO. There we first naviagete the POJO class and then generate schemas
and populate AxisService with operations and messages. So when we do
?wsld we just serialize that and print out the wsdl.
Unfortunately I can't do that since my custom deployer supports services
that are RPC/encoded. IMO, Axis2 should really support RPC/enc at some
point, but until then there's no way to actually get the WSDL I'd like
from our standard mechanisms.
Clearly ?wsdl2 won't work for rpc/enc services, though.
For now, I'm going to get this in for 1.3, but I'll note that it's
experimental and may change if we come up with a better design.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
