Activation Passivation in Oracle ADF 11g

Opps, does the application runs perfectly for one user and shows weird behavior for multiple users ? is it ? then my gut feeling says the application is not activation safe.
Refer to http://blogs.oracle.com/Didier/entry/set_jboampooldoampoolingfalse_1 by
Didier Laurent - Sr Principal Support Engineer in the JDeveloper team

And once you really find out its an activation passivation issue, here is what you are to do
In your AM Impl class override the activateState(Element elem) and passivateState(Document doc, Element parent) method in the root AMImpl or each of the AMImpl class.

What we actually do in this method is create an XML structure to store the user defined values during passivation and reading those values back on activation.

Keep following as i will shortly upload a sample example to reproduce the error and the way to fix it.

Oracle ADF 11g

Hmm, on the face of it, Oracle ADF 11g seems to be a good choice for Java EE development. Bundled with JDev 11g “Productivity with Choice”, it will give a tough fight to Open Source community (Spring, EJB, etc) at least this is what i can say as of now.

What i will try here is to compare and list out the ways which can help the development community to benefit from Java EE technologies coupled with Oracle ADF, the way to integrate them, my observation on which to use and the common pitfalls to look out for before going to production with Oracle ADF.