Greatings
I'm working on a migration from Axis1.4 to Axis2 1.3.
We choosed to use the POJO approach since it seems to be the easiest
one. That means I don't generate my WSDL, they are autogenerated by
axis.
I am currently encountering 2 major problems.
- Beans presents in WSDL
Some of our services return different objects depending of the
parameters. To do so, we have a simple inheritance schema that look
like :
interface A
object B implements Aobject C implement A...
All the methods in the service return A, so by default the generated
WSDL only contains the definition of A.
In Axis1, there an extraClasses parameter in the WSDL that we were
using to declare objects B and C.I couldn't find an equivalent in
Axis2 (in the service.xml).I've read http://issues.apache.org/jira/
browse/AXIS2-1056, but it seem to fix only java2wsdl and this isn't
what I am looking for.Is there any way for it?or, in your opinion,
would a patch be easy to write?
- Beans description in WSDL for List :Some of the javabeans sent or
received by our webservices contains List
One nice feature in axis1 was that java.util.List were converted in
the WSDL as type="impl:ArrayOf_xsd_anyType"Now, it looks like
type="xs:anyType"
i tried to convert some of them ito arrays, just to see and i get
maxOccurs="unbounded" minOccurs="0" seems weird since it is not
explicitly said it is an array, but why not ...
problem is i used to use List<Number> as type and it's strangely
deserialized.is Number type supported by Axis2?is there an official
list of supported java types ?
thanks for your time and your answers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
