Ara Abrahamian wrote: > Should be a typo :o) I'll correct it.
Great! Currently I switched to EJB1.1, which works, but I need message beans later on. > PS: middleware-company.com! Cool ;-) yeah, I'm porting the TheServerSide.com portal to use XDoclet. I had some problems, but got the latest CVS, got some more problems, and it forced me to change into a structure that was superior to what I had intended to do in the first place :-) At first I wanted to have each entity be two classes: XBean, containing the business logic and abstract get/sets, and then XJDBC which subclasses XBean and implements ejbLoad/ejbStore for BMP. But that didn't quite work, so instead I made a superclass EntitySupport that XBean could extend, and in EntitySupport.ejbLoad/ejbStore I delegate to a DAO object that handles the JDBC. This is really cool because it means that I can very easily switch persistence mechanism by simply making a factory mechanism for the DAO handlers :-) So, for example, during dev I'd use a simple XML storage, or db4o, and then for production I'd switch to JDBC, but without having to change my code at all. Aaaanyway. Back to coding. /Rickard -- Rickard Öberg Chief Architect, TheServerSide.com The Middleware Company _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
