I have been using Castor XML for a rather large business object model for the purposes of marshalling into and out of SOAP message for client to server communication.   Fairly classic, I imagine.  It has worked very very well for us.  Thank you very much!!

 

The approach we took, thus far, was to create an appropriate mapping file with our domain model to sort of get Castor to do what we wanted. Nothing fancier that that, no direct calls etc.  There was some handcrafting done within the objects to handle Maps, etc, but not much.

 

Okay, all this time I’m seeing references to JDO.  Like this tag is used in JDO, and ignored by Castor XML, etc.  Well, the JDO stuff has been (until now) ignored by me.

 

Now, I want to take this business object model and add persistence to a relational database.

 

My general, sort of high level questions is are:

 

What, if any, relationship is there  between the XML Mapping files that I have in place today, and what I might need for persistence?  Is there any re-use  possible? I’m not talking about just getting them to cooperate, but looking to see if I can reuse the mapping.

Or am I now going faced with creating a whole set of mapping files for JDO.

 

I’m not averse to doing this, I just don’t want to miss anything that might make my life easier.

 

 

Also, pointers to any other links that might help me to begin to tackle this problem will be helpful.  I have handcrafted an earlier version of this Object Model for persistence, and it works okay.  I would, however, like to begin using some technologies that I can grow with.  I have been looking at other solutions (like Hibernaet, commercial Cocobase, etc) as well as Castor JDO.  I’ve had such good luck with Castor XML, it makes sense for me to look at Castor JDO.

 

Any help with these questions and a suggestion of a best way to start will be helpful.  I plan to start with a small subset of the model with some one to many odd relationships to prove the concept.

 

Thanks for your help.

 

 

 

Reply via email to