Is there any way to work around this issue?
Is there anyway to invalidate the bean so that its CMR relationship is reloaded even if it
has already been involved in a transaction?
Has the issue been targeted for correction in any specific release?
Thanks,
Jack
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983521#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...