On Jan 7, 2007, at 11:33 PM, Matt Hogstrom wrote:
I was thinking about M2 this weekend and was considering many of
the challenges we face in putting out certified releases. Up till
now the number of permutations has been pretty limited and that has
been Jetty and Tomcat. With Java EE 5.0 life is no longer that
simple. Here are the choices I know of today:
Web Container (Tomcat / Jetty)
WebServices (Axis 2 / CXF)
EJB 3.0 Persistence (OpenJPA / Cayenne)
I think this makes 6 different assemblies and of course 6 separate
certification efforts. Perhaps we can do this and perhaps we
can't. Based on where projects are at and their desire to
participate in helping to integrate (and do TCK testing :).
ummm 2 * 2 * 2 == 8
I could be very wrong but I thought that the cmp 2.1 support in
openejb3 was relying on openjpa-specific features. If so I wonder if
it will be tricky to run the tck on other jpa implementations.
rather than saying we'll only ship when we have all 6 it seems more
appropriate to me to say that we'll ship the assemblies that people
are willing to work on which includes TCK testing. Any other ideas
on how to handle this? Anyone interested in a specific
configuration and want to step up to TCK testing?
I think maybe we should concentrate on packaging things as plugins,
although this doesn't really affect what we run through the tck.
thanks
david jencks
Matt Hogstrom
[EMAIL PROTECTED]
