There should have been no coding changes since we tried this in GF v2.1.
Are you asking for deployment descriptors? If so, here they are:
Are you saying GF v3 does support EJB 2.x the same as GF v2.1?
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC
'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
'
http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<description>
Bean-Managed Persistence Entity EJB for managing the Bid Attachment Data.
</description>
<enterprise-beans>
<session>
<ejb-name>ApplicationSecurityBean</ejb-name>
<home>net.meridianleasing.appsecurity.ApplicationSecurityHome</home>
<remote>net.meridianleasing.appsecurity.ApplicationSecurity</remote>
<ejb-class>net.meridianleasing.appsecurity.ApplicationSecurityBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
sun-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 8.0 EJB 2.1//EN" "
http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_1-0.dtd">
<!-- Generated by XDoclet -->
<sun-ejb-jar>
<!--
To add any role mappings, add an Unparsed XML Entity file to your XDoclet
merge directory called sunone-role-mappings.ent that contains the
<role-mapping> elements.
<!ELEMENT role-mapping (role-name, role-impl)>
<!ELEMENT role-impl (group*, user*)>
N.B. This is an Unparsed XML Entity file, rather than an XML Document,
since if there are multiple mappings it will not be well-formed.
-->
<enterprise-beans>
<ejb>
<ejb-name>ApplicationSecurityBean</ejb-name>
<jndi-name>ApplicationSecurity</jndi-name>
</ejb>
<!--
To add any persistence manager descriptors, put an XML Document named
sunone-pm-descriptors.xml in your XDoclet merge directory containing the
<pm-descriptors> element.
-->
</enterprise-beans>
</sun-ejb-jar>
[Message sent by forum member 'shayden' (shayden)]
http://forums.java.net/jive/thread.jspa?messageID=358651