"Louth, William (Exchange)" wrote:
>
> HI Arkin,
>
> Are you saying then that Web Logic currently is not EJB 1.1 compliant?
No. The EJB 1.1 spec is not entirely clear on some points. this is one
of them. Nowhere does it say that ejbStore must be called, but the
intent was that is should be called. Hopefully 2.0 will clarify such
issues. I think by this time most of the vendors understand the design
principals of 1.1, whether the spec got it right or not.
> Probably most other servers are not in some way. Sun should already know the
> issues surrounding vague/unclear/incomplete statements in contracts. Ok
> getting back...is there not some compliancy test that we could run to verify
> this against? Do you have access to it? I feel that we need some further
> clarification on this especially if it could potential break some beans that
> are using this call back feature.
I assume that the 1.1 compatibility test does not cover this, since it's
not in the spec. Even if the issue is known, a 1.1 compatibility test
should not attempt to test this.
> This brings me onto another issue that I think I might have raised before.
> Currently I am deploying a session bean into about 4 ejb containers and each
> one has given me some problems. The jar just does not load that easily into
> containers without having to mess around with server configurations (jar
> must be already on the class path....get real, must have a extra line in the
> manifest file with no extension......) and so on. Also some of the client
> code has to be rewritten to take into account that the client must LOGON to
> the ejb server before accessing the beans each in the own different and
> unusual way. What happened to the simple life of just creating a new initial
> context and then performing a name lookup. This is really getting to
> me......
I can't help you with server side deployment. I know must EJB servers
are not that great.
The J2EE blueprints actually define a J2EE container for a client
application. That container should support application JARs, deployment
descriptors (client side) and enlistment in InitialContext. But I assume
no one but the Sun RI supports this model :-)
arkin
>
> kind regards,
>
> William Louth
>
> > -----Original Message-----
> > From: Arkin [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, April 10, 2000 9:33 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Unneeded calls to ejbStore
> >
> > "Louth, William (Exchange)" wrote:
> > >
> > > Do people think that this is breaking the container contract, just
> > working
> > > around it, enhancing it? I need more time to consider what the
> > implications
> > > for these features are. I hope eventually that we can come up with a
> > > standard way (specification ?.0) to address the real world needs that
> > led to
> > > these features being developed.
> >
> > The container should definitely call ejbLoad and ejbStore at the
> > transaction boundaries. That is the only way for the entity bean to
> > engage in any persistent-related behavior.
> >
> > That does not mean that CMP container has to load anything (it can use
> > the cache) or store anything (no changes made). But that's a decision
> > the CMP container can take regarding the fields it manages and only
> > these fields.
> >
> > It's possible that my bean will be doing something else in ejbLoad and
> > ejbStore that is not affected by caching or is-modified, and any missing
> > ejbLoad / ejbStore calls will break my bean.
> >
> > This is a consistent container - component contract that remains
> > consistent regardless of any particular optimizations that CMP
> > containers (but not BMP containers, and not all CMP containers in the
> > same manner) may do.
> >
> > arkin
> >
> >
> >
> > --
> > ----------------------------------------------------------------------
> > Assaf Arkin www.exoffice.com
> > CTO, Exoffice Technologies, Inc. www.exolab.org
> >
> > ==========================================================================
> > =
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> > body
> > of the message "signoff EJB-INTEREST". For general help, send email to
> > [EMAIL PROTECTED] and include in the body of the message "help".
>
> ***********************************************************************
> Bear Stearns is not responsible for any recommendation, solicitation,
> offer or agreement or any information about any transaction, customer
> account or account activity contained in this communication.
> ***********************************************************************
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
