No, we can't have a neutral namesapce handler, but we could provide two
different handlers, one for spring-dm and one for blueprint.  Both would
support the exact same xml schema.
In the url I gave earlier, you'll find the spring parsers that were used
before switching to blueprint:
   http://svn.apache.org/repos/asf/servicemix/smx4/kernel/tags/kernel-1.1.0
For example:

http://svn.apache.org/repos/asf/servicemix/smx4/kernel/tags/kernel-1.1.0/jaas/jaas-config/src/main/java/org/apache/servicemix/kernel/jaas/config/impl/NamespaceHandler.java



On Wed, Apr 7, 2010 at 01:02, tribon cheng <[email protected]> wrote:

> It's my pleasure if i can provide this patch. i wish to finish this patch
> today.
>
> Would you mind giving me some related resources(like web links) to get
> advanced touch to custom namespaces?
>
> I know that there are two custom NamespaceHandler in karaf which depend on
> geronimo implementation as following:
>
> public class NamespaceHandler implements
> org.apache.geronimo.blueprint.NamespaceHandler
>
> Do you mean that I can provide a neutral NamespaceHandler which depend on
> neither geronimo nor spring-dm?
>
> I need your help, Guilaume, thank you very much!
>
>
> best regards!
>
> 2010-04-07
>
>
>
> Tribon cheng
>
>
>
>
>
>
> 发件人: Guillaume Nodet
> 发送时间: 2010-04-06  22:25:49
> 收件人: users
> 抄送:
> 主题: Re: A question about felix karaf and Spring DM
>
> So I've had a closer look at what would be required.
> The problem right now is that karaf defines two custom namespaces but
> custom
> namespaces aren't standardized by the blueprint spec yet (it's being worked
> on though).
> In the meantime, we could support both spring-dm and aries blueprint
> implementation (former geronimo blueprint implementation) by providing two
> implementations of the same namespace.
> I think there would be one remaining thing to do which is to provide a
> neutral way to access the ConfigAdmin and properties placeholders, which
> basically mean rewriting those namespaces (it should mostly be some
> repackaging thingy as both aries and spring-dm support almost the same
> features).  This way, we could switch easily between spring-dm and aries.
> If you're willing to go that way and provide some patches, i'd be happy to
> help.
> On Tue, Apr 6, 2010 at 15:03, Tribon Cheng <[email protected]> wrote:
> > thank you for your answer, Guillaume.
> > Do you mean that i modify the blueprint configuration xml file contained
> in
> > karaf-jaas.jar and karaf-shell.jar,
> > and use spring-dm specific features instead?
> > In this way I can remove the geronimo blueprint bundle from karaf, it's
> > right?
> > thanks a lot!
> >
> >
> > On Tue, Apr 6, 2010 at 5:28 PM, Guillaume Nodet <[email protected]>
> wrote:
> >
> > > Karaf works well with Spring-DM 1.2.x afaik.
> > > If you really need to use 2.0.x, i suppose it should be possible by
> > > modifying the blueprint xml to use spring-dm specific features instead
> of
> > > the geronimo ones.
> > > Though, it should be possible to have two blueprint extenders under
> > certain
> > > conditions, so we should try to support that if possible.
> > >
> > > On Tue, Apr 6, 2010 at 11:06, Tribon Cheng <[email protected]>
> wrote:
> > >
> > > > I just want to find a OSGI runtime framework which can provide well
> > > > management, hot deploy, log config and so on.
> > > >
> > > > So karaf is a good candidate. But for the blueprint implement, I'd
> > perfer
> > > > to
> > > > choose SpringDM to obtain more features of Spring.
> > > >
> > > > The problem is that karaf contains the geronimal blueprint
> > implementation
> > > > and Karaf-Shell,Karaf-JAAS have strong* dependencies *
> > > > **
> > > > *on it, if i install another blueprint implementation like SpringDm,
> >  the
> > > > blueprint config file will be parsed twice, once by*
> > > > **
> > > > *geronimal and the other by springdm.*
> > > > **
> > > > *can someone give me some suggestions, thanks a lot.*
> > > >
> > > >
> > > > --
> > > > Contribute to Enterprise Integration
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers,
> > > Guillaume Nodet
> > > ------------------------
> > > Blog: http://gnodet.blogspot.com/
> > > ------------------------
> > > Open Source SOA
> > > http://fusesource.com
> > >
> >
> >
> >
> > --
> > Contribute to Enterprise Integration
> >
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Reply via email to