I have never heard any of the main developers talk about JBoss4 _not_ being J2EE compatible. It has always been my understanding that the AOP framework would form the underpinnings of JBoss4's EJB implementation and be available as a more-flexible, lighter weight API for people who aren't concerned with portability.

Scott, Bill, Marc - can one of you clarify?

thanks,
danch

Rahul Ganjoo wrote:
"but one of the goals of JBoss 4 is to make it so developers don't have
to deal with all the J2EE APIs"

from this and the discussion in general.. Jboss4 and J2EE compliance are
two entirely
different "roadmaps" (IMHU).. i mean its important for everyone here to
know what direction Jboss
is going to take.. is j2EE compliance important and is Jboss going for
it..or
is it keeping up the Jboss4 AOP vision and hence chucking compliance?





------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to