RE: [wtp-dev] Java EE 5 models design overview

["Raev, Kaloyan" <kaloyan.raev@xxxxxxx>]

Hi Jesper, 

We have taken a look at the J2EE 1.4 models implementation. It did make
impression that there are lots of hand made tweaks there. 

We decided to make the initial Java EE 5 models generated from the XML
schemas. There is also a lot of hand made work to be done to integrate
Java Annotations in these models. 

Can you outline in more details the tweaks that were done to the J2EE
1.4 models, so we have them in mind for the Java EE 5 ones? Do you think
better approach is to extend the existing J2EE 1.4 models with Java EE 5
specification instead of implementing separate Java EE 5 models?

Greetings
Kaloyan

-----Original Message-----
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jesper Steen Moller
Sent: Tuesday, November 14, 2006 9:52 PM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Java EE 5 models design overview

Actually, the current J2EE models rely on hand-coded XML translation 
between the EMF and DOM model, using the nifty Translator framework. 
Making that work with an EMF model is done by hand, and not for the 
faint of heart.
However, it gives rewards with round-trip editing inside SSE and with 
the possibility of versioning the XML, e.g. for web.xml 2.2, 2.4.

We're using this framework in the Mule IDE - it is very powerful, but 
has its quirks.

-Jesper
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev