Hi Kevin...
Accessing entity beans through session beans is usually the recomended
procedure, but it does depend on what your doing.
Jim
--On Sunday, October 22, 2000 10:32 AM -0700 "Duffey, Kevin"
<[EMAIL PROTECTED]> wrote:
> Thanks.
>
> Good news...I used ANT 1.1 and made a simple build script that compiles my
> com.company.ejb folder into a .jar file including the META-INF dir. I was
> finally able to get EJB deployed!!! So i am stoked about that. I do have a
> lot to learn still, and the spec from what I heard was mostly for vendors
> to understand..didn't help developers too much. But I will read it again.
> I am also still reading on an EJB book from ORiely press that covers EJB
> 1.1. It talks more about CTM's than EJB J2EE servers to my surprise, but
> I suppose they are the same thing.
>
> I really want to use stateless EJB session objects that work with entity
> objects. I don't want my web/client side to access entity objects
> directly...I don't know if thats the right way or not. What do you think?
> One of our developers here thinks we should just use Entity objects
> directly, but I don't see how that will help locate our logic on the ejb
> server. Do ejb session objects work directly with entity objects?
>
> Ahh..so much to learn..so little time. I think I'll be just in time for
> EJB 2.0! :)
>
>
>> -----Original Message-----
>> From: Juan Lorandi (Chile) [mailto:[EMAIL PROTECTED]]
>> Sent: Friday, October 20, 2000 2:52 PM
>> To: Orion-Interest
>> Subject: RE: EJB Help..
>>
>>
>> the create method must reside in the Home interface and must match an
>> ejbCreate method in the bean class...
>>
>> the Home And Remote interfaces (Login.java and LoginHome.java) must be
>> implemented somewhere,
>> because the Bean class doesn't implement it...
>>
>> EJB Servers/Containers, at deploy time, build a class that
>> implements them
>> and calls your ejb--
>> providing an indirection pattern which enables to provide transaction,
>> security, caching and pooling support
>>
>> I suggest you read (again) extra carefully the ejb spec, and
>> don't skip any
>> section, specially the ones about
>> Container responsabilities, this will give you the insight to
>> know why your
>> app isn't behaving well...
>>
>> HTH,
>>
>> Rifle
>>
>> PS: Copies of your Login*.java and the ejb-jar.xml would be welcome...
>>
>> -----Original Message-----
>> From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
>> Sent: Viernes, 20 de Octubre de 2000 17:22
>> To: Orion-Interest
>> Subject: RE: EJB Help..
>>
>>
>> HI,
>>
>> > Double check your ejb-jar.xml--are you setting LoginHome as
>> your Home
>> > interface in there? Is there a LoginHome.create() method
>> > declared? Is there
>> > a LoginBean.ejbCreate() method defined?
>>
>> Hmm..I don't have a LoginHome.create()..the Orion Primer
>> didn't show that. I
>> have a Login.java, LoginBean.java and LoginHome.java. I think
>> Login.java is
>> the only one with a create() method in it. Should both the "interface"
>> classes have a create() in it?
>>
>> Also, why is Orion trying to compile it if its already
>> compiled? Or is this
>> some sort of "assembly" routine Orion does? I assume from
>> what I read that
>> the EJB server "implements" the interfaces..so is it
>> generating its own code
>> at runtime and that is what compiling is failing?
>>
>> Thanks again.
>>
