Well....
It seems that this is an issue with our Resin application
server... For fun I brought our app up on a Tomcat install and it works just
fine...
So while it works under Tomcat, it fails under Resin... Any
ideas on why Resin (www.caucho.com) causes
the problem?
Thanks,
-Clint
-Clint
From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 11:51 AM
To: [email protected]
Subject: RE: Autogenerated WSDL still not adding wsdl: to types section
On the same note, is it possible to get axis 1.1 source /
jars any longer? All the mirrors are "down"...
cwd
From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 11:50 AM
To: [email protected]
Subject: RE: Autogenerated WSDL still not adding wsdl: to types section
So for fun I went back to our CVS and pulled the jars from
our project from last year (Dec 12 2005 to be precise) which was using axis
1.1.
Those jars produce a correct wsdl.
Thoughts?
cwd
From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 11:02 AM
To: [email protected]
Subject: Autogenerated WSDL still not adding wsdl: to types section
Hello
All,
I'm
wondering if this is still a problem for anyone (everyone)?
see
jira:
I'm
using axis 1.2.1, I've used 1.3, and the nightly 1.4 and I still do not get my
wsdl auto generated correctly... All I need to do is save the generated wsdl to
a file, add wsdl: manually to the types section and the wsdl works
fine.
Anybody else?
Is
this still an issue? is it getting worked?
-clint
