hi,
I just upgraded to castor-0.9.5.4 and my existing code with respect to
loading mapping files fails.
MY code looks as follows:
Mapping mapping = new Mapping();
String mapFile =
Thread.currentThread().getContextClassLoader().getResource("mapping.xml").getFile();
mapping.loadMapping(mapFile);
Hi Paul,
With the type-approach Castor will generate classes for all complexTypes
and any top-level elements. With the element-approach castor will
generate a class for all elements and all complexTypes.
You should definately see a difference in the classes generated for both
types. Did you de
I tried both element and type and I get the same 12 classes generated.
Just tried it again to make sure I didn't miss anything, but there
appears to be no difference. I did check to insure it was picking up my
builder properties file (just in case) by also asking it to extend from
a super class.
Bruce,
Thanks very much. This does look very promising. I was wondering about
possibly having all elements. Forgive me for my newness to schema
creation, but I do have one last question related to the solution. In
the fixed up schema it has:
A
Paul,
Try generating your source code using the "type" approach. You can
specify this in the "castorbuilder.properties" or in a binding-file if
you're using one.
http://castor.exolab.org/sourcegen.html#Class-Creation/Mapping
--Keith
Paul Grillo wrote:
I would really appreciate some help on this,
On Thu, 27 Jan 2005 11:41:27 -0500, Paul Grillo
<[EMAIL PROTECTED]> wrote:
>
> I would really appreciate some help on this, i'm sort of up against it. any
> help would be "greatly" appreciated...
>
> I have a fairly complex schema that i'm generating java for. I have
> flexibility to change
I would really
appreciate some help on this, i'm sort of up against it. any help would be
"greatly" appreciated...
I have a fairly
complex schema that i'm generating java for. I have flexibility to change
the schema, write binding files, or whatever. I guess i'm having a problem
underst
