[ http://jira.jboss.com/jira/browse/JBAS-5348?page=all ] Adrian Brock closed JBAS-5348. ------------------------------ Resolution: Done -- 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-5348?page=all ] Brian Stansberry reopened JBAS-5348: ------------------------------------ Assignee: Brian Stansberry (was: Adrian Brock) Re-opening to deal with deployers/profileservice-beans.xml remoting connector dependency. -- 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-5348?page=comments#action_12405985 ] Brian Stansberry commented on JBAS-5348: ---------------------------------------- Adrian had another solution. :-) The beans that provide remote access to the profile service need to go into deploy, which will allow the remoting connector to go back into remoting-service.xml. See JBAS-5358. -- 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

[ https://jira.jboss.org/jira/browse/JBAS-5348?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned JBAS-5348: -------------------------------------- Assignee: Ron Sigal (was: Brian Stansberry) Ron, I'm passing this one over to you. It's logically related to what you're doing on JBAS-3926. -- 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/JBAS-5348?page=com.atlassian.jira.plug... ] Ron Sigal commented on JBAS-5348: --------------------------------- The actual moving from conf to deploy has already been done (again) by Scott (JBAS-4814 "Refactor the conf/jboss-service.xml services"), but I've just moved the Remoting stuff from deploy/remoting-service.xml to deploy/remoting-jboss-beans.xml. There's somewhat more commentary on JBAS-3926 "Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml". Note that all that remains in deploy/remoting-service.xml is "jboss:service=invoker,type=jrmp", "jboss:service=invoker,type=local", and "jboss:service=invoker,type=pooled". so Brian's comment above about renaming remoting-service.xml is relevant again. "legacy-service.xml"? "legacy-invokers-service.xml"? -- 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