Title: Message
Tony,
you
were right about IWSState not conforming to Java Bean conventions. I was missing
one of the setter methods. Now it's working fine.
Thanks.
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent:
Wednesday, October 06, 2004 1:24 AM
It may be related to IWSState not following
Java Bean conventions (get and set methods for each property). I don't
know why a section wasn't generated, though, to define the
types in the tns1 namespace.
Tony
Greetings.
I am using java2wsdl to generate
wsdl for my web service.
I have a getN
One important addendum to my note about writing a Handler that
overrides generateWSDL():
>This code belongs in a Handler in the requestFlow
This Handler must be invoked in the *responseFlow*, not the requestFlow.
If you're calling MessageContext.setProperty("WSDL", ...) in the
request instead, Ax
Nelson,
yes, it's not cached. no specific reason for not doing it :) Yes, this code should
work
-- dims
--- Nelson Minar <[EMAIL PROTECTED]> wrote:
> I've been experimenting with overriding the WSDL that Axis provides in
> a dynamic fashion. Doing more than just substituting a static file.
> F
Sent: Thursday, April 15, 2004 3:28 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: WSDL generation problem
i don't have a ejb container so i tried to strip down the class and did
not see any problem. see
the java and build.xml enclosed.
-- dims
--- Rob Jellinghaus <[EMAIL PROT
o do in your Java code* (or even in your
> java2wsdl target) to fix this error, given the wording of the error
> itself.
>
> Cheers!
> Rob
>
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 15, 2004 2:28 PM
> To:
ic message?)
There's no way to know *what to do in your Java code* (or even in your
java2wsdl target) to fix this error, given the wording of the error
itself.
Cheers!
Rob
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 2:28 PM
To: [EMA
d a
> campaign object (via any of the campaign.set*() methods).
> * @param campaign
> * @throws NFNoSuchEntityException if no campaign with that ID exists
> */
>public void updateCampaign(
> com.nimblefish.core.domain.campaign.Campaign campaign )
> throws com.nimblefis
PROTECTED]
Sent: Thursday, April 15, 2004 2:24 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: WSDL generation problem
Rob, Jagannath,
you should not get this problem in Axis 1.2 Beta. If you do, then please
open a bug report.
thanks,
dims
--- Rob Jellinghaus <[EMAIL PROTECTED]> wr
Rob, Jagannath,
you should not get this problem in Axis 1.2 Beta. If you do, then please open a bug
report.
thanks,
dims
--- Rob Jellinghaus <[EMAIL PROTECTED]> wrote:
> If ever a problem deserved to be a FAQ on the Wiki, this is it. I had
> exactly the same problem only with "http://util.java
If ever a problem deserved to be a FAQ on the Wiki, this is it. I had
exactly the same problem only with "http://util.java"; instead of
"http://management.javax";. Overall the java2wsdl documentation MUST
describe what to do when this problem is hit
Cheers,
Rob
-Original Message-
Fr
Separate WSDL files proabably. Unless you can get away which
services are valid for which client type.
-Original Message-From: Doss Markus
[mailto:[EMAIL PROTECTED]Sent: Monday, August 11, 2003
10:03 AMTo: [EMAIL PROTECTED]Subject: WSDL
generation
Hi
all,
we pr
Read the Java2WSDL section of the user's manual:
http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.html
Russell Butek
[EMAIL PROTECTED]
Vinit Kumar <[EMAIL PROTECTED]> on 02/21/2002 11:02:32 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject:
13 matches
Mail list logo