file a jira issue for this behaviour to be changed.. give it low priority and assign it to
3.3 (but it still could be rejected)... there is a workaround I think to after the start,
re-assign it. Not sure if that works
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060280#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...