I think it would be good for wicket to have a somewhat complex schema and database for which new ideas and examples can be tried against... kind of like the one Hibernate has. I'm just throwing this out as an idea so feel free to suggest something better.
1) I have come up with an example genealogy schema that has some complexity to it, if others think it might work for that purpose. 2) I'd like to suggest using HSQLDB since that is very easy to check out and run for use by examples and the actual database can be easily committed to CVS because it stores the data as SQL statements. 3) The database definition files could go into wicket-contrib-data and the Java classes for Hibernate and Cayenne could go into the wicket-contrib-data-hibernate and wicket-contrib-data-cayenne projects, respectively. Does this make sense to do? Any objections to putting it there? I'm going to use it for testing and demonstrating RAD components so if people think it would *not* be useful elsewhere then it could just go into a new RAD project I am planning to create with the actual RAD components. Jon -- Jon Carlson Reply to: [EMAIL PROTECTED] ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
