> I envision the mapping file to look like:
>
> <field name="arg" set-method="%1" get-method="getArg"/>
Very interesting....
Does your ongoing work also include support for factory methods in
addition to constructors? (Not trying to press too hard, just trying to
figure out whether this work would be usable; it sounds like it is).
FWIW -- What I've been playing with this morning was support for a
factory method without arguments (figuring that argument handling seemed
much harder...).
a) added "factory-method" to the mapping.xsd as an optional string
attribute of a class.
b) I had started mucking UnmarshallHandler startElement() method adding
some clauses near calls to newInstance that would attempt to invoke the
provided factory-method if it was specified.
If your work includes this type of functionality, I'll abandon my work
and wait. If you would be interested in my work as a contribution (when
its finished, which won't be for a little while), I'll continue.
> I'll probably release it in two phases. The first will be attribute
> based constructor arguments ( or Factory method arguments) and the
> second will be element based arguments. Since attributes are passed in
> with the startElement it will be the easiest and therefore come first.
I had figured the same from my preliminary looking into the code. That
would certainly be sufficient for my case.
PC
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
- [castor-dev] [XML] Mapping and static factory methods Paul Christmann
- Re: [castor-dev] [XML] Mapping and static factory met... Rhett Sutphin
- Re: [castor-dev] [XML] Mapping and static factory met... Keith Visco
- Paul Christmann
