<Weblogic>
Making the [session]bean methods synchronized won't solve any reentrancy
problem
since an exception would be thrown the moment you even remotely so try to
"touch"
the session bean from another thread.
We tried synchronizing on the session bean itself but this led to a deadlock
in many cases.
Eventually, we ended up storing a lock object (just any plain object) in the
session and
having every servlet or JSP/JHTML synchronize on a particular lock for any
given session
if more than one EJB session are kept.
This obviously requires extra care to be taken by the developers but it is
only necessary to
do so when a session is accessed by multiple requests(be it from a frame or
a child window)
on behalf of a single and unique client.
</WEBLOGIC>
This method could probably applied to a session bean being shared among
multiple clients(HttpSession)
by storing lock objects in the ServletContext or any other application
context. Haven't tried this though.
Frederic Kam-Thong
Invera Inc.
Westmount, Quebec
-----Original Message-----
From: dan benanav [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 18, 2000 22:18
To: [EMAIL PROTECTED]
Subject: Re: Vendor Challenge
You would have to make sure the beans methods are synchonized for this to
work.
===========================================================================
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".
