[
https://issues.jboss.org/browse/JBIDE-10344?page=com.atlassian.jira.plugi...
]
Rob Cernich commented on JBIDE-10344:
-------------------------------------
You should be able to correct this by removing the immediate flag from the service
declarations in the jboss-management-service.xml files. The services should only be
loaded when they are picked up by as.core.
I've modified the binaries in my Eclipse install and I haven't had any problems.
You might also want to make the names of the services unique (there's a warning in the
Eclipse log, two services with the same name).
consider refactor how AS7 management service is done to avoid eager
loading
---------------------------------------------------------------------------
Key: JBIDE-10344
URL:
https://issues.jboss.org/browse/JBIDE-10344
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: JBoss Tools 3.3.0 Nightly (2011-11-30_14-04-32-H4078)
Mac + Ubuntu
Reporter: Rob Stryker
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.0.Beta1
AS71 and AS70 management interfaces points back to as.core causing eager loading.
could move the as.core interfaces into a shared bundle instead or not use declarative
services for AS7.
Need to consider the options.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira