Hello Bruce,
very good work! I think where the masters overlook everything, it's hard for them to see the difficulties for newbie's as I am. Each of us comes from differend direction to Castor and read that part he is most interessted in. Then also reads all those other stuff and realises that there can be great stuff done with Castor. For example I come to this through a project where we wear using Tibco (MOM product (http://www.tibco.com)) where I was writing a custom adapter, that reads messages from the tibco bus (read broadcast TCP/IP layer) and send them to the XML-SOAP interface of the billing application Cordaptix (from SPL Workgroup, but stay away of that (my opinion)). In this interface I choice to use log4j as my logging package. This because I hat red (previous project) that log4j could be extended by your own appender (oke have to write a Tibco appender I thought). Then at a searten moment I hat to write this appeander, but before starting with it I did a google through the web and come to Raccoon, which hat already a implementation of the log4j appender for Tibco, where I was looking for! Then hat a look through Raccoon's other technoligies one of the new ones was Castor (I hat seen the site before), but now I hat some time to read the presentation and some web pages. Then I realised that Castor would save me lot of time to generate value beans for applications. In my current project I started using it for that job the first time. We are using a Oracla database and as many times they where using JDBC queries to do the information storige and retrievals. Then I introduced SQLJ already some improvement. But when investigating the XSD -> vlaue bean stuff, I also red the JDO stuff. I new it would be a big improvment to use that over SQLJ at least not writing any SQL stuff any more (at least for all the basis JDBC insert/update/delete cases). I'm allways strugeling with the project managers / delivery managers why we still use those blody RDBMS systems and not a real sollution for OO persistence... We do not even have tools to solve the OO - Relational Mapping problems. Most of the projects do not even realize that they have that problem (Oke the struggel with it, but don't know that it is just the OO - Relations problem). So starting with SQLJ was done to be sure everything will work. I create a DAO layor which is used by the Business Logica layer (which is used by the Struts web application layer). This DOA layer gives me now the possibility to handle the persistence through JDBC, SQLJ and expirimenting now with JDO. We also have a TMP version, so we don't need a DB behind it. This is handy if the tables and other stuff (trigger, sequences, etc, etc) is not ready. Then the Business Logica layer can already be created and like wise the web layer. As you see I didn't come in from the XML direction. The site contains a lot of information, but the differned part present them to the outside as one big sollution. When reading through the stuff it's sometimes hard to find your way through, because the XML and XML Schema stuff is good documented, then the mapping from to other XML instance is already a little bit less (at least it was for me, but was also not readly my first consearn). Then going on to JDO everything JDO can do for you is well documented, but then how to do it is a very hard job (at least it was for me). After a lot of time looking around where to find this JDO mapping explained I came to the XML mapping stuff. Very good this intergration, but point to it. Also explain better what the XML instance releted mapping stuff is and what the JDO (SQL) releted stuff is and the other thing. In the mapping part http://castor.exolab.org/xml-mapping.html the DTD are written, but not all the things are explained. As newbie I have the hole time the idea that the site is a great and quick reference for guru's how rember something and have in a few words enough info again about what they didn't remember any more. But for newbie's it's very hard to get through and get thing up and running. Greetings, Tjeerd -----Original Message----- From: Bruce Snyder [mailto:[EMAIL PROTECTED]] Sent: vrijdag 12 april 2002 5:05 To: [EMAIL PROTECTED] Subject: Re: [castor-dev] newbie question about Persistent interface This one time, at band camp, Verhagen, Tjeerd said: VT>He Guru Bruce, VT> VT> VT>The PDF 'castor xml source code generator User document' improvements: VT>----------------------------------------------------------------------- VT>general VT>- Remove all the 'extra' newlines from the code / propertie examples. VT>- Add a chapter how to use the source generator with Ant and a property VT> file! Where Ant is in fact the standard building tool. VT> VT> VT>paragraph 2.1 Usage VT>- Handy that the extra packages needed in your classpath are not mentioned VT> at least you can search again to find out how it is working. VT> Include the package names and the url's where to find them! VT> VT> VT>paragraph 2.2 Source Generator Options VT>- How to use the properties file? This stupid newbie didn't get it to work. VT> In the examples the name is also differned (I just saw, see also below)! VT> Nice that command line option to tell castor, where the property file VT> can be found. VT> Handy that the following command line options can't be included in the VT> property file (or at least it's not explained): VT> - lineseperator VT> - types VT> - f VT> - nodesc VT> - nomarshall VT> - testable VT> VT> VT>paragraph 2.2.3.3 Setting up a super class VT>- Make a reference / example of JDO implementing this: VT> VT>------------------------------------------------------------------------- --- VT>---- VT> package org.organisation.project; VT> VT> VT> import org.exolab.castor.jdo.TimeStampable; VT> VT> VT> public abstract class JDOBaseClass implements TimeStampable { VT> private long timestamp = TimeStampable.NO_TIMESTAMP; VT> VT> VT> public long jdoGetTimeStamp() { VT> return timestamp; VT> } VT> public void jdoSetTimeStamp(long timestamp) { VT> this.timestamp = timestamp; VT> } VT> VT> } VT> VT>------------------------------------------------------------------------- --- VT>---- VT>- And reference it also to long transations. Maybe even add a 'Tip' that VT>this VT> technic can be used for web applications! VT> VT> VT> VT> VT>castor v0.9.3.9 VT>--------------- VT>- In the castor v0.9.3.9 distribution, the presentions HTML pages are not VT>included VT> only the images (directory '\doc\ora-mar-2k'). VT> VT>- examples.zip VT> - Here the property file 'castor.properties' for the sourcegenerator is VT>called VT> differend then in the User document 'castorbuilder.properties' VT>(paragraph VT> 2.2 && 2.2.3). VT> VT> VT>The newbie again Tjeerd, These are all great suggestions. I generally work more on the Castor JDO side than I do on the Castor XML side. Some of the things that you've eluded to in your messages reference the areas where Castor JDO and Castor XML overlap. Hopefully Arnaud and/or Keith will see your comments regarding Castor XML. I will do my best to use your suggestions for the Castor JDO side. Thanks again. Bruce -- perl -e 'print unpack("u44", "\?0G)U8V4\@4VYY9&5R\"F)R=6-E0&)S;GED97(N;W)G\"\@\`\`");' ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
