<html><body>
<p><tt>gavin.king@gmail.com wrote on 01/08/2009 08:46:13 PM:<br>
> On Fri, Jan 9, 2009 at 6:46 AM, Jim Knutson <knutson@us.ibm.com> wrote:<br>
> > but I think that's beside the point.<br>
> > The point is that there's a platform pattern. To integrate with the<br>
> > platform, I think you need to conform to the platform pattern. If<br>
> > you don't like the platform pattern, then the entire pattern ought<br>
> > to be consistently changed, not just one portion of it.<br>
> <br>
> Jim, this doesn't seem right to me.<br>
> <br>
> "Platform patterns" begin somewhere. A pattern is first introduced in<br>
> one spec, and people notice that the pattern is useful and has a wider<br>
> range of usefulness, and then they start to reuse the pattern in other<br>
> places in the platform.<br>
> <br>
> Take annotations, for example.<br>
> <br>
> Annotations were first trialed in the EJB spec and in the WS stuff in<br>
> Java EE 5. They were not supported in the servlet spec, the JSF spec<br>
> or anywhere else!<br>
> <br>
> Someone could have reasonably raised the objection during Java EE 5<br>
> that the use of annotations in EJB3 was inconsistent with the<br>
> "platform pattern" for specifying metadata.<br>
</tt><br>
<tt>It was raised as an objection and the pushback that was recieved was that</tt><br>
<tt>there was no time left to address it in the other specs. So, yes, there</tt><br>
<tt>was a conscious effort for platform consistency. It was understood that</tt><br>
<tt>the other technologies would follow suit during EE 6 and they have. In</tt><br>
<tt>other words, it was not a trial. Trial "standards" are never a good</tt><br>
<tt>idea. That's why open source plays an important role in understanding</tt><br>
<tt>what the industry wants prior to nailing things down in a standard.</tt><br>
<br>
<tt>I don't think the same could be said here. It's not a conscious effort</tt><br>
<tt>that the platform as a whole is going to move to this XML style and just </tt><br>
<tt>doesn't have the time. At least not yet it isn't.</tt><br>
<tt><br>
Thanks,<br>
Jim Knutson<br>
WebSphere J2EE Architect</tt><br>
<br>
</body></html>