I don't remember exactly, but the comment I added to the code gives us a clue:
//-- mapping loader now supports a basic EnumFieldHandler
//-- for xml we simply need to make sure the toString()
//-- method is called during getValue()
//FieldHandler handler = xmlDesc.getHandler();
//handler = new
What version of Castor are you using ? With 1.0.4, you
shouldnot get any of these at all ..
Werner
From: Carey, Tom [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 24. Oktober 2006 19:24To:
'user@castor.codehaus.org'Subject: [castor-user] Xml: Source Code
Generator - eliminating
Yes, please. Just to make sure, are you by any chance using the j2
(alias arraylist) field info factory during generation ? If so, I
think I knw where the problem is
Werner
-Original Message-
From: Romero, Carlo [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 24. Oktober 2006 19:43
Thanks, Keith. Looks like I have been reading that commetn again and
again, but failed to notice that this was moved to MappingLoader ...
:-(.
Werner
-Original Message-
From: Keith Visco [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 25. Oktober 2006 08:08
To: Werner Guttmann
Cc:
Yes, I have the j2 option turned on, but since you already fixed this,
will this be of any help to you?
-Original Message-
From: Werner Guttmann [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 5:40 AM
To: user@castor.codehaus.org
Subject: RE: [castor-user] Compilation Error
Not any more .. ;-).
Werner
-Original Message-
From: Romero, Carlo [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 25. Oktober 2006 14:37
To: user@castor.codehaus.org; Werner Guttmann
Subject: RE: [castor-user] Compilation Error in Castor 1.0.4
Generated Code
Yes, I have the j2
The unused imports showed up with 1.0.1. With 1.0.4,
Iwas getting a NPE with the schema I was using so no classes were
generated. I'll be putting in a Jira bug for the NPE this
morning.
Tom
From: Werner Guttmann
[mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 5:38
AMTo:
Jira bug created: CASTOR-1659
-Original Message-
From: Ralf Joachim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 24, 2006 1:25 PM
To: user@castor.codehaus.org
Subject: Re: [castor-user] XML Source Code Generator - v1.0.4 throws a NPE
Hi Tom,
can you please create a bug report at
Hi,
Thanks for the suggestion, but it didn't seem to help. I tried that and
updated it to look closer to what you had in your validation example, as
shown below.
Mapping File --
?xml version=1.0 encoding=UTF-8?
mapping xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Gregg-
That implies to me that the container=false logic isn't handling
namespaces correctly. Since it's been an undocumented feature for
several years now, I would hazard a guess that the code may not be as
well vetted as the rest of Castor. I would suggest raising an issue
in Jira and
Title: Castor and xsd:decimal
We have an element in an xml file coming in as 0.. The element is an xsd:decimal. When the document is unmarshaled and then marshaled again, the value changes from 0. to 0E-12. Is there a way around this without changing the type of the
Not sure. I guess I will have to look at this in more detail. As always,
can you please create a new Jira issue and attach *all* relevant files,
e.g. input document, mapping file (if required), Castor properties (if
you are using a custom one), etc.
Thanks in advance
Werner
Romero, Carlo wrote:
Unless I am missing
something it appears as though there might bea problem with the map-to
xml="" directive. It appears to work fine if the element is one or
2 levels deep. However it doesnt work if your mapping to an element 4
levels deep (not sure about 3) At least this has been my
13 matches
Mail list logo
