Hi,
thanks to Mark and
Kevin, we could now trace that the WSDL-Emitter driver code in the Axis1.1
EJBProvider is flawed.
It has the
"stopClasses" meta-attribute not set such that the wsdl generator also
tries to build wsdl descriptions for methods declared in EJB interfaces
(and produces a lot of namespace-exceptions since the datatypes used there are
not Web Service compatible).
JBoss.net
EJBProvider now has the stopClasses set, again, and should produce more
reasonable WSDL-output (provided that your exposed business methods/datatypes
are mapped accordingly).
This has been
fixed in head and 3.2
CGJ
########################################### |
Title: Nachricht