You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2012/11/22 14:22:58 UTC
[jira] [Created] (ACE-306) Pax runner based target server
Tuomas Kiviaho created ACE-306:
----------------------------------
Summary: 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
[jira] [Commented] (ACE-306) Pax runner based target server
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ACE-306) Pax runner based target server
Posted by "Tuomas Kiviaho (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503117#comment-13503117 ]
Tuomas Kiviaho commented on ACE-306:
------------------------------------
Hello Marcel,
What I meant to write was 'in addition' instead 'instead of' because it good to have a solution such as ace-laucher that is self-reliant and works out-of-the-box. What I was after was to have option 3) without having to use management agent. run-target infact uses also the management-agent and not directly the fine-grained bundles so I had to skim though the management agent activator in order to see what makes it tick (which bundles are started and what configurations given out).
The main reason I wrote this issue was that there wasn't really anything in the bin-build.xml nor in the run-target to support the scenario 3). devserver on the other hand has a nice pax runner environment and I think that target environment could be served similarly. Currently I feel that the learning curve is a bit steep for us that are unable to appreciate the work you've put in to make thing easier. :-)
> 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