[ https://jira.jboss.org/jira/browse/EJBTHREE-1641?page=com.atlassian.jira.... ] Dimitris Andreadis commented on EJBTHREE-1641: ---------------------------------------------- How come this is unscheduled? As it is now, while booting AS 5.1.0.Beta1 you get a bunch of: ... 17:56:28,765 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:28,781 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:30,578 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:30,593 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:30,781 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:32,000 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:32,000 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co mpatibility between EJB3 and AS is resolved 17:56:32,109 WARN [Ejb3Deployment] [EJBTHREE-1641] NoOp setRemoteProxyFactoryRe gistry; developers may ignore this message; it will be removed when backwards-co ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-1641?page=com.atlassian.jira.... ] Andrew Lee Rubinger updated EJBTHREE-1641: ------------------------------------------ Fix Version/s: 1.1.2 (was: Unscheduled) Affects Version/s: 1.1.1 Thanks, D - this should have been set when I did release scheduling. EJB3 Plugin must be compatible w/ latest AS release, so now that 5.0.1 is out I can fully resolve. ie. First fix + deprecate, then remove stuff. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-1641?page=com.atlassian.jira.... ] Andrew Lee Rubinger resolved EJBTHREE-1641. ------------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/EJBTHREE-1641?page=com.atlassian.jira.... ] Andrew Lee Rubinger reopened EJBTHREE-1641: ------------------------------------------- May be resolved fully only when AS 5.1.x is out. Then revert r84888 to close. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira