I am running into what looks like the exact same problem with version 2.7.0. Is there any
chance that 2.7.0 missed the fix?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207426#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...