Re: getting rid of create/destroy altogether, how many other significant incompatible changes to the API have been made? If we got rid of the Fqn constructors as was discussed at the beginning of this thread, ignore the rest of this post. :-) If the API is basically compatible w/ 2.x, that's an argument for leaving create/destroy around even if we internally move their functionality to start/stop. That is, don't make people rewrite their apps/prevent upgrades for a minor API cleanliness benefit. No longer having Fqn constructors means nearly everyone has to rewrite their apps, in which case might as well clean up whatever you can. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168772#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...