[
https://issues.apache.org/jira/browse/KARAF-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853909#comment-15853909
]
Christian Schneider commented on KARAF-201:
-------------------------------------------
A simple way to do this is to couple it with a service that encapsulates a
resource. For example if you have a db then the common resource is the
DataSource. So I think the right place to run automatic migration scripts would
be the service that provides the DataSource. The service could make sure the
migration scripts are run before the DataSource is published.
In OSGi there is already a really good system to express dependencies using
capabilities and services. So I think we can implement this in a good way
without touching the feature mechanism.
If you are interested we can look into providing database migration hooks in
pax-jdbc-config which I think would be a good place for this.
> Add post feature installation triggers
> --------------------------------------
>
> Key: KARAF-201
> URL: https://issues.apache.org/jira/browse/KARAF-201
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-core, karaf-feature
> Reporter: Guillaume Nodet
> Fix For: 4.1.1
>
>
> Something like:
> {code}
> <script trigger="post">
> // do anything using gogo commands
> </script>
> {code}
> The result could be displayed to the user so that the installation could give
> him some information (manual steps, or whatever), though it may need a
> separate element.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
