[jbosstools-issues] [JBoss JIRA] (JBIDE-10803) JBoss AS 7.0.2 server start not detected

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12687616#comment-12687616 ] 

Snjezana Peco commented on JBIDE-10803:
---------------------------------------

{quote}
And yes, I was not talking about plugin dependencies but example dependencies.
{quote}

This issue is related to plugin dependencies.

{quote}
if we add the management api's as direct dependencies that screws up classloading afaik and makes it impossible to install multiple versions as7 management API afaics.

I'm not completely following what you mean by this:
"definning the JBoss AS 7.x/EAP 6 servers/runtimes in as.management.* plugins (as.core could be installed without as.management.* plugins, but wouldn't include JBoss AS 7.x/EAP 6 servers/runtimes)"

Why should as.management.* have server/runtimes ? the intent of as.management.* is to allow for multiple versions of the management API over time to be used by server/runtimes.
{quote}

Because as.core can't create AS 7/EAP 6 runtimes. This plugin declares AS 7/EAP6 extension points, but can't create runtimes. It realy depends on management.* plugins, but this dependency isn't declared in the OSGi manifest. If a plugin declares an extension point, it would have to be capable to create it.

In my opinion the classloading problem can be easily solved using different plugins for different APIs.
That means the following:
JBoss AS 7.0 Runtime would be in its own plugin and use a separate API. The AS 7.0 server/runtime extension points would also be defined in this plugin.
JBoss AS 7.1 would be in other plugin. I suppose EAP 6 and AS 7.1 use the same API and could be defined in the same plugin. This plugin would include AS 7.1/EAP 6 server/runtime ext. points.
These two plugins would be independent on each other and would have their own classloader. 

This way, as.core wouldn't include AS 7/EAP 6 runtimes and this issue wouldn't happen.

                
> JBoss AS 7.0.2 server start not detected
> ----------------------------------------
>
>                 Key: JBIDE-10803
>                 URL: https://issues.jboss.org/browse/JBIDE-10803
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, JBossAS/Servers, updatesite
>    Affects Versions: 3.3.0.Beta1
>         Environment: Eclipse Java Indigo x86_64, installed only central,central community & dependencies
> JBoss Tools nightly build 3.3.0.v20120205-1417-H4165-Beta1
> Fedora 16, 64b
> JBoss AS 7.0.2
>            Reporter: Radim Hopp
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.Beta3
>
>
> When trying to start JBoss AS server, the server is started correctly, but IDE won't recognize that it's already started (job "Starting <server name>" won't end).

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