On 5/18/05, Calmbach, Richard <[EMAIL PROTECTED]> wrote:
> One thing I notice is that the manual still describes some features as
> not supported by JaxMe, whereas the XJCTask javadoc does not have those
> warnings (e.g., external schema bindings). Which one is closer to the
> truth I don't know a
The "schemaReader" change is the main thing. As a side effect, the
description of the "classpath" nested element needs updating, too, since
it talks about the "schemaReader" attribute, which is now a nested
element.
One thing I notice is that the manual still describes some features as
not support
Nacho G. Mac Dowell wrote:
...However I would like to ask if when you find a bug you
could file it to JIRA. This way it doesn't get lost in the mailing
lists.
I would have, but Jira appeared to be a royal pain to use. (Last I
checked, the bug-entry page was horribly wide, not even fitting in a
Hi Richard, from what I've been looking this only applies to
schemaReader, correct?
regards,
nacho
Richard Calmbach (JIRA) wrote:
Tables in manual chapter 2 need updating
Key: JAXME-53
URL: http://issues.apache.org/jira/browse/JAXME-53
For input like this:
...
...
when JaxMeXS creates an XSAttribute object, isGlobal() returns false.
Attached is a test program that demonstrates the problem.
This seems to apply to JaxMeXS in JaxMe 0.3.1, 0.4beta, and
the current default CVS branch (HEAD?).
Daniel
package
For input like this:
...
...
when JaxMeXS creates an XSAttribute object, isGlobal() returns false.
Attached is a test program that demonstrates the problem.
This seems to apply to JaxMeXS in JaxMe 0.3.1, 0.4beta, and
the current default CVS branch (HEAD?).
Daniel
packag
For input like this:
...
...
when JaxMeXS creates an XSComplexType object, both
isRestriction() and isExtension() return false.
The XML Schema specification says:
[Definition:] Except for a distinguished ·ur-type definition·,
every ·type definition· is, by construction, either a ·r
Hi Daniel, thank you very much for your input. It is greatly
appreciated. However I would like to ask if when you find a bug you
could file it to JIRA. This way it doesn't get lost in the mailing
lists. I would also like to note that I couldn't reproduce some of the
bugs you talk about. In part
On 5/16/05, Daniel Barclay <[EMAIL PROTECTED]> wrote:
> JaxMeXS generates an incorrect object structure. It inserts the
> representation of an extra element above the representation
> of the element, and leaves a null pointer in the particles
> list.
Hmmm. The use of xs:extension builds an *im
[ http://issues.apache.org/jira/browse/JAXME-53?page=comments#action_65594
]
Jochen Wiedmann commented on JAXME-53:
--
Patches welcome ... :-)
> Tables in manual chapter 2 need updating
>
>
> Key: J
Jochen Wiedmann wrote:
On 5/16/05, Daniel Barclay <[EMAIL PROTECTED]> wrote:
JaxMeXS ... inserts the
representation of an extra element above the representation
of the element, and leaves a null pointer in the particles
list.
Hmmm. The use of xs:extension builds an *implicit* sequence,
consisti
Hi, Daniel,
please file a patch for that one, which suggests what you would like
being changed. I'll look into the other one (the IllegalStateException).
IMO, the main difference between the SAXParseException and the
LocSAXException should be, that the latter contains system ID, line and
column
Tables in manual chapter 2 need updating
Key: JAXME-53
URL: http://issues.apache.org/jira/browse/JAXME-53
Project: JaxMe
Type: Bug
Versions: current (nightly), future (enh)
Environment: N/A
Reporter: Richard Calmb
When given input like this:
...
...
JaxMeXS generates an incorrect object structure. It inserts the
representation of an extra element above the representation
of the element, and leaves a null pointer in the particles
list.
Mor
In JaxMeXS, the XSComplexType methods isEmpty(), isMixed(), and
isElementOnly() throw IllegalStateException if hasSimpleContent()
returns true.
This is inconsistent with other sets of methods that represent mutually
exclusive cases and with the XML Schema specification's treatment of the
cases.
Tho
15 matches
Mail list logo
