So I can take a class, describe my proposed web service in a WSDD and then
use AdminClient to publish it. But much of the documentation and discussion
here describes how to use Java2WSDL to generate WSDL - what is the
motivation for doing this when Axis does this for you?
I'm trying to expose an e
you'll need the WSDL produced by Java2WSDL to register your webservice
with a UDDI registry, so other clients that are not necessarily written
with Axis/Java can locate and invoke your webservice.
Ed Pond wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
So I can
Hi all
I met a question while deploy web service into a tomcat5 cluster. I set the
scope=session, and the tomcat console show me :
java.lang.IllegalArgumentException: Value for attribute Convert is not serial
izable.
It seems that axis or container put the service into session. But C
Question: Are u willing to pitch in to help? If so, please review existing bugs in
bugzilla and
upload patches. The more folks pitching in, the quicker we can get out releases.
thanks,
dims
--- Tony Opatha <[EMAIL PROTECTED]> wrote:
>
> I think it is extremely important that we release:
>
> 0
I think it is extremely important that we release:
0) AXIS 1.2 Beta by early Jan. '04
1) AXIS 1.2 Final Release by mid-Jan. '04
2) AXIS 1.3 Release by mid-Feb to mid-March '04
AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal code changes in AXIS 1.1-based web services appli
