At 02:22 PM 06/02/2000 +0200, you wrote: >Hey > > > I'll need a specific assignment for them, like adding BMP support, or > > writing a bean developer's guide or jBoss developer's guide, or mapping out > > what still needs to be done to be fully J2EE compliant and/or compatible > > with other containers, or some other project. It must be something that two > > people can accomplish in nine weeks of part-time work, something > > well-defined that I can grade, something that beginning Java programmers > > can accomplish with a bit of effort and (hopefully) with the support of > > this group. > >One of these sounds good, yes :-) What would benefit jBoss most? Based on what I've seen of jBoss and the mailing lists, I'm leaning toward this assignment: (1) A jBoss/EJB 1.1 compliance map and (2) Adding BMP support to jBoss. For the jBoss/EJB 1.1 compliance map, I think it would be beneficial to have a Web page at jboss.org that lists all of the requirements from the EJB 1.1 specification <http://java.sun.com/products/ejb/docs.html> (chapters 3 through 20) and an annotated list showing how jBoss does and does not comply with each requirement. I also want a list of each of the roles discussed in the document and which roles jBoss and the jBoss organization play in J2EE. It would be a great service (and a pretty good review article for a magazine) to have similar lists for all of the competing EJB containers on the market. I think this compliance map could act as a road map for future developers and could help bean developers choose which container will work for their EJB architecture. For example, right now, if you need bean-managed persistence (BMP), don't use jBoss. For adding BMP support to jBoss, I'm a little hazy on the details. What needs to be done? How much work will it take? Is this the best use of our graduate students, or would jBoss be better off if they solved some other problem or wrote a particular plug-in? -- Ken Jenks, http://abiblion.com/ Tools for reading.
