Having both Remote & Local Component interfaces to a Bean?

[Bhanu]

I would appreciate if some one answers the following:-

1) Is it possible to have both the remote & local component interfaces to a Bean( EB/SFSB/SLSB)in the same ejb-jar? If so how to define them in DD.

2) Can CMP filds of EB be primitive?

3) Should EB in EJB 2.0 be CMP & CMT only?

Thanks
Bhanu

[Sylvain Bouchard]

Hi Bhanu,

I'll try to answer all your question.

1) Is it possible to have both the remote & local component interfaces
to a Bean( EB/SFSB/SLSB)in the same ejb-jar? If so how to define them
in DD.


Yes, you can. Here's an example.

    
<enterprise-beans>
<entity>
     <ejb-name>DirectorEntityBean</ejb-name>
     <home>com.somepck.DirectorEntityHome</home>
     <remote>com.somepck.DirectorEntity</remote>
     <local-home>com.somepck.DirEntityLocalHome</local-home>
     <local>com.somepck.DirEntityLocal</local>
 
                     <ejb-class>com.somepck.DirectorEntityBean</ejb-class>
     <persistence-type>Container</persistence-type>
                     ...
                </entity>
</enterprise-beans>

2) Can CMP fields of EB be primitive?


Yes, this is from the EJB 2.0 specs.

The Bean Provider must ensure that the Java types assigned to the
cmp-fields are restricted to the following: Java primitive types and Java
serializable types.



3) Should EB in EJB 2.0 be CMP & CMT only?

No, an EB can be CMP or BMT (Bean-Managed Transaction)


When designing an enterprise bean, the Bean Provider must decide whether
the enterprise bean will demarcate transactions programmatically in the
business methods (bean-managed transaction demarcation), or whether the
transaction demarcation is to be performed by the Container based on the
transaction attributes in the deployment descriptor (container-managed
transaction demarcation).


Hope this will help you

Sylvain
SCJP - SCWCD

[Bhanu]

Thank you Sylvain!!

But I see the following in the EJB 2.0 Spec, which is hinting that Entity Beans can not be BMT. ( Pg:179 10.5.4)

The getUserTransaction method returns the javax.transaction.UserTransaction
interface. Entity bean instances must not call this method.

[ March 03, 2006: Message edited by: Bhanu P Jasthi ]
[ March 03, 2006: Message edited by: Bhanu P Jasthi ]

[Sylvain Bouchard]

Hi Bhanu,

You right, I've read the question too quickly.
I miss the EB part of your question.

This thread might clarify your doubts even further.

https://coderanch.com/t/317305/EJB-JEE/java/why-entity-bean-cannot-manage

Sylvain
SCJP - SCWCD