On Tue, Jul 17, 2001 at 10:17:31AM +0200, Tomasz Skutnik wrote:
> Hi !
> 
> I'd like to know what is the policy of JBoss J2EE interfaces development 
>    ? My problem is that I'm implementing WebDAV connector using J2EE 
> connector specification (PFD2 - Proposed Final Draft - 05 April 2001, 
> acquired from www.jcp.org), but JBoss jboss-j2ee.jar contains classes 
> with outdated interfaces (according to this spec). My question is : 
> What's the JBoss policy of implementing (or keeping up-to-date) with 
> specs ? Are we going to move to newer spec (although it's still only 
> PFD) or wait for official release ?

I'm not aware of any general policy on this, but I'd imagine that the
idea is to keep as up to date as possible in the main CVS branch.

Updating JBossCX to PFD2 is something I've been intending to do for
a while (I even logged a job-thingy at SourceForge to remind
myself).  I've had other priorities for a while (and will continue to
have them for a while longer, I hope).

> Taking that we try to follow specs as fast as possible (even PFDs/Drafts 
> etc.) should I post diffs to patch jboss-j2ee.jar sources (removed 4 
> methods from javax.resource.cci.ConnectionFactory interface, few changes 
> in org.jboss.RARDeployer to take deployment descriptor changes into 
> account, and possibly modifying DDs of existings connectors) ? Of course 
> there'll be impact on existing deployment/connector code/DDs, but it 
> should also be quite simple.

I don't think it's necessary to worry too much about backward
compatibility in the main CVS branch.  You'd need to update the
jboss-j2ee interfaces, the JBossCX stuff and the bundled resource
adapters (the JDBC ones from JBossPool and the JMS one from wherever
its source is).

If you want to do this, I'd be grateful.  Submit a patch to SourceForge
and I'll try to find time to review and commit it.

Toby.

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to