Could you build passivation-safe application?

Question

There are a lot of posts about testing application with disabled application module pooling (Example: http://andrejusb.blogspot.com/2010/01/demystifying-adf-bc-passivation-and.html). We have few adf-application developed in different ways, but no one worked correctly if pooling is off. A lot of features described in blogs and manuals didn’t work if pooling is off, what means that there will be unexpected errors in production environment if you use this features.
I've got a question to developers, not to oracle employees:
Does anyone managed to develop production (not test) application, which correctly works if application module pooling is disabled?
And one more question:
Which problems could I face and how to solve them if I use jbo.ampool.issupportspassivation="false" except there will be no free AMs more?

Answer 1

Thanks for answers.
Now my applications are passivation-safe;
The solution which solved passivation problems was very easy. Just it is necessary to call executeQuery() or executeEmptyRowSet() on viewobject before creating first row in it. This solved all my passivation problems.
So, the right way to create row in fresh viewobject is:
ViewObject vo = am.findViewObject("ViewObjectName");
vo.executeEmptyRowSet();
vo.insertRow(vo.createRow());
And passivation problems will be if row is created in this way:
ViewObject vo = am.findViewObject("ViewObjectName");
vo.insertRow(vo.createRow());
This is correct for 11.1.2.2.0 as for 11.1.1.5.0