[jboss-jira] [JBoss JIRA] Commented: (JBAS-5348) Move remoting configuration into deploy

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12437534#action_12437534 ] 

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"?

> Move remoting configuration into deploy
> ---------------------------------------
>
>                 Key: JBAS-5348
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5348
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Remoting
>            Reporter: Adrian Brock
>            Assignee: Ron Sigal
>             Fix For: JBossAS-5.0.0.GA
>
>
> Move the remoting configuration into deploy from jboss-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