Bugs item #522926, was opened at 2002-02-26 13:12
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402704&aid=522926&group_id=31602

Category: ejbdoclet
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Vincent Harcq (vharcq)
Summary: dataHolder not set to null in passivate

Initial Comment:
Hi,

I'm using Bluestone as my application server. And he 
reuses my remote interface this is allowed according 
to the specs. Only then the old data is retruned when 
I call getData() because it isn't created. There must 
be an ejbPassivate methode where the dataObject is set 
to null.

----------------------------------------------------------------------

Comment By: Vincent Harcq (vharcq)
Date: 2002-03-01 11:17

Message:
Logged In: YES 
user_id=125677

Sorry but the spec says that  a bean is resent to the Pool 
in two cases : ejbPassivate and ejbRemove.
If BlueStone reuse instances without calling one of these 
methods then it is a BlueStone problem.
When sending back an instance to the pool it calls 
something right?  unsetEntityContext maybe ?  Then hack you 
xdoclet to call ejbPassivate from unsetEntityContext

Figure 23  - Chapter 10.5.1


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2002-03-01 10:12

Message:
Logged In: NO 

Sorry, it's seems to be an _option_ in bluestone! It will 
not call the ejbPassivate unless you specify it to do so.

----------------------------------------------------------------------

Comment By: Vincent Harcq (vharcq)
Date: 2002-02-28 22:24

Message:
Logged In: YES 
user_id=125677

It is being realeased by ejbPassivate today wich is correct
I also added realsing in ejbRemove() 
ejb 2 spec 10.5.1

----------------------------------------------------------------------

Comment By: Marcus Brito (pazu)
Date: 2002-02-26 13:42

Message:
Logged In: YES 
user_id=360347

The dataObject is serializable, so there is no need to set
it as null during passivation. The application server should
be able to serialize the dataObject during passivation.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=402704&aid=522926&group_id=31602

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to