[ http://issues.apache.org/jira/browse/JAXME-47?page=comments#action_57622
]
Jochen Wiedmann commented on JAXME-47:
--
This is how a union converts a string at runtime: For any possible type, in the
order specified by the schema, it attempts to conv
[ http://issues.apache.org/jira/browse/JAXME-48?page=all ]
Jochen Wiedmann updated JAXME-48:
-
Attachment: JAXME-48.patch
Go on and check it in. Don't forget to edit your record in the status file. And
please be so kind to check it into HEAD and v0_4.
[ http://issues.apache.org/jira/browse/JAXME-49?page=comments#action_63764
]
Jochen Wiedmann commented on JAXME-49:
--
AFAIK, the specification requires only, that global elements be serializable.
In other words, what you request is *not* portable.
[ http://issues.apache.org/jira/browse/JAXME-50?page=comments#action_64619
]
Jochen Wiedmann commented on JAXME-50:
--
Nacho, I think you are referring to the use of "propertyName" in the
getXMLFieldName() method?
My preliminary impression is, that
[ http://issues.apache.org/jira/browse/JAXME-50?page=all ]
Jochen Wiedmann updated JAXME-50:
-
Attachment: jaxme50-0.4.patch
jaxme50-HEAD.patch
Please verify, whether the attached patch works. (Nice example for cooperation,
this bug, btw.
[ http://issues.apache.org/jira/browse/JAXME-50?page=all ]
Jochen Wiedmann closed JAXME-50:
Resolution: Fixed
Patch applied to 0.4 branch and HEAD.
> The generation of isSet methods generates wrong code
> --
[ http://issues.apache.org/jira/browse/JAXME-51?page=all ]
Jochen Wiedmann closed JAXME-51:
Resolution: Invalid
I admit, that this policy is not what I would expect as well. Nevertheless, it
is intentional, following the JAXB specification (see quo
[ http://issues.apache.org/jira/browse/JAXME-52?page=all ]
Jochen Wiedmann closed JAXME-52:
Resolution: Won't Fix
One addition to Nacho's explanations: You may use the jaxb:property/@name
customization to work around the problem. See
http://cvs.ap
[ http://issues.apache.org/jira/browse/JAXME-52?page=comments#action_65176
]
Jochen Wiedmann commented on JAXME-52:
--
The schemaBindings element allows to specify a suffix for element names, as in
This is an untest
[ 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
[ http://issues.apache.org/jira/browse/JAXME-54?page=all ]
Jochen Wiedmann closed JAXME-54:
Resolution: Invalid
Use ISO8859-1, not ISO-8859-1.
> ISO-8859-1 encoding not working correctly.
> --
>
> K
[ http://issues.apache.org/jira/browse/JAXME-54?page=comments#action_65854
]
Jochen Wiedmann commented on JAXME-54:
--
Charset is a Java 1.4 class. We cannot use that.
> ISO-8859-1 encoding not working correctly.
> -
[ http://issues.apache.org/jira/browse/JAXME-55?page=all ]
Jochen Wiedmann closed JAXME-55:
Resolution: Fixed
Without having too much ideas about wsdl ant the like, I do
believe, that you have an error here:
Most possibly, this should be
[ http://issues.apache.org/jira/browse/JAXME-57?page=all ]
Jochen Wiedmann closed JAXME-57:
Resolution: Invalid
- Please, do file bug reports only, if you believe you have
found a bug. As you say yourself, you are new to this kind
of stuff and t
[ http://issues.apache.org/jira/browse/JAXME-56?page=all ]
Jochen Wiedmann closed JAXME-56:
Resolution: Duplicate
You are still using an attribute "arrayType" without prefix. This is
invalid. I do not know, what the correct prefix would be, but the
[
http://issues.apache.org/jira/browse/JAXME-58?page=comments#action_12315891 ]
Jochen Wiedmann commented on JAXME-58:
--
A question which came up while discussing the feature: To resolve IDREF's, the
parser will obviously create an internal Map of ID =>
[
http://issues.apache.org/jira/browse/JAXME-58?page=comments#action_12315892 ]
Jochen Wiedmann commented on JAXME-58:
--
Proposed way to resolve the issue;
Forgetting for a moment, that the actual bean classes need changes,
I'll suggest that we start wi
Nestes groups with multiplicity 1
-
Key: JAXME-60
URL: http://issues.apache.org/jira/browse/JAXME-60
Project: JaxMe
Type: Sub-task
Components: JaxMe Core
Reporter: Jochen Wiedmann
--
This message is automatically generated
Nested groups with multiplicity > 1
---
Key: JAXME-61
URL: http://issues.apache.org/jira/browse/JAXME-61
Project: JaxMe
Type: Sub-task
Reporter: Jochen Wiedmann
--
This message is automatically generated by JIRA.
-
If you thin
[ http://issues.apache.org/jira/browse/JAXME-60?page=all ]
Jochen Wiedmann closed JAXME-60:
Fix Version: 0.4
Resolution: Fixed
Assign To: Jochen Wiedmann
Supported, as of 0.4.
> Nestes groups with multiplicity 1
> ---
[ http://issues.apache.org/jira/browse/JAXME-59?page=all ]
Jochen Wiedmann resolved JAXME-59:
--
Fix Version: 0.6
Resolution: Duplicate
Assign To: Jochen Wiedmann
Duplicate of JAXME-61
> CDMv2.01 schema cannot be compiled
> --
[ http://issues.apache.org/jira/browse/JAXME-59?page=all ]
Jochen Wiedmann closed JAXME-59:
> CDMv2.01 schema cannot be compiled
> --
>
> Key: JAXME-59
> URL: http://issues.apache.org/jira/browse/JAXME-5
[
http://issues.apache.org/jira/browse/JAXME-62?page=comments#action_12317128 ]
Jochen Wiedmann commented on JAXME-62:
--
Hmmm, the reason for the IllegalArgumentException is, that the check for
maxLength occurs within setFoo() and not within the SAX han
[ 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
> ---
[ 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
[ http://issues.apache.org/jira/browse/JAXME-58?page=all ]
Jochen Wiedmann updated JAXME-58:
-
Attachment: idMap3.patch
To keep the discussion open, a modified version of your patch. The IDREF
properties should now be objects indeed.
I am currently cons
[
http://issues.apache.org/jira/browse/JAXME-64?page=comments#action_12318387 ]
Jochen Wiedmann commented on JAXME-64:
--
Marcus, your contribution is extremely welcome. In fact, Nacho is currently
working on the "mavenization" of JaxMe itself.
As Nacho
[ http://issues.apache.org/jira/browse/JAXME-65?page=all ]
Jochen Wiedmann updated JAXME-65:
-
Attachment: JAXME-65.patch
The ChoiceHandlerSG did not treat a choice with minOccurs="0" as optional.
> mixed="true" attribute on complexTypes unsupported?
>
[ http://issues.apache.org/jira/browse/JAXME-65?page=all ]
Jochen Wiedmann closed JAXME-65:
Fix Version: 0.6
Resolution: Fixed
Assign To: Jochen Wiedmann
Patch applied to trunk and 0.5 branch.
> mixed="true" attribute on complexTypes un
[ http://issues.apache.org/jira/browse/JAXME-58?page=all ]
Jochen Wiedmann updated JAXME-58:
-
Attachment: JAXME-58.patch
The attached patch could be considered the final implementation. I've changed
the following things:
- The ID interface is no longer
[ http://issues.apache.org/jira/browse/JAXME-58?page=all ]
Jochen Wiedmann closed JAXME-58:
Fix Version: 0.6
Resolution: Fixed
Assign To: Jochen Wiedmann
After initial work on merging the JAXME-28 branch, I changed my mind and
decided to
[
http://issues.apache.org/jira/browse/JAXME-66?page=comments#action_12318754 ]
Jochen Wiedmann commented on JAXME-66:
--
xjc:dom is a really tough job, because most likely you have to modify almost
all parts of JaxMe.
Let's begin with the first step: T
[ http://issues.apache.org/jira/browse/JAXME-67?page=all ]
Jochen Wiedmann closed JAXME-67:
Fix Version: 0.6
Resolution: Fixed
Assign To: Jochen Wiedmann
Fixed in trunk and 0.5 branch. Thanks, in particular for resolving the problems
sou
[ http://issues.apache.org/jira/browse/JAXME-68?page=all ]
Jochen Wiedmann closed JAXME-68:
Fix Version: 0.6
Resolution: Fixed
Assign To: Jochen Wiedmann
Sorry, I have added the missing classes.
> JAXBSchemaSG does not compile
> ---
[
http://issues.apache.org/jira/browse/JAXME-64?page=comments#action_12318986 ]
Jochen Wiedmann commented on JAXME-64:
--
Marcus, sorry for having replied to the list and not by commenting this issue:
The plugin needs some extensions for being usable wit
[
http://issues.apache.org/jira/browse/JAXME-64?page=comments#action_12319343 ]
Jochen Wiedmann commented on JAXME-64:
--
I do not understand the difference. A generic plugin should be usable for
building JaxMe itself (more precisely: The JaxMe examples
[ http://issues.apache.org/jira/browse/JAXME-69?page=all ]
Jochen Wiedmann closed JAXME-69:
Fix Version: 0.6
Resolution: Fixed
Assign To: Jochen Wiedmann
Applied to the upcoming 0.6 branch.
> duplicate code
> --
>
>
[
http://issues.apache.org/jira/browse/JAXME-61?page=comments#action_12355730 ]
Jochen Wiedmann commented on JAXME-61:
--
Eric,
I am sorry to say, but you are right: This is the same problem. Again sorry:
You'll have to use another JAXB implementation o
[
http://issues.apache.org/jira/browse/JAXME-72?page=comments#action_12358070 ]
Jochen Wiedmann commented on JAXME-72:
--
I'd highly appreciate a Unit test, or at least an example, that demonstrates
what problem is fixed by your patch. To be honest, I ha
[ http://issues.apache.org/jira/browse/JAXME-73?page=all ]
Jochen Wiedmann closed JAXME-73:
Resolution: Duplicate
Eric, I am really sorry, but your "workaround" doesn't change the fact, that
you are in fact using nested groups with multiplicity > 1
[ http://issues.apache.org/jira/browse/JAXME-72?page=all ]
Jochen Wiedmann closed JAXME-72:
Fix Version: 0.6
Resolution: Fixed
Patch applied to the branches 0.4, 0.5 and MAVEN (future 0.6). Note, that I
changed one details: The method for gene
[
http://issues.apache.org/jira/browse/JAXME-74?page=comments#action_12358471 ]
Jochen Wiedmann commented on JAXME-74:
--
I am sorry, but the zip files data is completely usable. I have spent about 20
minutes, trying to get it compiled, but now it's too
[ http://issues.apache.org/jira/browse/JAXME-74?page=all ]
Jochen Wiedmann reassigned JAXME-74:
Assign To: Jochen Wiedmann
> JAXP Transform seems fails
> --
>
> Key: JAXME-74
> URL: http://issues.apache.org/j
[
http://issues.apache.org/jira/browse/JAXME-74?page=comments#action_12358505 ]
Jochen Wiedmann commented on JAXME-74:
--
The problem is as follows:
The TransformerHandler expects to see a complete sequence
startDocument() ... endDocument()
Obvious
[
http://issues.apache.org/jira/browse/JAXME-72?page=comments#action_12358777 ]
Jochen Wiedmann commented on JAXME-72:
--
The repository was converted to subversion since the last release. Try
http://svn.apache.org/repos/asf/webservices/jaxme
> Gene
[ http://issues.apache.org/jira/browse/JAXME-75?page=all ]
Jochen Wiedmann closed JAXME-75:
Resolution: Invalid
The error is in your application:
List children = sh.getLibraryReference();
children.ad
[ http://issues.apache.org/jira/browse/JAXME-79?page=all ]
Jochen Wiedmann closed JAXME-79:
Resolution: Fixed
Assign To: Jochen Wiedmann
Fixed in the 0.5 branch and in HEAD.
Unfortunately, you will nevertheless be unhappy: First of all, you ne
[ http://issues.apache.org/jira/browse/JAXME-64?page=all ]
Jochen Wiedmann closed JAXME-64:
Resolution: Fixed
Added to the maven branch below projects/mp.
> [PATCH] Maven plugin for JaxMe2
> ---
>
> Key: JAXME-
Mixed content with empty elemen tcauses NPE
---
Key: JAXME-80
URL: http://issues.apache.org/jira/browse/JAXME-80
Project: JaxMe
Type: Bug
Versions: 0.5
Reporter: Jochen Wiedmann
Priority: Minor
The following d
[ http://issues.apache.org/jira/browse/JAXME-81?page=all ]
Jochen Wiedmann closed JAXME-81.
Resolution: Fixed
Applied, thank you!
> build error "The database is already in use by another process"
> --
Element references are referencing the global elements type interface and not
the element itself
Key: JAXME-83
URL: http://issues.apache.org/jira/browse/JAXME-83
minOccurs="0" not recognized in choice, if the choice is within an extension
Key: JAXME-84
URL: http://issues.apache.org/jira/browse/JAXME-84
Project: JaxMe
Issue T
[ http://issues.apache.org/jira/browse/JAXME-84?page=all ]
Jochen Wiedmann resolved JAXME-84.
--
Resolution: Fixed
The problem turned out to be, in fact, in the XS layer.
If an extended element has empty content, then the resulting content is
actually t
[
http://issues.apache.org/jira/browse/JAXME-86?page=comments#action_12445410 ]
Jochen Wiedmann commented on JAXME-86:
--
No problem with the large XSD. The debug setting is maven's -X switch, btw.
First of all, I can reproduce the problem. D
[
http://issues.apache.org/jira/browse/JAXME-87?page=comments#action_12445411 ]
Jochen Wiedmann commented on JAXME-87:
--
Kenney, would it be possible to modify your patch in a more intrusive manner?
Drop support for Maven 1, change the direc
[
http://issues.apache.org/jira/browse/JAXME-86?page=comments#action_12445462 ]
Jochen Wiedmann commented on JAXME-86:
--
The problem is here;
IMO, the JAXB specification states that the "name" attribute must be a fully
qualified t
[ http://issues.apache.org/jira/browse/JAXME-77?page=all ]
Jochen Wiedmann resolved JAXME-77.
--
Fix Version/s: 0.6
Resolution: Fixed
Assignee: Jochen Wiedmann
Applied to 0.5 and 0.6 branch.
> Java parser chokes on import packagename.*
>
[ http://issues.apache.org/jira/browse/JAXME-87?page=all ]
Jochen Wiedmann resolved JAXME-87.
--
Resolution: Fixed
Applied, with modifications, to the MAVEN branch. Plan is to move the branch to
the trunk ASAP.
> Convert build to Maven 2
>
[
http://issues.apache.org/jira/browse/JAXME-89?page=comments#action_12455301 ]
Jochen Wiedmann commented on JAXME-89:
--
I haven't yet worked out why, but the AntLRTest fails after applying your patch:
The class name must not be null or empt
[ http://issues.apache.org/jira/browse/JAXME-89?page=all ]
Jochen Wiedmann resolved JAXME-89.
--
Fix Version/s: 0.6
Resolution: Fixed
Assignee: Jochen Wiedmann
Applied to 0.5 branch and trunk.
> Multiple "implements" clauses are not supp
[
https://issues.apache.org/jira/browse/JAXME-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-92.
--
Resolution: Won't Fix
This is obviously a matter of programming style and taste. The JavaJS frame
[
https://issues.apache.org/jira/browse/JAXME-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann reassigned JAXME-94:
Assignee: Jochen Wiedmann
> startElement method larger than 64KB when using a large amount of
[
https://issues.apache.org/jira/browse/JAXME-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524019
]
Jochen Wiedmann commented on JAXME-94:
--
Had some time yesterday to inspect it. My first impressions:
- This won't
[
https://issues.apache.org/jira/browse/JAXME-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann updated JAXME-95:
-
Assignee: Jochen Wiedmann
Remaining Estimate: 0h
Original Estimate: 0h
> JavaPar
[
https://issues.apache.org/jira/browse/JAXME-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-95.
--
Resolution: Fixed
Applied, thank you!
> JavaParser.parseObject() handles inner interfaces incor
[
https://issues.apache.org/jira/browse/JAXME-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-100.
---
Resolution: Invalid
Assignee: Jochen Wiedmann
Use on either element or attribute. See
[
https://issues.apache.org/jira/browse/JAXME-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-99.
--
Resolution: Invalid
Assignee: Jochen Wiedmann
Use xjc:serializable. See
http://java.su
[
https://issues.apache.org/jira/browse/JAXME-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697487#action_12697487
]
Jochen Wiedmann commented on JAXME-102:
---
Did you use the jaxb:property customization?
[
https://issues.apache.org/jira/browse/JAXME-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-102.
---
Resolution: Won't Fix
Using jaxb:property is the way to resolve such conflicts that the specif
[
https://issues.apache.org/jira/browse/JAXME-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved JAXME-104.
---
Resolution: Fixed
Fix Version/s: 0.6
Assignee: Jochen Wiedmann
Applied, thank
[
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
71 matches
Mail list logo
