Hi,
Instead of blanking out the value, remove it. (I wish that an empty, blank, value
would be signalled as missing but it doesn't. You have to remove the tag. Also, if you
remove the tag but there's a default value in your XSD... hasXXX() still returns false
whereas it should return true :-(
Hi,
I notice that this question is still not resolved, despite Keith's answer. So I looked
at it again and came to wonder: Is the below correct?
From: Keith Visco [mailto:[EMAIL PROTECTED]
Sent: vrijdag 5 maart 2004 19:16
> Castor supports type-safe enum if they have a valueOf method as such:
Hi,
Look at the source-generator in Castor. It generaters Java objects for the types
defined in the XSD, with marshalling support built-in.
regards,
--Tim
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and
is thus for use only by the intended recipient. If
Hi,
When I specify a type of 'xsd:date' in my xml schema, the generated classes have a
Castor specific date type. All my code uses java.sql.Date. This gives a lot of
ugly-looking code. Is it possible to coerce the SourceGenerator to generate
java.sql.Date instead? And if so, how?
I currently
;
to:
return (fieldName ? java.lang.Boolean.TRUE : java.lang.Boolean.FALSE);
This way were still prevent the creation new Boolean instances
unecessarily and it should be backward compatible with all JDK versions.
Thanks,
--Keith
"Leeuw van der, Tim" wrote:
>
> Hi,
>
> I
Hi,
In what way is the jar-file broken? I just generated new classes with it, but didn't
yet try marshalling / unmarshalling XML messages with it.
--Tim
-Original Message-
From: Marco Herrn [mailto:[EMAIL PROTECTED]
Sent: dinsdag 24 februari 2004 9:29
To: castor-dev
Subject: Re: [casto
Hi,
In my XML Schema I have an integer field named messageVersion, with a default-value.
When I generate java code from this schema, I the default value is properly set for
this field. However, the corresponding boolean _hasMessageVersion isn't set, meaning
it's always 'false' unless explicitl
Hi,
Any reason why 'type' mode is not the default for the source generator?
Backwards compatibility issues? If so, what exactly?
'type' mode seems to solve lots of people's problems (including mine) and if
it's the default, such problems wouldn't even surface.
Does using 'type' mode any other pro
ember 2003 14:01
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] castorbuilder.properties
> Von: Leeuw van der, Tim [mailto:[EMAIL PROTECTED]
> I put castor.builder properties somewhere in a directory in
> my classpath, before the castor-library itself. I don't try
> to modify
I put castor.builder properties somewhere in a directory in my classpath,
before the castor-library itself. I don't try to modify the original /
default.
Does that help?
With regards,
--Tim
-Original Message-
From: Marco Herrn [mailto:[EMAIL PROTECTED]
Sent: maandag 1 september 2003 12:
, which is what you describe in your email below.
-Original Message-----From: Leeuw van der,
Tim [mailto:[EMAIL PROTECTED] Sent: Tuesday, August
19, 2003 8:04 AMTo: 'Horan, Richard E'Cc:
CastorDevList (E-mail)Subject: RE: [castor-dev] java 1.4 and
hank you again.
Rick
Horan
-----Original Message-From: Leeuw van der,
Tim [mailto:[EMAIL PROTECTED] Sent: Tuesday, August
19, 2003 7:40 AMTo: [EMAIL PROTECTED]Subject: Re:
[castor-dev] java 1.4 and castor XML
Hi,
I'm not experiencing any problems. There's
Title: Message
Hi,
I'm
not experiencing any problems. There's one thing that didn't work for me, that
is perhaps attributable to me using jdk1.4, but I forgot what it was
exactly...
It had
to do with me trying to marshall not to output-stream, but to dom-document or
something like that...
dag 30 juli 2003 11:11
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] SourceGenerator questions
As regards point 2), use the following setting in castorbuilder.properties.
org.exolab.castor.builder.javaclassmapping=type
Cheers.
-Original Message-----
From: Leeuw van der, Tim [mailto:[EMAIL
Thanks! :-)
--Tim
-Original Message-
From: Keith Visco [mailto:[EMAIL PROTECTED]
Sent: woensdag 30 juli 2003 12:51
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] XMLInstance2Schema problem
Hi Tim,
I just checked in a patch for this.
--Keith
"Leeuw van der, Tim" wrote
castorbuilder.properties.
org.exolab.castor.builder.javaclassmapping=type
Cheers.
-Original Message-
From: Leeuw van der, Tim [mailto:[EMAIL PROTECTED]
Sent: 30 July 2003 10:05
To: [EMAIL PROTECTED]
I have a couple of questions regarding the source-generator, which doesn't
generate the
The tool that generates an XSD from an XML instance is nice, but I found 1
problem with it: When there are tags in my XML that have only attributes,
but no content, they are defined in the XSD without any of their attributes!
Example:
I have a couple of questions regarding the source-generator, which doesn't
generate the code I like but looks like it should be able to do so quite
easily...
In my XSD I have defined some simpleTypes, and some complexTypes.
My source is, for sake of argument, generated into a package my.foo
1) Th
18 matches
Mail list logo
