--- Dain Sundstrom <[EMAIL PROTECTED]> wrote: > On Sunday, March 23, 2003, at 07:30 PM, Dave Neuer > wrote: > > > --- Dain Sundstrom <[EMAIL PROTECTED]> wrote: > >> > >> The more tests we have the better we will be, but > I > >> doubt that sun will > >> let us check the TDK into CVS, so it will be > >> worthless to everyone but > >> the few JBoss employees that get access. > >> > >> -dain > > > > Is a condition of the TDK license that you can't > use > > the information about your source tree that it > reveals > > to improve the product? Does it specifically bar > you > > from writing JUnit test cases which test for a bug > > which just happens to be a bug regarding spec > > compliance? > > Got me. Where did you find the license to the J2EE > TDK license? > > -dain >
I didn't, I was asking you ;-). Seriously, I can imagine Sun has got some onerous conditions in there compatabitliy test kit license. However, if JBoss can't pass the tests, it's because of "bugs" (i.e., missing features) in the code, and I can't imagine that even if the license for the test kit somehow prohibits you from sharing the kit itself or the results, it would also restrict you from fixing "bugs" in your source code, whatever those bugs might be. I mean, Sun's J2EE specs are public. It'd be tough for their lawyers to prove you fixed a bug or added a feature just because you ran the tests. But, to an extent it would be beside the point. I'm working now on a project to replace a Lotus Notes/Domino application and the management of the company brought me on because *they* chose JBoss to replace it, and I've taken the advanced training. They didn't seem to concerned about spec compliance. They care about performance, flexibility, and no $3000/CPU licensing. Spec compliance is valuable because it provides (in theory, at least) predictable behavior when you don't have the source of the application. When you've got the source, you don't need predictable behavior; everything is completely transparent. You can turn on source-level debugging and step through the code! Don't like how it does feature X? Fix it! Certified spec compliance for JBoss would be nice for one little extra marketing buzzword. But at this point, JBoss probably has enough momentum that spec compliance could be at most icing on the cake. You know for sure that if someone out there needs some in-spec feature that JBoss doesn't have bad enough, they'll send a patch to add it. Dave __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
