Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Stephane Roy]

Hi Amila,

Please could let me know the JIRA reference of the bug related to this 
problem ?

Thus, I could know when the problem is fixed in Axis2.

Thanks in advance.

Stephane Roy
Alcatel-Lucent

Amila Suriarachchi wrote:

Any way this is a bug and I fixed it for the trunk.

On 5/10/07, *Amila Suriarachchi* <[EMAIL PROTECTED] 
> wrote:


have you put elementFormDefault="qualified" in your schma?


On 5/10/07, *Stephane Roy* < [EMAIL PROTECTED]
> wrote:

Hi,

The XSD schema used by my WSDL defines the following types:

...
   
 

   
 
   
 
 
   
 
   

 
   
...

In short, typeA uses typeB, typeB being defined within typeA.


I generated the code for the server in adb mode with the command

$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd

Then in /tmp/my/dir/server/src, I have a java file for typeB,
for which
the package name is not set ('package ;'). As a result, the java
code
cannot be compiled.

I have this problem with Axis2.1.1.1 and with the latest release
(Axis2.1.2).


However, if I change my XSD schema, to have something like this:

...
   
 
   
   
 
   

   
 
   
   
 
   
...

In short, typeB is now defined at the top-level in the XSD
schema and
typeA defines elementB which uses a reference to typeB.

Now, the code generation in adb mode works fine and the java
files compile.


I would like to know if someone had this kind of problem before.
Is this behavior a known issue or a limitation of Axis2.1.x ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent


-- 
Amila Suriarachchi,
WSO2 Inc. 





--
Amila Suriarachchi,
WSO2 Inc.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Stephane Roy]

Hi Amila,

Thanks for your quick reply.

Please could let me know the reference of the bug related to this problem ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent

Amila Suriarachchi wrote:

Any way this is a bug and I fixed it for the trunk.

On 5/10/07, *Amila Suriarachchi* <[EMAIL PROTECTED] 
> wrote:


have you put elementFormDefault="qualified" in your schma?


On 5/10/07, *Stephane Roy* < [EMAIL PROTECTED]
> wrote:

Hi,

The XSD schema used by my WSDL defines the following types:

...
   
 

   
 
   
 
 
   
 
   

 
   
...

In short, typeA uses typeB, typeB being defined within typeA.


I generated the code for the server in adb mode with the command

$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd

Then in /tmp/my/dir/server/src, I have a java file for typeB,
for which
the package name is not set ('package ;'). As a result, the java
code
cannot be compiled.

I have this problem with Axis2.1.1.1 and with the latest release
(Axis2.1.2).


However, if I change my XSD schema, to have something like this:

...
   
 
   
   
 
   

   
 
   
   
 
   
...

In short, typeB is now defined at the top-level in the XSD
schema and
typeA defines elementB which uses a reference to typeB.

Now, the code generation in adb mode works fine and the java
files compile.


I would like to know if someone had this kind of problem before.
Is this behavior a known issue or a limitation of Axis2.1.x ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent

-- 
Amila Suriarachchi,
WSO2 Inc. 


--
Amila Suriarachchi,
WSO2 Inc.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Amila Suriarachchi]

Any way this is a bug and I fixed it for the trunk.

On 5/10/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:


have you put elementFormDefault="qualified" in your schma?

On 5/10/07, Stephane Roy <[EMAIL PROTECTED] > wrote:
>
> Hi,
>
> The XSD schema used by my WSDL defines the following types:
>
> ...
>
>  
>
>
>  
>
>  
>  
>
>  
>
>
>  
>
> ...
>
> In short, typeA uses typeB, typeB being defined within typeA.
>
>
> I generated the code for the server in adb mode with the command
>
> $AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
> /tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd
>
> Then in /tmp/my/dir/server/src, I have a java file for typeB, for which
> the package name is not set ('package ;'). As a result, the java code
> cannot be compiled.
>
> I have this problem with Axis2.1.1.1 and with the latest release
> (Axis2.1.2).
>
>
> However, if I change my XSD schema, to have something like this:
>
> ...
>
>  
>
>
>  
>
>
>
>  
>
>
>  
>
> ...
>
> In short, typeB is now defined at the top-level in the XSD schema and
> typeA defines elementB which uses a reference to typeB.
>
> Now, the code generation in adb mode works fine and the java files
> compile.
>
>
> I would like to know if someone had this kind of problem before.
> Is this behavior a known issue or a limitation of Axis2.1.x ?
>
> Thanks in advance.
>
> Stephane Roy
> Alcatel-Lucent
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Amila Suriarachchi,
WSO2 Inc.





--
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Incomplete code generation with wsdl2java, in adb mode

[Amila Suriarachchi]

have you put elementFormDefault="qualified" in your schma?

On 5/10/07, Stephane Roy <[EMAIL PROTECTED]> wrote:


Hi,

The XSD schema used by my WSDL defines the following types:

...
   
 

   
 
   
 
 
   
 
   

 
   
...

In short, typeA uses typeB, typeB being defined within typeA.


I generated the code for the server in adb mode with the command

$AXIS2_HOME/bin/wsdl2java.sh -uri myService.wsdl -p my.package -o
/tmp/my/dir/server -d adb -s -wv 1.1 -ss -sd

Then in /tmp/my/dir/server/src, I have a java file for typeB, for which
the package name is not set ('package ;'). As a result, the java code
cannot be compiled.

I have this problem with Axis2.1.1.1 and with the latest release
(Axis2.1.2).


However, if I change my XSD schema, to have something like this:

...
   
 
   
   
 
   

   
 
   
   
 
   
...

In short, typeB is now defined at the top-level in the XSD schema and
typeA defines elementB which uses a reference to typeB.

Now, the code generation in adb mode works fine and the java files
compile.


I would like to know if someone had this kind of problem before.
Is this behavior a known issue or a limitation of Axis2.1.x ?

Thanks in advance.

Stephane Roy
Alcatel-Lucent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Amila Suriarachchi,
WSO2 Inc.