[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] JEE 5 Working Group Meeting - Agenda
- From: Naci Dai <naci.dai@xxxxxxxxxxxxx>
- Date: Thu, 04 Jan 2007 12:15:39 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 18.104.22.168 (Windows/20061207)
Thank you for the detailed explanations. I have looked at the bugs to
get a feel for JBoss reqs. There are lots of good things in there.
I think it would be very useful to gather these thoughts under a few
common topics. Maybe Robert, can merge some of those bugs under Chuck's
EJB3 bugs, and model extensibility discussions that is being lead by SAP.
It will help us focus on critical items.
- Review M3 & M4 status for EJB 3.0 Facets and Projects
- Review JEE 5 Model Extension Point Design (Hristo Sabev)
I promised before the holidays to give some info about how we had and are
adding EJB3 support to JBossIDE and at the same time tries to be
with WTP projects; so here better late than never:
What we have done is basically to create a EJB3 facet that is the best
can hook into the lifecycle/wizardry of WTP components until true JEE
support is added to WTP. Thus the ejb3 facet today is basically just a
for the library dependencies and used as a "tag" to identify the ejb3
and it will probably be phased out when WTP gets JEE 5 support.
I write "probably" because another issue with WTP is it's restrictive
which users are not too happy about being restricted too - thus we
might still need
the EJB3 facet to support less rigid project structures (because WTP
is bound to modules
for which there can only be one even though that is not always what
but that is another bigger discussion that is a topic for another
discussion (normally done at eclipsecon ;)
Going back to the EJB3 facet'ing and our need to "hook" in and
extend/bend WTP to allow
us to provide EJB3 facilities our main issues have been mix of small
but some problems based on the entire nature / structure of the API.
the small things had to do with bugs in background upstream classes that
(seemingly) assumed only a very few people would actually be using or
classes and then the "impedance mismatch" between Server/Runtimes and
JBoss (and other servers) configurability.
To get a view/feel of the issues we bumped into the best way is to
look at the bugs Robert Stryker reported/commented on in context of WTP:
I can unfortunately not always attend the JEE 5 conf call, but Robert
will try and attend these.
Happy New Year!
Max Rydahl Andersen
JBoss a division of Red Hat
wtp-dev mailing list
itu teknokent ari-1 25
Maslak, Istanbul 34469
+90 (533) 580 2393 (cell)
+90 (212) 328 0825 (phone)
+90 (212) 328 0521 (fax)