-
1. Re: Problems with beans that have been passivated
pmuir Sep 13, 2009 8:04 PM (in response to meetoblivion)John, please file a JIRA for this, I understand (I think) what you are saying, and can see how it might happen. We can certainly fix it (whether it is an easy fix tho ;-).
If possible please attach a test case showing this. If not, a simple example packaged for JBoss AS would suffice :-)
Thanks!
-
2. Re: Problems with beans that have been passivated
meetoblivion Sep 13, 2009 9:35 PM (in response to meetoblivion)Ok, just created WBRI-389.
I have to ask, any idea when a patch/commit could be available for this? I have an app that I want to release public on top of webbeans but this causes an issue with it. Internal apps it's not as much of a problem because a) business users are faster b) business users are more patient. Also, what does the compatibility look like from the old AS 5.1 version and current? Would an app work there without requiring a partial rewrite?
-
3. Re: Problems with beans that have been passivated
pmuir Sep 23, 2009 9:02 PM (in response to meetoblivion)I scheduled it for CR2, so you are looking at around 4-6w.
Web Beans should still work with AS 5.1, we moved to a snapshot of 5.2 as we needed some of the new features there - if you can live with out those, you are safe.