[jboss-dev-forums] [Design of EJB 3.0] - Re: Transient re-injection

[wolfc]

That's what I keep saying, all these transient fields are not our problem but the app / bean developers problem. So we could lose the functionality all together.
anonymous wrote : The Bean Provider must assume that the content of transient ?elds may be lost between the PrePassivate and PostActivate noti?cations.
  | ...
  | The one exception is that containers are not required to reset the value of transient ?elds during activation[11]. Declaring the session bean?s ?elds as transient is, in general, discouraged.
  | 
In contrary to spec, we are providing a mechanism to help out a bean provider: transient re-injection. Somewhere along the line this has broken down, either TCK or injection refactoring. If we want it fixed we should build it back in, but as a seperate functionality, not hack it into the injection framework.

XPCs, SFSB refs and that kind of stuff is all covered in 4.2.1 and is container (/ our) responsibility, those work fine.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016592#4016592

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4016592