The issue was never formally fixed (it is still open). So no real surprise that it is
still an issue in 3.2.2. I've set the fix version to 3.3 so it does not slip of the
radar
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120589#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...