I'm guessing that Axis is replacing any characters
that might be confused with XML markup, hence "<" is being
replaced with "<" and so on. I'm not sure why this wouldn't
get changed back again at the server side. Perhaps you can try defining
the parameter as a CDATA section, in your XML schema.
T
romJava.Emitter.setCls(Emitter.java:1477) atorg.apache.axis.wsdl.Java2WSDL.run(Java2WSDL.java:500) atorg.apache.axis.wsdl.Java2WSDL.main(Java2WSDL.java:542)
From: Ransel Lopez
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 29, 2004
12:38 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2Java p
Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Safdar AliSent: Thursday, January 29, 2004 1:27
PMTo: [EMAIL PROTECTED]Subject: Re: WSDL2Java
problem / Solution
Gourav, you are absolutely right for
WSDL2Java utility, we don't need all these
n jar files
Safdar.
- Original Message -
From:
Pani, Gourav
To: '[EMAIL PROTECTED]'
Sent: Thursday, January 29, 2004 9:02
PM
Subject: RE: WSDL2Java problem /
Solution
That's odd. The only thing I use in my CLASSPATH to do WSDL2Java
is
rsday, January 29, 2004 2:06
PMTo: [EMAIL PROTECTED]Subject: Re: WSDL2Java
problem / Solution
Hi all, (especially Lopez, Kondapalli,
Ashley)
Finally, after doing 3 days of brain storming.. I
have come to a solution for WSDL2Java problem where it throws Exception at
different l
MAIL PROTECTED]
Sent: Monday, January 26, 2004 5:07
PM
Subject: RE: WSDL2Java problem
Hi
Safdar,
I
have the same problem. I sent the same question and I didn't get any answer.
Please, if you find the solution let me know. I'll do the
same.
Thank you very muc
CTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 28, 2004 7:04 AM
Subject: Re: WSDL2Java problem
> Safdar,
>
> I believe you will find that the Java specs now state that any jars that
> change/add-to the java.* and javax.* packages must be in the endorsed
> directory o
Safdar,
I believe you will find that the Java specs now state that any jars that
change/add-to the java.* and javax.* packages must be in the endorsed
directory of your JRE/JDK.
If that is not the issue, I have had many similar issues with other
applications and it was easily solved by moving a
Title: Message
Hi
Safdar,
I
have the same problem. I sent the same question and I didn't get any answer.
Please, if you find the solution let me know. I'll do the
same.
Thank you very much
Ransel López, Web Services
Developer
Time Industrial,
Inc. An Outsourced
Contractor Time and Cos
Hi,
I too got the same problem..,both Java2WSDL and WSDL2Java are giving similar types of errors.I posted this question last week,but no repsonse :(
I even tried using IBM's wsdl4j.jar,but didnt work.
regards
Rao.,Safdar Ali <[EMAIL PROTECTED]> wrote:
Hello,
I am getting the following er
- Original Message -
From: "Alan Moore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 9:38 AM
Subject: RE: WSDL2JAVA problem
> I didn't use the ant task but instead used the task. It has
a
> fork option that I found was r
anks!
Anuj.
> -Original Message-
> From: Alan Moore [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 21, 2002 12:38 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: WSDL2JAVA problem
>
>
> I didn't use the ant task but instead used the
> task. It has a
]
> Sent: Monday, May 20, 2002 5:22 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: WSDL2JAVA problem
>
>
> Well, we have crimson.jar in our CLASSPATH (see in
> our ant target below). I've tried replacing that with
> xerces.jar but no dice. 8( Also, we&#
wade through the
code and see.
Thanks,
Han
-Original Message-
From: Simon McClenahan [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 20, 2002 5:10 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL2JAVA problem
The first thing I would check is to make sure that you have an XML parser in
your
anks.
Anuj.
> -Original Message-
> From: Simon McClenahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 20, 2002 5:10 PM
> To: [EMAIL PROTECTED]
> Subject: RE: WSDL2JAVA problem
>
>
> The first thing I would check is to make sure that you have
> an XML parser in
- Original Message -
From: "R. Lake" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 20, 2002 3:17 PM
Subject: Re: WSDL2JAVA problem
> This is possibly a similar effect I'm seeing except with Java2WSDL. I've
> tried setting the classp
This is possibly a similar effect I'm seeing except with Java2WSDL. I've
tried setting the classpath to ".;xerces.jar" to get example 6 of the user
guide working so perhaps there's a conflict between Xerces and JDK1.4? The
other examples must have picked up and used the JDK parser correctly in
ord
arser is available, even though Axis does not give
any hint to that being the cause.
cheers,
Simon
> -Original Message-
> From: Han Wang [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 20, 2002 4:03 PM
> To: [EMAIL PROTECTED]
> Subject: RE: WSDL2JAVA problem
>
One more problem:
I'm getting a null pointer exception and no description of the problem:
[apply] java.lang.NullPointerException
[apply] at org.apache.axis.wsdl.toJava.Utils.holder(Utils.java:494)
[apply] at
org.apache.axis.wsdl.toJava.JavaWriterFactory.constructSignat
ure(Ja
I discovered another problem with the code generation:
(AXIS Beta 2)
In WSDL:
Generated Java:
public class TpOctet implements java.io.Serializable,
org.apache.axis.encoding.SimpleType {
private byte[] value;
Hi,
JSSE needs a little more configuration. Have a look at
http://xml.apache.org/soap/docs/install/FAQ_Tomcat_SOAP_SSL.html
There is an updated version for Axis which I don't find right now. It's
essentially the same procedure as described by the document mentioned above.
HTH, Sven
--
Title: WSDL2JAVA Problem
Sounds
like you need to configure your JDK to support https URLs.
I
don't believe this is supported right out of the box...
There
should be info in the Java documentation about this, but I don't have a pointer
handy.
--
Tom
Jordahl
Macromedia
-Original Me
Are you sure you're using wsdl4j.jar that comes with AXIS? I understand
there's another one floating around that's incompatible.
Russell Butek
[EMAIL PROTECTED]
Frank van Lingen <[EMAIL PROTECTED]> on 03/12/2002 07:37:56 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Sub
Could you send me the wsdl file.
Thanks
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
oliver.kowalke@t-
Show me your WSDL and the WSDL2Java command you used.
Russell Butek
[EMAIL PROTECTED]
"Jean Marc Taillant" <[EMAIL PROTECTED]> on 02/07/2002 04:44:34
AM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: WSDL2Java problem when generating complex type package?
Hi a
have with the whole document vs. rpc and literal
vs. encoded mess.
--
Tom Jordahl
Macromedia
-Original Message-
From: Brette, Marc [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 12:37 PM
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL2Java problem with complex ty
al Message-
From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
Sent: 06 February 2002 18:10
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL2Java problem with complex type ?
There is a bug, which I have a fix for and will check in to the CVS tree
shortly.
The stub still doesn't work however.
e WSDL and generate stubs...
I am still looking at it, but no promises for a short term fix. :-)
--
Tom Jordahl
-Original Message-
From: Brette, Marc [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 11:27 AM
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL2Java problem with c
Thanks for your help.
-Original Message-
From: Tom Jordahl [mailto:[EMAIL PROTECTED]]
Sent: 06 February 2002 16:45
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL2Java problem with complex type ?
In looking at the WSDL, this is strange:
http://schemas.xmlsoap.org/soap/encoding/"; />
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 10:43 AM
To: 'Russell Butek'; '[EMAIL PROTECTED]'
Subject: RE: WSDL2Java problem with complex type ?
The rpc/literal case isn't handled correctly by the emitter, as you discovered. This
is mostly because w
out that simple. :-(
--
Tom Jordahl
Macromedia
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 06, 2002 8:48 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: WSDL2Java problem with complex type ?
The soap:body in the binding says use=&
Butek [mailto:[EMAIL PROTECTED]]
Sent: 06 February 2002 14:48
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: WSDL2Java problem with complex type ?
The soap:body in the binding says use="literal". This means that the outer
layer - getRTQuote/getRTQuoteResponse - is stripped and the
The soap:body in the binding says use="literal". This means that the outer
layer - getRTQuote/getRTQuoteResponse - is stripped and the contents of the
complexType are in the parameter list instead of the complexType itself, so
nothing need be generated for the complexType.
Now that that's explai
33 matches
Mail list logo
