In Jboss 4.0.5GA this problem still occures.. Is it a bug or a human failure. Can any body post a work around or solution please ? Wzzl View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016606#4016606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4016606