[
https://issues.apache.org/jira/browse/GERONIMO-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-6263:
-----------------------------------
Description:
with the rebase on karaf 3 the old strategy of starting geronimo app client via
a separate main class doesn't really work any more. I've started on a way of
running app clients as karaf instances.
(implemented, not all tested)
-- expose command line args through geronimo ServerInfo (just like they are now
exposed in karaf ServerInfo)
-- have the app client gbean get the client args from ServerInfo
-- use the -o <artifactId> option to start the app client, thus ignoring the
contents of config.xml as a persistent configuration list
-- have the app client gbean stop the framework after the app client main
method exits.
-- install the client instance from a .kar file
(need to do)
-- modify/write a script to start karaf with the -o <artifactId> option
-- figure out what "clean" options are needed so different app clients don't
interfere with each other.
-- figure out if the instance/instance.properties can be left out.
-- edit config files in instance/client so they are more appropriate for an app
client. For instance var/config/config.xml should probably be empty.
-- make sure everything works :-)
was:
with the rebase on karaf 3 the old strategy of starting geronimo app client via
a separate main class doesn't really work any more. I've started on a way of
running app clients as karaf instances.
(implemented, not all tested)
-- expose command line args through geronimo ServerInfo (just like they are now
exposed in karaf ServerInfo)
-- have the app client gbean get the client args from ServerInfo
-- use the -o <artifactId> option to start the app client, thus ignoring the
contents of config.xml as a persistent configuration list
-- have the app client gbean stop the framework after the app client main
method exits.
-- install the client instance from a .kar file
(need to do)
-- modify/write a script to start karaf with the -o <artifactId> option
-- figure out what "clean" options are needed so different app clients don't
interfere with each other.
-- figure out if the instance/instance.properties can be left out.
-- make sure everything works :-)
> App client as karaf "instance"
> ------------------------------
>
> Key: GERONIMO-6263
> URL: https://issues.apache.org/jira/browse/GERONIMO-6263
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: application client
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> with the rebase on karaf 3 the old strategy of starting geronimo app client
> via a separate main class doesn't really work any more. I've started on a
> way of running app clients as karaf instances.
> (implemented, not all tested)
> -- expose command line args through geronimo ServerInfo (just like they are
> now exposed in karaf ServerInfo)
> -- have the app client gbean get the client args from ServerInfo
> -- use the -o <artifactId> option to start the app client, thus ignoring the
> contents of config.xml as a persistent configuration list
> -- have the app client gbean stop the framework after the app client main
> method exits.
> -- install the client instance from a .kar file
> (need to do)
> -- modify/write a script to start karaf with the -o <artifactId> option
> -- figure out what "clean" options are needed so different app clients don't
> interfere with each other.
> -- figure out if the instance/instance.properties can be left out.
> -- edit config files in instance/client so they are more appropriate for an
> app client. For instance var/config/config.xml should probably be empty.
> -- make sure everything works :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
