Hi,

The abstraction layer for entities is explained in the EJB 2.0 spec,
chapter 9.4:

 The Bean Provider must define the entity bean class as an abstract class.
The persistence manager provides the implementation class that is used for
the entity bean at runtime.


You can follow this same idiom in EJB 1.1 by creating an abstract entity
class. However, since there's no PM in ejb 1.1 you'll need to create the
implementation class as well. When you migrate from 1.1 to 2.0 you can
leave the implementation to the persistence manager.

-- Juha

At 16:07 2.3.2001 -0500, you wrote:
>Hello,
>
>I have a few quick questions about EJB in general. I hope I can ask it here.
>
>I downloaded a program called ejbDoclet where given a bean class, it will
>create a slew of other classes including:
>
>remote interface 
>home interface 
>primary key class 
>EntityBean CMP layer 
>EntityBean BMP layer 
>bulk data class 
>ejb-jar.xml
>
>What I don't understand is that it creates an abstract class that a CMP or
>BMP class would implement. The abstract class contains all of the business
>methods and required methods that must be implemented from the EntityBean
>class. Why this additional layer of abstraction? Is this defined in a
>specification somewhere? Aren't the only classes required are home, remote,
>and bean classes for an EJB? Why should an additional abstract class be
>implemented by the bean class?
>
>Has anyone here used ejbDoclet before?
>
>Sorry for all the questions.
>
>Thanks.
>
>
>Thanks.
>
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>I haven't lost my mind. It's backed up on tape somewhere.
>
>Patrick Hardy  Doubleday Interactive, Inc.
>Java Web Consultant    401 Franklin Avenue
>*516 873 4693  Garden City, New York 11530
>
>
>
>-----Original Message-----
>From: Kenneth Robinson [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 02, 2001 16:03 PM
>To: 'JBoss-User'
>Subject: [jBoss-User] Setting Context when using WAR files
>
>
>Hi everyone,
>
>I've been experimenting with JBoss for a couple of
>weeks now and am really excited about using it for
>some of our future projects.
>
>I do have two simple (I hope) questions:  
>
>1.  When deploying a WAR file, is there some way of
>explicitly setting the Context?  Obviously this can
>be done when using EARs, but I've been unable to find
>how to do this for WARs.  Currently, the deployer
>seems to just use the file name.  
>
>2.  Hand in hand with the previous question, is
>there any reason I should not be able to deploy
>multiple WARs into the same Context.  The thought
>here is multiple developers will each work on
>separate parts of a larger app, and each can deploy
>as they complete their sections.
>
>Thanks,
>
>Ken Robinson
>
>
>--
>--------------------------------------------------------------
>To subscribe:        [EMAIL PROTECTED]
>To unsubscribe:      [EMAIL PROTECTED]
>
>
>--
>--------------------------------------------------------------
>To subscribe:        [EMAIL PROTECTED]
>To unsubscribe:      [EMAIL PROTECTED]
>
>


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]

Reply via email to