On 9/25/14 09:16 , Raymond Auge wrote:
On Thu, Sep 25, 2014 at 9:08 AM, Peter Kriens <peter.kri...@aqute.biz
<mailto:peter.kri...@aqute.biz>> wrote:
Somebody in your system must do the schema migration. This bundle
should create a synthetic bundle with the capability that
describes the current version. When this bundle migrates the
database, it first deletes the synthetic bundle (if present) and
refreshes. This will unresolve anybody that has a DB dependency.
You then migrate the db, knowing nobody uses it that depends on it.
Then you install a new synthetic bundle with the updated schema
version capability and refresh again. Only the bundles that can
handle the new version will resolve.
Tom and I had a brief discussion about this and he came up with about
the same model of synthetic bundles housing the capabilities.
... wouldn't it be nice if we could create capabilities through an
API? R7?
I would think that for such special use cases, generating a bundle would
suffice, since it can easily be done at run time. Why keep adding
features for more and more specialized use cases when they can be
accomplished already?
-> richard
This would be an extremely powerful feature and not very far out from
what the current wiring API can already do (except not for packages).
--
*Raymond Augé*
<http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
Senior Software Architect
*Liferay, Inc.* <http://www.liferay.com> (@Liferay)
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
