[
https://jira.jboss.org/jira/browse/JBAS-5358?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBAS-5358.
---------------------------------
Resolution: Done
There is no reason for any of the profileservice beans to be in deployers, so the
profileservice-jboss-beans.xml deployment has been moved to deploy.
Move remote access to profile service into deploy
-------------------------------------------------
Key: JBAS-5358
URL:
https://jira.jboss.org/jira/browse/JBAS-5358
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Brian Stansberry
Assignee: Scott M Stark
Fix For: JBossAS-5.0.0.GA
The current deployers/profileservice-beans.xml.bak includes a couple beans that bring in
a dependency on the Remoting connector. This forces the deployment of the remoting
connector in conf/jboss-service.xml instead of in deploy where it belongs. Need to move
the profile service's "ConnectMBean" and
"ProfileServiceInvocationHandler" into deploy.
--
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