Hi Dims,
In my case, tweaking the WSDL is problematic as I am working on dynamic
test cases. I have a Client class and a web service class. I then would
like to generate the client stubs by pointing the wsdl2java at the
running web service. My problem is that the generated stubs are not what
the c
d be another option.
What do the axis team think about it?
Modify the generated signature? Have convenient method generated? Or Let
it as it is...?
/Jongjin
- Original Message -
From: "Michael Merz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Beehive Developer
Repost with more descriptive header.
-michael
-Original Message-
From: Michael Merz
Sent: Friday, December 17, 2004 10:23 AM
To: [EMAIL PROTECTED]
Cc: Beehive Developers
Subject: FW: More Axis questions...
I don't understand some of the behavior of wsdl2java when run against a
ru
I don't understand some of the behavior of wsdl2java when run against a
running web service with "header" web parameters
("ParamDesc.setInHeader(true)"). The generated methods in the client
stub look quite different from the original ones; in particular, they
seem to have parameters that are not re
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
I've seen some strange behavior when using wsdl2java against a running
web service w/ DOC/Literal/Wrapped binding, when I define a "header"
INOUT parameter (and thus use "ParamDesc.setInHeader(true)" and
"ParamDesc.setOutHeader(true)"). The generated method
s) in the client side, the
deserialization of SOAP Fault message would fail.
I will add other comments in JIRA BEEHIVE-133.
/Jongjin
>From: "Michael Merz" <[EMAIL PROTECTED]>
>Reply-To: "Beehive Developers" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
Bcc: [EMAIL PROTECTED]
I'm autogenerating my clients using the wsdl2java ant task. It's working
really well.
One question regarding exception handling, though: When the server
throws a custom exception (subclass of java.lang.Exception), how does
the autogenerated client propagate the results in t
cements). Let's get together and discuss the
programming/ deployment model, the current state of the project and
future directions/ requirements! I look forward to seeing you at
ApacheCon!
Cheers,
-michael
--
2004/US BOF submission
Submitter: Michael Merz <[EMAIL PROTECTED]>
Title: Bee
