[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    RE: [jira] Commented: (XMLBEANS-253) .xsdconfig qname element should allow specifying only element o
From:       "Rizwan Ahmed" <rahmed () tibco ! com>
Date:       2006-03-17 22:45:08
Message-ID: B5ACD5B0D63ABA4FB1A1B6C467964FBDBF547C () NA-PA-VBE01 ! na ! tibco ! com
[Download RAW message or body]


Hello,

I am looking at creating a Java2WSDL tool using xmlbeans data binding.
I will have to generate the WSDL schema types from xmlbean objects.
I am wondering if anyone has tried anything similar.
At this stage I don't have much experience with XMLBeans, so I am
wondering if the XMLBean gurus have any suggestions about the
approach/practicality/limitations of such an effort.

Any suggestions are welcome.

Thanks,
Rizwan



-----Original Message-----
From: Lawrence Jones (JIRA) [mailto:xmlbeans-dev@xml.apache.org] 
Sent: Thursday, March 16, 2006 10:20 AM
To: xmlbeans-dev@xml.apache.org
Subject: [jira] Commented: (XMLBEANS-253) .xsdconfig qname element
should allow specifying only element or only complexType

    [
http://issues.apache.org/jira/browse/XMLBEANS-253?page=comments#action_1
2370731 ] 

Lawrence Jones commented on XMLBEANS-253:
-----------------------------------------

There is a similar issue where the schema has an anonymous inner type
e.g.:

	<xs:element name="service-type">
		<xs:complexType>
               .
               .
               .
		</xs:complexType>
	</xs:element> 

and then the .xsdconfig file has a <qname> element to rename the class
for <service-type>. As things stand the _inner_ interface which is
created for the anonymous type will end up as (java_name_for_outer_type
+ "2"). There is a request that it be original (non-xsdconfig) name for
the outer element (without the "Document" suffix of course). Not sure
how (if?) this affects backward compat.

> .xsdconfig qname element should allow specifying only element or only
complexType
>
------------------------------------------------------------------------
---------
>
>          Key: XMLBEANS-253
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-253
>      Project: XMLBeans
>         Type: Improvement
>   Components: Binding
>     Versions: Version 2.1
>  Environment: All
>     Reporter: Lawrence Jones
>     Assignee: Lawrence Jones
>     Priority: Minor
>      Fix For: TBD
>  Attachments: test.wsdl, test.xsdconfig
>
> Currently the <qname> element in .xsdconfig files allows only the name
and javaname attributes to be specified.
> If you have a schema with a global type and a global element with the
same name and you try to map that name to a non-default javaname using
the <qname> element in a .xsdconfig file then you will get that one of
them maps to the javaname and one of them maps to javaname + "2" in
order to avoid collisions. 
> Suggest that we update <qname> to allow a third attribute which
specifies whether this mapping applies to elements only, types only, or
both with default being both.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]