Comments on: Annotations vs. XML http://javidjamae.com/2006/11/19/annotations-vs-xml/ Javid Jamae's thoughts on software, startups, and other things. Sat, 25 May 2013 19:41:38 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Vlad http://javidjamae.com/2006/11/19/annotations-vs-xml/comment-page-1/#comment-326 Vlad Thu, 04 Mar 2010 00:56:40 +0000 http://javidjamae.com/?p=126#comment-326 >Mariusz said: >consider another thing, those are not POJO’s in it’s strict sense, >those are Entities! Only if you want your application be tied to a database. E.g., imagine your POJOs could be persisted in your app's database, and at some point your app got integrated with another system via web services, and could pull POJOs of the same type from that system. >Mariusz said:

>consider another thing, those are not POJO’s in it’s strict sense, >those are Entities!

Only if you want your application be tied to a database.

E.g., imagine your POJOs could be persisted in your app’s database, and at some point your app got integrated with another system via web services, and could pull POJOs of the same type from that system.

]]> By: Nuru http://javidjamae.com/2006/11/19/annotations-vs-xml/comment-page-1/#comment-313 Nuru Wed, 22 Apr 2009 19:19:51 +0000 http://javidjamae.com/?p=126#comment-313 >>I haven't heard of a way to specify two mutually exclusive sets of Hibernate annotations on my classes. Read about Hibernate annotations. Not JPA >>I haven’t heard of a way to specify two mutually exclusive sets of Hibernate annotations on my classes.

Read about Hibernate annotations. Not JPA

]]> By: Mariusz http://javidjamae.com/2006/11/19/annotations-vs-xml/comment-page-1/#comment-151 Mariusz Fri, 14 Mar 2008 13:31:31 +0000 http://javidjamae.com/?p=126#comment-151 John, consider another thing, those are not POJO's in it's strict sense, those are Entities! John,

consider another thing, those are not POJO’s in it’s strict sense, those are Entities!

]]> By: John http://javidjamae.com/2006/11/19/annotations-vs-xml/comment-page-1/#comment-27 John Mon, 15 Oct 2007 21:56:00 +0000 http://javidjamae.com/?p=126#comment-27 Working on a Hibernate/Spring project right now. Got spring cfg in XML and Hib in Annotations.<br/>Recently started becoming concerned with the fact that my Pojo's now know something about their persist store (tables/cols etc) and the imports now directly reference hibernate classes for the annotations - which is kinda ugly when in some environments I'm using them as pojo's and in our unit test env where we mock there is no Hibernate.<br/><br/><br/>This leads me towards an all XML approach but I don't find the proliferation of non-java artefacts very appealing either. Working on a Hibernate/Spring project right now. Got spring cfg in XML and Hib in Annotations.
Recently started becoming concerned with the fact that my Pojo’s now know something about their persist store (tables/cols etc) and the imports now directly reference hibernate classes for the annotations - which is kinda ugly when in some environments I’m using them as pojo’s and in our unit test env where we mock there is no Hibernate.

This leads me towards an all XML approach but I don’t find the proliferation of non-java artefacts very appealing either.

]]>