jboss.net 3.1.0 alpha not generating wsdl

[essington]

how do I get jboss to generate wsdl information when I call

http://localhost:8080/axis/services/myService?wsdl

right now I am getting a response that says
AXIS error

Sorry, something seems to have gone wrong... here are the details:

java.lang.ClassCastException: $Proxy142

is there something I don't have configured correctly?

-jason

[scharlau]

Jason,

JBoss.NET is built using the axis-beta1 jar, which doesn't support generating wsdl files on the fly. Nor, can you swap the axis.jar in your jboss-all build setup for a newer axis-beta2 or axis-beta3 jar as the method calls are different, and your build won't work. I've tried, and it doesn't work that way. ;-(

However, after you've built the modules, you can swap out the axis.jar for one from the axis-beta2 (I've not tried this with axis-beta3, so don't know if that works.) This gives you an up-sie snd a down-side.

Upside: you can get the wsdl file for SOME services.
Downside: you can't connect to EJBs as the method calls don't work anymore.

cheers

Bruce

[jeffdelong]

I am able to generate wsdl from http://localhost:8080/axis/services/OrderService?wsdl
(see attached file)

I am using JBoss 3.0.0 with axis.jar dated 5/31/2002 which I copied into default/deploy from all/deploy. I do use the jax-rpc.jar and log4j-core from xml-axis-beta2, but those are the only jars from beta2. My service does connect to ejbs.

You are correct that if I try to use the axis.jar from beta2 axis generates a "no such operation" message.

[nusa]

Bruce,

I've tried to swap axis.jar from JBoss.Net with axis-beta3, but still it didn't work. I think the message about
QName methode, I forgot ...

Cheers,