You can detect if a jar is an EJB 2.0 jar by looking at the DOCTYPE.  I 
already do this in ApplicationMetaData, so all you need to do is call 
isEJB2x().

-dain

marc fleury wrote:

> 2.0 is so much more powerful than 1.1 we will support only 2.0 when it is
> stable.  For now we need both,
> 
> marcf
> 
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of
> |Adrian Brock
> |Sent: Monday, March 04, 2002 7:13 AM
> |To: [EMAIL PROTECTED]
> |Subject: [JBoss-dev] Guidance required EJB1.1/2.0
> |
> |
> |Hi,
> |
> |I'm apply the create<METHOD> patches from sourceforge.
> |As the patch says the verifier code is incomplete.
> |The 2.0 verifier does not exist, the patch allows
> |create<METHOD> for 1.1
> |
> |I was wondering, do we need to support both 1.1 and
> |2.0 in the container as well? The spec suggests
> |we should for at least CMP. I couldn't find it
> |stated explicitly for other types.
> |
> |Regards,
> |Adrian
> |
> |_________________________________________________________
> |View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=10128
> |
> |_______________________________________________
> |Jboss-development mailing list
> |[EMAIL PROTECTED]
> |https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 



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

Reply via email to