corruption,
interception, amendment, tampering or viruses or any consequences thereof.
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: den 22 mars 2007 11:41
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java problem, Axis2 jaxbri
use jdk 1.5. jaxb
use jdk 1.5. jaxb only works with jdk 1.5
On 3/22/07, Reneta Säll (HF/EBC) <[EMAIL PROTECTED]> wrote:
Hi all,
When I run the code generator in Axis2, get this error:
C:\axis2\bin>WSDL2java -uri bank.wsdl -d jaxbri -g
Using AXIS2_HOME: C:\axis2
Using JAVA_HOME:C:\j2sdk1.4.2_12
Excepti
Your WSDL doesn't define a portType. It can't generate a Java interface if you haven't defined a WSDL interface.
AnneOn 1/18/06, Torsten Schmidt <[EMAIL PROTECTED]> wrote:
Hi,I've got another confusing Exception...Earlier I generated the WSDL files using AXIS 1.2 and everything was fine.But i need
he form +foo():FooResponse, and the
nowrapped flag made them take the form +foo(FooParams):FooResponse,
where FooParams has no fields. :-P.
Chris
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 12, 2005 05:33
To: axis-user@ws.apache.org
Subject
That worked. Thank you.On 11/12/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Hmmm...
Doesn't make sense to me why it isn't producing the signature you want,
but you might try adding another layer of wrapping in your response
message, so that when Axis unwraps the request, it returns a return
Hmmm...
Doesn't make sense to me why it isn't producing the signature you want,
but you might try adding another layer of wrapping in your response
message, so that when Axis unwraps the request, it returns a return
value rather than a set of parameters. e.g.:
lf, but I
am in heavy work in another project right now with a tight deadline.
Anyone tried this and met the same problem?
Geir
-Original Message-
From: Jan Bares [mailto:[EMAIL PROTECTED]
Sent: 27. oktober 2005 17:00
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java problem
Than
ry to generate the axis client from
that.
But there should be another solution. Sorry I couldn't help you.
-Original Message-
From: Jan Bares [mailto:[EMAIL PROTECTED]
Sent: 27. oktober 2005 15:03
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java problem
Thanks, but it do
axis client from
that.
But there should be another solution. Sorry I couldn't help you.
-Original Message-
From: Jan Bares [mailto:[EMAIL PROTECTED]
Sent: 27. oktober 2005 15:03
To: axis-user@ws.apache.org
Subject: Re: WSDL2Java problem
Thanks, but it doesn't help. Comparing the
Thanks, but it doesn't help. Comparing the generated files, nothing
changes with respect to the classes in problem. The QName for the
classes is registered even without -a. Does Axis handle this type of calls?
Jan
Hansen, Geir wrote:
When generating your client code, are you sure you tried t
When generating your client code, are you sure you tried the -a option
("generate code for all elements, even unreferenced ones").
See http://ws.apache.org/axis/java/reference.html WSDL2Java Reference
Geir
-Original Message-
From: Jan Bares [mailto:[EMAIL PROTECTED]
Sent: 27. oktobe
I suggest you file a bug.
Anne
On 6/27/05, Antonio Ruiz Martínez <[EMAIL PROTECTED]> wrote:
> Hello!
>
> Anne Thomas Manes wrote:
>
> Antonio,
>
> You're not the first person to ask exactly this question. I don't see
> what is unusual about the D-Sig schema that causes Axis to barf.
>
>
Antonio,
You're not the first person to ask exactly this question. I don't see
what is unusual about the D-Sig schema that causes Axis to barf.
Would you please try to embed the D-Sig schema inside your WSDL and
try it again?
Anne
On 6/25/05, Antonio Ruiz Martínez <[EMAIL PROTECTED]> wrote:
> H
13 matches
Mail list logo
