So depending on which karaf version you use, the ext namespace has changed.
In karaf <= 1.4.0, the namespace is
xmlns:ext="http://geronimo.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
as shown in
http://svn.apache.org/repos/asf/felix/releases/karaf-1.4.0/shell/ssh/src/main/resources/OSGI-INF/blueprint/shell-ssh.xml
While in karaf >= 1.6.0, the namespace is
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
http://svn.apache.org/repos/asf/felix/releases/karaf-1.6.0/shell/ssh/src/main/resources/OSGI-INF/blueprint/shell-ssh.xml
This is because the blueprint implementation has been moved from
Geronimo to Aries project ...
If you use the right one, you should not have the grace period problem anymore.
On Wed, Jul 7, 2010 at 13:53, Jean-Philippe Clement
<[email protected]> wrote:
> Hello, I'm using Karaf and I would like some help.
>
> I would like to simplify the configuration of my bundles blueprint XML
> files. I wish I could write something in those files such as
> "${mydefaultvalue}" which would be automatically resolved when the bundle is
> loaded.
>
> Karaf manual gives an example which mentions the "blueprint-ext" xmlns:ext
> namespace. Looking into that direction I found things about "blueprint-cm"
> (xmlns:cm).
>
> However, using either ext or cm leads my bundle to be stuck to the
> "GracePeriod" state.
>
> Could you please help me resolving this problem?
>
> Thanks.
>
> Jean-Philippe Clément
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
