---------- Forwarded message ---------- From: Behrang Saeedzadeh <[EMAIL PROTECTED]> Date: Fri, 17 Dec 2004 17:11:35 +0330 Subject: Re: OJB && struts To: [EMAIL PROTECTED]
> ie Hibernate ... the only guys who managed to get it right with ORM in > the last 4 years of sun and theserverside wafflers are going to be > running the show. Incidentally I remember before Fleury was kicked off > how there was always 30 people jumping on the Entity Beans are great > bandwagon ... yeah .. I remember that one pretty well. As long as I remember Sun has always said that EJBs in general and Entity Beans in particular are not suited for every kind of application. Long ago there was a JavaWorld article named "To EJB or not to EJB" that discussed this problem and was pretty insightful. I have never liked Entity Beans too but there was a thread at TheServerSide about CMP Entity Beans and someone asked if there's any successful non trivial project based on them and some guys announced that they have built large-scale enterprise applications using CMPs for things like banking and ... and their customers were all happy and their projects successful. So yes, Entity Beans are great if used in correct places. However they had their own cons: it were possible to design a general purpose persistence layer suitable for a wider range of applications and not as difficult to understand as CMPs and Hibernate was proving instance. So they started revising the whole EJB spec and Entity Beans in particular but the goals of EJB 3.0 Entity Beans and JDO was very similar so they merged them and it will benefit from both of the strong points of Hibernate and JDO (and CMP Entity Beans if any.) However I was not talking about CMP Entity Beans. I was saying that JDO 1.0 + Externsions and JDO 2.0 is at least as good as Hibernate. I and many others () prefer it over Hibernate, you and many others don't. > The dev/community process for it should be something like this .... > > a) Hibernate implement it b) Jboss integrate it c) Sun accept it I don't know what are you talking about. > So it isn't really a standard then any more than hibernate is it ? > Because everyone is going > to add their little tweaks to it ... You may be right but I don't care about JDO being a standard or not. I only say that it's at least as good as Hibernate. > Is the only thing you get as standard the persistence manager interface ??? Not only the interface: the specification which includes the interface too + a reference implementation + a compatibility test kit. As long as I know many other standards (like ANSI/ISO C++, and ...) are not as broad as standards defined in the JCP. > I already use XDoclet for hibernate mapping generation, I'm talking > about the fact that your > build process now consists of the following. > > 1 Write Java file > 2 Write XDoclet mappings > 3 Run XDoclet to generate mappings ( remember it doesn't work with Java 5 ) > 4 Compile classes > 5 Run ant task to bytecode enhance > 6 Let them redeploy within tomcat or whatever > 7 Test 1, 2, 3, 4, 6, 7 are not exclusive to JDO. And using Ant, 5 does not have any noticable negative side effect. > JDO didn't make it, didn't do it right, was late for the dance and is > due to be superseded ... .. what the hell point is there in > investing time and effort in something like that ? This is your personal view point. I don't think so. > The only reason to use JDO is that you want to use Hibernate but your > boss says that you have to use something with an "(If we don't get a > clue we will go bust) Sun Microsystems" sticker on it. No. In the next project my boss has gave me the freedom to choose the persistence layer along many other things and if everything goes well I'll absolutely be using JPOX. - Behrang -- Behrang Saeedzadeh http://www.jroller.com/page/behrangsa --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
