You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jaxme-dev@ws.apache.org by Denis Bessmertnyj <db...@ciklum.net> on 2007/08/28 10:30:48 UTC
maxOccurs
And why JaxMe doesn't want to work with maxOccurs="unbounded"?
How I may have this functionality?
_____
From: Denis Bessmertnyj [mailto:dbe@ciklum.net]
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
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 8/28/07, Denis Bessmertnyj <db...@ciklum.net> 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: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
RE: maxOccurs
Posted by Denis Bessmertnyj <db...@ciklum.net>.
Jochen,
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.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Model groups with
maxOccurs > 1 are not yet supported.
at
org.apache.ws.jaxme.maven.plugins.JaxMeGoal.runGenerator(JaxMeGoal.java:551)
at
org.apache.ws.jaxme.maven.plugins.JaxMeGoal.execute(JaxMeGoal.java:498)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:539)
... 16 more
Caused by: org.xml.sax.SAXParseException: Model groups with maxOccurs > 1
are not yet supported.
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexContentTypeSG.verify(JAXBCo
mplexContentTypeSG.java:203)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexContentTypeSG.initialize(JA
XBComplexContentTypeSG.java:118)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexContentTypeSG.getLocalEleme
ntParticles(JAXBComplexContentTypeSG.java:124)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexContentTypeSG.getElementPar
ticles(JAXBComplexContentTypeSG.java:130)
at
org.apache.ws.jaxme.generator.sg.impl.ComplexContentSGImpl.getElementParticl
es(ComplexContentSGImpl.java:42)
at
org.apache.ws.jaxme.generator.sg.impl.ccsg.BeanGeneratingVisitor.startComple
xContent(BeanGeneratingVisitor.java:99)
at
org.apache.ws.jaxme.generator.sg.impl.ccsg.ParticleWalker.walk(ParticleWalke
r.java:36)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexTypeSG.createXMLBean(JAXBCo
mplexTypeSG.java:206)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBComplexTypeSG.getXMLInterface(JAXB
ComplexTypeSG.java:182)
at
org.apache.ws.jaxme.generator.sg.impl.ComplexTypeSGImpl.getXMLInterface(Comp
lexTypeSGImpl.java:46)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBTypeSG.generate(JAXBTypeSG.java:25
2)
at
org.apache.ws.jaxme.generator.sg.impl.TypeSGImpl.generate(TypeSGImpl.java:92
)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.generate(JAXBSchemaSG.jav
a:223)
at
org.apache.ws.jaxme.generator.sg.impl.SchemaSGImpl.generate(SchemaSGImpl.jav
a:67)
at
org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorImpl.java
:148)
at
org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorImpl.java
:180)
at
org.apache.ws.jaxme.maven.plugins.JaxMeGoal.runGenerator(JaxMeGoal.java:549)
... 19 more
-----Original Message-----
From: Jochen Wiedmann [mailto:jochen.wiedmann@gmail.com]
Sent: Tuesday, August 28, 2007 11:33 AM
To: Denis Bessmertnyj
Cc: jaxme-dev@ws.apache.org
Subject: Re: maxOccurs
On 8/28/07, Denis Bessmertnyj <db...@ciklum.net> wrote:
> And why JaxMe doesn't want to work with maxOccurs="unbounded"?
Look into the "examples" folder. It contains schemata with
maxOccurs="unbounded", that work very well.
--
"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: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org
Re: maxOccurs
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 8/28/07, Denis Bessmertnyj <db...@ciklum.net> wrote:
> And why JaxMe doesn't want to work with maxOccurs="unbounded"?
Look into the "examples" folder. It contains schemata with
maxOccurs="unbounded", that work very well.
--
"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: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org