Comments on: Annotations vs. Interoperability? http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/ A blog about programming in .NET and Java Thu, 20 Nov 2008 18:04:09 +0000 http://wordpress.org/?v=2.0.2 by: Alef Arendsen http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-329 Thu, 19 Jan 2006 00:05:49 +0000 http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-329 I've posted a reply on my blog (http://blog.arendsen.net) since it's rather lengthy. regards, Alef I’ve posted a reply on my blog (http://blog.arendsen.net) since it’s rather lengthy.

regards,
Alef

]]> by: Steve Loughran http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-328 Wed, 18 Jan 2006 22:45:25 +0000 http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-328 I agree that you can add excellent metadata to stuff, but fear that java-land is about to over-embrace annotations now that they are possible. You can see that with some of the xdoclet uses, where your late-binding resource mapping stuff ends up being early-bound into the java source. In hibernate, the example I'd cite is where there is an @ tag to declare the batch fetch size when retrieving objects. That is a per-installation tuning feature; a deployment where db and app are on the same host is very different from where the db is 4000 miles away, so you cannot declare it forever in the code. the annotations can be a hint, to set the defaults, but they must be overrideable. -steve I agree that you can add excellent metadata to stuff, but fear that java-land is about to over-embrace annotations now that they are possible. You can see that with some of the xdoclet uses, where your late-binding resource mapping stuff ends up being early-bound into the java source.

In hibernate, the example I’d cite is where there is an @ tag to declare the batch fetch size when retrieving objects. That is a per-installation tuning feature; a deployment where db and app are on the same host is very different from where the db is 4000 miles away, so you cannot declare it forever in the code. the annotations can be a hint, to set the defaults, but they must be overrideable.

-steve

]]> by: Aviad Ben Dov http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-327 Wed, 18 Jan 2006 21:48:30 +0000 http://blog.springsource.com/arjen/archives/2006/01/18/annotations-vs-interoperability/#comment-327 So what do you think of frameworks like <a href="http://jakarta.apache.org/tapestry" rel="nofollow">Tapestry</a> or <a href="http://javachaos.crazyredpanda.com/?p=37" rel="nofollow">X2J</a>? So what do you think of frameworks like Tapestry or X2J?

]]>