Hi
You agreed that (2) is a problematic behaviour but did not say anything about
(1). Do you mean that it is the way it should be done - or I just missed some
command-line or configuration flag? To be more specific - I'll try to explain
it a bit in more details though briefly:
say, there are data types:
class A { public String someString; public A someLink; }
and
class B extends A { public String someInt; }
and the exposed service is:
class MySvc { String myOp(A arg) {..} }
Running of Java2WSDL on it:
java2wsdl -cn MySvc -xc B
creates 2 non-related types:
<xs:complexType name="A">
<xs:sequence>
<xs:element name="someLink" type="ns:A"/>
<xs:element name="someString" type="xs:string"/>
</xs:sequence>
</xs:complexType>
and
<xs:complexType name="B">
<xs:sequence>
<xs:element name="someLink" type="ns:A"/>
<xs:element name="someString" type="xs:string"/>
<xs:element name="someInt" type="xs:int"/>
</xs:sequence>
</xs:complexType>
Since complexType B is not extension of А it (the B type element) can't be
passed as the someLink.
Do you consider it as a correct treatment?
Sincerely,
Alex
-----Original Message-----
From: Sanjiva Weerawarana <[EMAIL PROTECTED]>
To: javaDev <[EMAIL PROTECTED]>
Date: Thu, 16 Nov 2006 05:19:34 +0530
Subject: Re: [Axis2] Is Axis2 1.1 working for you?
>
> On Wed, 2006-11-15 at 23:07 +0300, javaDev wrote:
> > I wouldn't say it works for me, especially Java2WSDL:
> > 1) it flattens chains of extender java data types to independent schema
> > types without extending relations between them.
> > 2) it generates a notification-type operation for void methods even if it
> > throw application exception, as for:
> > public void addUser(User) throws UserDuplicationException {...}
>
> The latter is definitely a bug which needs to be fixed ASAP .. void
> methods aren't handled correctly. Please open a JIRA.
>
> Sanjiva.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
