[jira] Created: (JAXME-105) can't generate get list method with element has maxOccurs=unbounded
can't generate get list method with element has maxOccurs=unbounded - Key: JAXME-105 URL: https://issues.apache.org/jira/browse/JAXME-105 Project: JaxMe Issue Type: Bug Components: JaxMe Core Affects Versions: current (nightly) Environment: wiindow xp, j2se 1.6 Reporter: chan tsz yeung Fix For: current (nightly) Dear all, I have a xsd file. One of the element contains maxOccurs=unbounded tag. However, after running ant with default build.xml. The generated interface file only contains public java.util.List getAddress(); function but no corresponding get method generated. Could you please advise? Thanks. Stephen -- 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: jaxme-dev-unsubscr...@ws.apache.org For additional commands, e-mail: jaxme-dev-h...@ws.apache.org
[jira] Resolved: (JAXME-105) can't generate get list method with element has maxOccurs=unbounded
[ https://issues.apache.org/jira/browse/JAXME-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Wiedmann resolved JAXME-105. --- Assignee: Jochen Wiedmann Resolution: Invalid I assume, that you mean no corresponding set method generated? If so, that's perfectly as requested by the JAXB spec, thus an intentional behaviour. To set your elements, use object.getAddress().clear(); object.getAddress().addAll(myAddresses); can't generate get list method with element has maxOccurs=unbounded - Key: JAXME-105 URL: https://issues.apache.org/jira/browse/JAXME-105 Project: JaxMe Issue Type: Bug Components: JaxMe Core Affects Versions: current (nightly) Environment: wiindow xp, j2se 1.6 Reporter: chan tsz yeung Assignee: Jochen Wiedmann Fix For: current (nightly) Dear all, I have a xsd file. One of the element contains maxOccurs=unbounded tag. However, after running ant with default build.xml. The generated interface file only contains public java.util.List getAddress(); function but no corresponding get method generated. Could you please advise? Thanks. Stephen -- 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: jaxme-dev-unsubscr...@ws.apache.org For additional commands, e-mail: jaxme-dev-h...@ws.apache.org
Get minOccurs and maxOccurs attributes from an element
hello
i tried to parse XML schema to my own data structure.
when i tried to find out if an element can appear more than one time
(maxOccurs 0), i found that this property is not exposed - XSElement
expose only the name attribute of an element, and not the min/max Occurs
attributes.
i forced to create my own XSElementImpl, and expose the min/max attributes
myself. for example:
*public* *int* getMaxOccurs()
{
* return* ((XsTElement)getXsObject()).getMaxOccurs();
}
mybe you should add these methods (get min/max) to the XSElement interface?
thanks,
Jona.
Error message while generating java classes : Model groups with maxOccurs 1 are not yet supported.
Hi, i am new to jaxMe and trying to generate java classes uusing attached xsd.But while generating java classes i am getting following error : Build Failed: Model groups with maxOccurs 1 are not yet supported. the xsd is xs:group name=Directory xs:sequence xs:element name=Directory minOccurs=0 maxOccurs=unbounded xs:complexType xs:group ref=Directory minOccurs=0 maxOccurs=unbounded / xs:attribute name=content type=xs:string default=all/ xs:attribute name=path type=xs:string/ /xs:complexType xs:element name=File minOccurs=0 maxOccurs=unbounded xs:complexType xs:attribute name=Name type=xs:string/ /xs:complexType /xs:element /xs:sequence /xs:group for the follwoing xml: Directory content=all type=local path=C:\Examples\StoryBoarding file path=C:\Examples\StoryBoarding\test1.xml/ Directory content=all type=local path=C:\Examples\StoryBoarding\NewFolder file path=C:\Examples\StoryBoarding\NewFolder\shobha.txt/ /Directory /Directory i tried using complex type but in complex type the order of occurrence of directory and file matters.means diretory inside directory should come after file.but i dont want any dependancies. i wud be very thankfull if someone could tell me the solution thank in advance. Regards, Shobha -- View this message in context: http://www.nabble.com/Error-message-while-generating-java-classes-%3A-Model-groups-with-maxOccurs-%3E-1-are-not-yet-supported.-tf4586287.html#a13091520 Sent from the JaxMe - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error message while generating java classes : Model groups with maxOccurs 1 are not yet supported.
Hi Jose, Thanks for the help but i cant change the xml b'coz its request i mean i am getting this request.xml file as request and i want to process the request.The request is auto generated xml file. is there any another way? Regards, Shobha Jose Luis Huertas Fernández wrote: Hi Shobba, I'm afraid you will have to use a workaround until this feature is implemented :( This could be a possible solution. It's a bit ugly because it introduces a new artificial element (directoryelement) which can be a directory or a file, but it works: ?xml version=1.0 encoding=utf-8? xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; elementFormDefault=qualified attributeFormDefault=unqualified xs:element name=directory xs:complexType xs:sequence xs:element name=directoryelement minOccurs=0 maxOccurs=unbounded xs:complexType xs:choice xs:element ref=directory/ xs:element name=file xs:complexType xs:attribute name=name type=xs:string/ /xs:complexType /xs:element /xs:choice /xs:complexType /xs:element /xs:sequence xs:attribute name=content type=xs:string default=all/ xs:attribute name=type type=xs:string/ xs:attribute name=path type=xs:string/ /xs:complexType /xs:element /xs:schema Now you can validate XML like this: ?xml version=1.0 encoding=utf-8? directory xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=file:///D:/temp/directory.xsd content=all type=local path=C:\Examples\StoryBoarding directoryelement directory content=all type=local path=C:\Examples\StoryBoarding\NewFolder directoryelement file name=C:\Examples\StoryBoarding\NewFolder\shobha.txt/ /directoryelement /directory /directoryelement directoryelement file name=C:\Examples\StoryBoarding\test1.xml/ /directoryelement /directory or this (different order): ?xml version=1.0 encoding=utf-8? directory xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=file:///D:/temp/directory.xsd content=all type=local path=C:\Examples\StoryBoarding directoryelement file name=C:\Examples\StoryBoarding\test1.xml/ /directoryelement directoryelement directory content=all type=local path=C:\Examples\StoryBoarding\NewFolder directoryelement file name=C:\Examples\StoryBoarding\NewFolder\shobha.txt/ /directoryelement /directory /directoryelement /directory Hope this helps, Jose Luis. 2007/10/8, shobha [EMAIL PROTECTED]: Hi, i am new to jaxMe and trying to generate java classes uusing attached xsd.But while generating java classes i am getting following error : Build Failed: Model groups with maxOccurs 1 are not yet supported. the xsd is xs:group name=Directory xs:sequence xs:element name=Directory minOccurs=0 maxOccurs=unbounded xs:complexType xs:group ref=Directory minOccurs=0 maxOccurs=unbounded / xs:attribute name=content type=xs:string default=all/ xs:attribute name=path type=xs:string/ /xs:complexType xs:element name=File minOccurs=0 maxOccurs=unbounded xs:complexType xs:attribute name=Name type=xs:string/ /xs:complexType /xs:element /xs:sequence /xs:group for the follwoing xml: Directory content=all type=local path=C:\Examples\StoryBoarding file path=C:\Examples\StoryBoarding\test1.xml/ Directory content=all type=local path=C:\Examples\StoryBoarding\NewFolder file path=C:\Examples\StoryBoarding\NewFolder\shobha.txt/ /Directory /Directory i tried using complex type but in complex type the order of occurrence of directory and file matters.means diretory inside directory should come after file.but i dont want any dependancies. i wud be very thankfull if someone could tell me the solution thank in advance. Regards, Shobha -- View this message in context: http://www.nabble.com/Error-message-while-generating-java-classes-%3A-Model-groups-with-maxOccurs-%3E-1-are-not-yet-supported.-tf4586287.html#a13091520 Sent from the JaxMe - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Error-message-while-generating-java-classes-%3A-Model-groups-with-maxOccurs-%3E-1-are-not-yet-supported.-tf4586287.html#a13093145 Sent from the JaxMe - Dev mailing list archive at Nabble.com
Error message while generating java classes using jaxme: Model groups with maxOccurs 1 are not yet supported in jaxme
Hi, i am new to jaxMe and trying to generate java classes uusing attached xsd.But while generating java classes i am getting following error : Build Failed: Model groups with maxOccurs 1 are not yet supported. the xsd is xs:group name=Directory xs:sequence xs:element name=Directory minOccurs=0 maxOccurs=unbounded xs:complexType xs:group ref=Directory minOccurs=0 maxOccurs=unbounded / xs:attribute name=content type=xs:string default=all/ xs:attribute name=path type=xs:string/ /xs:complexType xs:element name=File minOccurs=0 maxOccurs=unbounded xs:complexType xs:attribute name=Name type=xs:string/ /xs:complexType /xs:element /xs:sequence /xs:group for the follwoing xml: Directory content=all type=local path=C:\Examples\StoryBoarding file path=C:\Examples\StoryBoarding\test1.xml/ Directory content=all type=local path=C:\Examples\StoryBoarding\NewFolder file path=C:\Examples\StoryBoarding\NewFolder\shobha.txt/ /Directory /Directory i tried using complex type but in complex type the order of occurrence of directory and file matters.means diretory inside directory should come after file.but i dont want any dependancies. i wud be very thankfull if someone could tell me the solution thank in advance. Regards, Shobha
maxOccurs
And why JaxMe doesn't want to work with maxOccurs=unbounded? How I may have this functionality? _ From: Denis Bessmertnyj [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 28, 2007 11:27 AM To: 'jaxme-dev@ws.apache.org' Subject: anyType Hi, I cannot understand, how I may have xsd:anyType functionality in my schema. What I need to use for your compiler working properly? - Denis
Re: maxOccurs
On 8/28/07, Denis Bessmertnyj [EMAIL PROTECTED] wrote: I have xsd:sequence minOccurs=0 maxOccurs=unbounded xsd:element name=titel type=xsd:string / xsd:element name=isbn type=xsd:string / . And receive org.apache.maven.lifecycle.LifecycleExecutionException: Model groups with maxOccurs 1 are not yet supported. You asked for maxOccurs in general. As the error message indicates, maxOccurs=unbounded is supported, except for model groups. Jochen -- Besides, manipulating elections is under penalty of law, resulting in a preventative effect against manipulating elections. The german government justifying the use of electronic voting machines and obviously believing that we don't need a police, because all illegal actions are forbidden. http://dip.bundestag.de/btd/16/051/1605194.pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maxOccurs=unbounded
If I define a schema with an element that has a maxOccurs=unbounded, JaxMe generates a List getMyElement(), but no corresponding setter. Thats a bit of a drag when Im trying to create such a document. I expect that the parser was implemented but not the writer. Any ideas when that might be implemented? Need a beta tester? Neil
Re: maxOccurs=unbounded
On 8/18/05, Neil Pitman [EMAIL PROTECTED] wrote: If I define a schema with an element that has a maxOccurs=unbounded, JaxMe generates a List getMyElement(), but no corresponding setter. That's a bit of a drag when I'm trying to create such a document. I expect that the parser was implemented but not the writer. See http://mail-archives.apache.org/mod_mbox/ws-jaxme-dev/200507.mbox/[EMAIL PROTECTED] Jochen -- What are the first steps on the moon, compared to your child's? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JAXME-63) JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/
JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/ - Key: JAXME-63 URL: http://issues.apache.org/jira/browse/JAXME-63 Project: JaxMe Type: Bug Components: JaxMe Core Versions: current (nightly) Environment: JDK 1.5.0, JaxMe CVS Reporter: Fredrik Vraalsen JaxMe accepts (and generates faulty code for) the following schema: xs:group name=params xs:choice xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:group xs:element name=call xs:complexType xs:group ref=params maxOccurs=unbounded/ /xs:complexType /xs:element However, it should give an error message about not supporting model groups with maxOccurs 1, as it does with the following schema: xs:element name=call xs:complexType xs:choice maxOccurs=unbounded xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:complexType /xs:element Perhaps somewhat related to JAXME-61, but I think the correct behaviour would be to fail with an error message on the first schema above until support for groups with maxOccurs 1 is working? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Aktualisiert: (JAXME-63) JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/
[ http://issues.apache.org/jira/browse/JAXME-63?page=all ] Jochen Wiedmann updated JAXME-63: - Attachment: JAXME63.patch Patch for the problem. JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/ - Key: JAXME-63 URL: http://issues.apache.org/jira/browse/JAXME-63 Project: JaxMe Type: Bug Components: JaxMe Core Versions: current (nightly) Environment: JDK 1.5.0, JaxMe CVS Reporter: Fredrik Vraalsen Fix For: 0.5 Attachments: JAXME63.patch JaxMe accepts (and generates faulty code for) the following schema: xs:group name=params xs:choice xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:group xs:element name=call xs:complexType xs:group ref=params maxOccurs=unbounded/ /xs:complexType /xs:element However, it should give an error message about not supporting model groups with maxOccurs 1, as it does with the following schema: xs:element name=call xs:complexType xs:choice maxOccurs=unbounded xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:complexType /xs:element Perhaps somewhat related to JAXME-61, but I think the correct behaviour would be to fail with an error message on the first schema above until support for groups with maxOccurs 1 is working? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Geschlossen: (JAXME-63) JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/
[ http://issues.apache.org/jira/browse/JAXME-63?page=all ] Jochen Wiedmann closed JAXME-63: Fix Version: 0.5 Resolution: Fixed Assign To: Jochen Wiedmann Interesting ... you've found some of the (surprisingly few) problems in the XS part. JaxMe (wrongly) accepts schema using group ref=... maxOccurs=unbounded/ - Key: JAXME-63 URL: http://issues.apache.org/jira/browse/JAXME-63 Project: JaxMe Type: Bug Components: JaxMe Core Versions: current (nightly) Environment: JDK 1.5.0, JaxMe CVS Reporter: Fredrik Vraalsen Assignee: Jochen Wiedmann Fix For: 0.5 Attachments: JAXME63.patch JaxMe accepts (and generates faulty code for) the following schema: xs:group name=params xs:choice xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:group xs:element name=call xs:complexType xs:group ref=params maxOccurs=unbounded/ /xs:complexType /xs:element However, it should give an error message about not supporting model groups with maxOccurs 1, as it does with the following schema: xs:element name=call xs:complexType xs:choice maxOccurs=unbounded xs:element name=string type=xs:string/ xs:element name=int type=xs:int/ xs:element name=boolean type=xs:boolean/ /xs:choice /xs:complexType /xs:element Perhaps somewhat related to JAXME-61, but I think the correct behaviour would be to fail with an error message on the first schema above until support for groups with maxOccurs 1 is working? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
