Snjezana,
Hi,
Currently, JBDS creates AS and Seam Runtime if EAP is included in JBDS.
No one runtime will be created if EAP and/or SOA-P is added by the user.
Taking this into consideration, I propose the following:
1) creating a new plugin (org.jboss.tools.runtime) that would start:
It looks like
devstudio repository is right place for plug-ins related
to JBDS functionality.
- JBoss AS
- Seam
- JBPM
no matter if they are added by the user or EAP is included in JBDS.
The plugin would depend on jboss.as, seam, jbpm (and drools) and use
the startup ext. point in a way similar to the the
org.jboss.tools.jst.firstrun plugin. It would always be loaded, but
the required plugins (jbpm, seam, as, drools) would be loaded only
when creating a workspace (if their runtime exists). The code for
initializing Seam Runtimes would be moved to this plugin.
We could also use the org.jboss.tools.jst.firstrun plugin if it is
possible to add these dependencies to it.
Now seam runtimes are initialized in
org.jboss.tools.seam.core/SeamFacetPreferenceInitializer.java. We cannot
add seam as dependency to firstrun plug-in because it would be a cyclic
dependency: seam depends on richfaces, richfaces depends on seam.
Question :
If the user adds SOA-P, EAP and AS servers, do we need to create
runtime for all of them?
We can add one more step to installer and provide UI to
configure
runtimes too. It would ask to find available runtimes in added servers
and allow to edit list of runtimes, but that's not a simple way :)
Denis
Snjeza