ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACE-306) Pax runner based target server
Date Thu, 22 Nov 2012 13:34:59 GMT

    [ https://issues.apache.org/jira/browse/ACE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502771#comment-13502771
] 

Marcel Offermans commented on ACE-306:
--------------------------------------

Tuomas, you are aware that you can either:

1) Use the launcher as an all-in-one executable jar that gives you Felix + a management agent.
2) Use any framework, install the management agent, which is available as a stand-alone bundle,
and go from there.
3) Use the more fine-grained bundles that make up the management agent (as is done in the
run-target project in Bndtools).

Also, with 1) it is very easy to launch a different framework, since this code already supports
the OSGi standard launcher API. A quick look does reveal that we currently rely on one Felix-specific
feature (to start extra activators as part of the system bundle). So, with a bit of work,
this launcher could be setup to launch whatever framework is on the classpath (but at the
cost of having to put both the launcher and a framework on the classpath yourself, which is
slightly more complex than just java -jar launcher.jar). Anyway, if you have suggestions on
how to improve this, feel free to make them here and we can see how we can make it easier
and more flexible for you.
                
> Pax runner based target server
> ------------------------------
>
>                 Key: ACE-306
>                 URL: https://issues.apache.org/jira/browse/ACE-306
>             Project: ACE
>          Issue Type: New Feature
>            Reporter: Tuomas Kiviaho
>
> It would be nice to have an open set of bundles instead of using ace launcher that embeds
everything together and forces using felix framework. I suggest that similar pax runner environment
would be provided by the ant script as it is now done for devserver.
> As bonus the configuration can be done using cfg files instead of CLI parameters.
> A downside is that for small projects there will be more ace bundles than actual project
bundles which gives a messy appearance in console. This can be avoided using OSGi subsystems
in the future.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message