[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation

2007-03-17 Thread Davanum Srinivas (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481909
 ] 

Davanum Srinivas commented on AXIS2-1749:
-

Fixed in svn revision 519539

> Wrong Java2WSDL generation
> --
>
> Key: AXIS2-1749
> URL: https://issues.apache.org/jira/browse/AXIS2-1749
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.1
>Reporter: Jabber W
> Assigned To: Deepal Jayasinghe
> Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt, 
> axis2patch1749and2116-v3.txt, patch-1749.txt
>
>
> During the generation of type definitions Java2WSDL of axis2-1.1 flattens 
> chains of extender java data types to independent schema types without 
> extending relations between them, while Axis121 stores these relations by 
> . 
> For example: say,
>   class A { public String someString; public A someLink; } and
>   class B extends A { public int 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:
>  
>   
> 
> 
>
>  
> and
>  
>
>  
>  
>  
>
>  
> while B should be:
>  
>
>   
>   
> 
>  
>
>
>  
> Since complexType B is not extension of ? it (the B type element) can't be 
> passed as the someLink.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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



[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation

2007-03-15 Thread Geir Egil Hansen (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481515
 ] 

Geir Egil Hansen commented on AXIS2-1749:
-

Although it is possible to do restriction by inheritance in Java (and C++), 
there is no specific syntax denoting that is what is done. It's done only 
programatically.

So I cannot see how to differ between restriction and extension.  I think Axis2 
should always use extension.  Another thing; how will Axis2 generate client 
code (and server code for that matter) on WSDL's using restriction and/or 
extension?  Haven't checked this out yet. But I'm gonna!

> Wrong Java2WSDL generation
> --
>
> Key: AXIS2-1749
> URL: https://issues.apache.org/jira/browse/AXIS2-1749
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.1
>Reporter: Jabber W
> Assigned To: Deepal Jayasinghe
> Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt, 
> patch-1749.txt
>
>
> During the generation of type definitions Java2WSDL of axis2-1.1 flattens 
> chains of extender java data types to independent schema types without 
> extending relations between them, while Axis121 stores these relations by 
> . 
> For example: say,
>   class A { public String someString; public A someLink; } and
>   class B extends A { public int 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:
>  
>   
> 
> 
>
>  
> and
>  
>
>  
>  
>  
>
>  
> while B should be:
>  
>
>   
>   
> 
>  
>
>
>  
> Since complexType B is not extension of ? it (the B type element) can't be 
> passed as the someLink.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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



[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation

2007-03-15 Thread Manoj Khangaonkar (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481280
 ] 

Manoj Khangaonkar commented on AXIS2-1749:
--

Gier,

I meant it to be ComplexExtension , but looks like I made it 
ComplexRestriction. Good catch.

In java derived types extend base types - hence extension

Since this is java2WSDL - how do you model restriction in java ? In other 
words, can you think of a case in java code
where the corresponding schema needs to be restriction.

I will update the patch to generate https://issues.apache.org/jira/browse/AXIS2-1749
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.1
>Reporter: Jabber W
> Assigned To: Deepal Jayasinghe
> Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt, 
> patch-1749.txt
>
>
> During the generation of type definitions Java2WSDL of axis2-1.1 flattens 
> chains of extender java data types to independent schema types without 
> extending relations between them, while Axis121 stores these relations by 
> . 
> For example: say,
>   class A { public String someString; public A someLink; } and
>   class B extends A { public int 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:
>  
>   
> 
> 
>
>  
> and
>  
>
>  
>  
>  
>
>  
> while B should be:
>  
>
>   
>   
> 
>  
>
>
>  
> Since complexType B is not extension of ? it (the B type element) can't be 
> passed as the someLink.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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



[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation

2007-03-15 Thread Geir Egil Hansen (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481131
 ] 

Geir Egil Hansen commented on AXIS2-1749:
-

With the patch installed on Axis2 1.1.1 I now get 


shouldn't it be 


In my case, the sub-class is an extension to base rather than a restriction. 
Is there any cases where restriction is necessary? Couldn't extension always be 
used here?

I changed the patched a bit by replacing
XmlSchemaComplexContentRestriction complexRestriction = new 
XmlSchemaComplexContentRestriction();
with
XmlSchemaComplexContentExtension complexExtension = new 
XmlSchemaComplexContentExtension();

and of course replacing use of complexRestriction  with complexExtension. 

But the question is; When to use extension and when to use restriction, and how 
to switch between the two?


> Wrong Java2WSDL generation
> --
>
> Key: AXIS2-1749
> URL: https://issues.apache.org/jira/browse/AXIS2-1749
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.1
>Reporter: Jabber W
> Assigned To: Deepal Jayasinghe
> Attachments: axis2-1749and2116.txt, axis2patch1749and2116-v2.txt, 
> patch-1749.txt
>
>
> During the generation of type definitions Java2WSDL of axis2-1.1 flattens 
> chains of extender java data types to independent schema types without 
> extending relations between them, while Axis121 stores these relations by 
> . 
> For example: say,
>   class A { public String someString; public A someLink; } and
>   class B extends A { public int 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:
>  
>   
> 
> 
>
>  
> and
>  
>
>  
>  
>  
>
>  
> while B should be:
>  
>
>   
>   
> 
>  
>
>
>  
> Since complexType B is not extension of ? it (the B type element) can't be 
> passed as the someLink.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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



[jira] Commented: (AXIS2-1749) Wrong Java2WSDL generation

2007-02-11 Thread Manoj Khangaonkar (JIRA)

[ 
https://issues.apache.org/jira/browse/AXIS2-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472115
 ] 

Manoj Khangaonkar commented on AXIS2-1749:
--

Hi all,

I am working on this issue and will provide a patch shortly.

Mj

> Wrong Java2WSDL generation
> --
>
> Key: AXIS2-1749
> URL: https://issues.apache.org/jira/browse/AXIS2-1749
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: codegen
>Affects Versions: 1.1
>Reporter: Jabber W
> Assigned To: Deepal Jayasinghe
>
> During the generation of type definitions Java2WSDL of axis2-1.1 flattens 
> chains of extender java data types to independent schema types without 
> extending relations between them, while Axis121 stores these relations by 
> . 
> For example: say,
>   class A { public String someString; public A someLink; } and
>   class B extends A { public int 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:
>  
>   
> 
> 
>
>  
> and
>  
>
>  
>  
>  
>
>  
> while B should be:
>  
>
>   
>   
> 
>  
>
>
>  
> Since complexType B is not extension of ? it (the B type element) can't be 
> passed as the someLink.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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