Tek1:

I am trying to use XDoclet and it has a lot of broken functionality.
Also, the castormapping part of it is not well supported.

At this point, I would recommend againt using xdoclet for
castor mappings.

Thanks,
        Neil.

--
Neil Aggarwal
JAMM Consulting, Inc.    (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development    Websites, Ecommerce, Java, databases


> -----Original Message-----
> From: tek1 [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 05, 2003 2:12 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [castor-dev] Code for auto-generating CUSTOM castor mapping
> files
>
>
> daniel,
>
> do you mean that you want to automatically generate the mapping.xml file
> based on your .java classes?
>
> have you checked out xdoclet's exolab/castor module?
>
>
>
> At 12:28 03/02/04 -0500, you wrote:
>
> >Thanks Bruce,
> >    I guess I need to ask some more advice (again you will probably tell
> > me that there is no toolset that can help me paddle up this unpleasant
> > creek, but I have to ask as it is always better to use a well crafted
> > wheel than to build one from scratch).
> >
> >      -Do you know a good general forum on Java serialization and data
> > versioning?  When I say this I mean a forum that deals with
> these topics
> > in the context of: java built in behavior, 3rd party tools
> (Castor etc),
> > and possibly informal code / algorithms.
> >
> >      -If there is no source for generating custom mapping files from
> > java classes, then I am at a fork in the road either I:
> >
> >            -proceed by writing my own mapping code (pros: it should be
> > able to kill my serialization and data versioning problems outright;
> > cons: given my codebase the solution might be buggy or problematic (esp
> > for classes lacking setter methods), also it will involve considerable
> > development work.
> >
> >          -look into leveraging the current standard java.io code (using
> > the underlying logic
> >to serialize my object but imposing my own XML formating of the data
> >(rather than the standard byte serialization)).  (pros: this should be
> >easier and more reliable, cons: data versioning would still be an
> >outstanding problem and I'd need to write a standalone to migrate data).
> >
> >-----Original Message-----
> >From: Bruce Snyder [<mailto:[EMAIL PROTECTED]>mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, February 04, 2003 8:55 AM
> >To: [EMAIL PROTECTED]
> >Subject: Re: [castor-dev] Code for auto-generating CUSTOM castor mapping
> >files
> >
> >This one time, at band camp, Daniel Shriver said:
> >
> >DS>   I was wondering if there is code available for
> auto-generating custom
> >DS>Castor mappings.  The code sometimes conforms to "Bean"
> standards ...and
> >DS>sometimes doesn't (mismatched or lopsided getters & setters,
> poorly named
> >DS>getters or setters...) and my understanding is that would
> confuse Castor....
> >
> >Daniel,
> >
> >Not only is this a complex task, but AFAIK there is nothing available
> >that will do this. However, among other tools, there is a GUI for
> >creating Castor mapping descriptors
> >(<http://o2xmapper.sourceforge.net/jdomapper>http://o2xmapper.sou
rceforge.net/jdomapper).
>But my favorite is
>XDoclet (<http://xdoclet.sf.net/>http://xdoclet.sf.net/) so that the
>mapping descriptors
>are generated dynamically each time you compile ;-) - very nice!

-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to