I have found some more detailed informations to my problem. The described behaviour rises
if I choose an JBoss AS 3.2 Server as server type. If I choose JBoss v3.2.3 everything
works fine. Does anybody has an explanation for this?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987045#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...