[ http://jira.jboss.com/jira/browse/JBAS-4499?page=comments#action_12366522 ] Clebert Suconic commented on JBAS-4499: --------------------------------------- Dimitris.. I have assigned this to you.. for your evaluation first. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4499?page=all ] Adrian Brock closed JBAS-4499. ------------------------------ Resolution: Deferred I'm deferring this issue. I don't care what policy you use for JBoss Messaging, but for the Appserver you need to raise a discussion thread in the forums where we can decide what JIRA issues need raising, NOT the way you have done it which is the wrong way around. 1) The JMSProvider is an integration api of the appserver. It is not intended to be used by other projects. It is simply wrong to do integration work inside external projects all integration work should be in the JBossAS codebase. 2) This api is wrong anyway. If we are going to push a shared jms provider api into core libs then we need to rework it as plain factory for connection factories and destinations (which could be implemented using jndi). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira