Hi Brett, all,
Have you considered using OSGi instead of [Plexus|Spring] ? I'm not an
expert of one or the other, but i try to do some projects with OSGi
since a few months and i like it.
Best regards,
Brett Porter a écrit :
Hi,
Given the discussion yesterday, I played around with some
Hi Carlos,
Thanks for your answer,
Carlos Sanchez a écrit :
spring has good integration with OSGi to enable Spring beans to be
OSGi services.
Yes, i'm aware that this integration exist and i've read a couple of
meetings reports related to it on the Equinox wiki, but why bother with
the
OK, this is just my personal opinion:
I think choice of Spring OSGi is influenced by a few things:
1) Archiva is looking to garner more contributions from the community.
Moving to Spring would, IMO, definately lessen the learning curve. There
is a comprehensive documentation and large user
Wow, that's cool. :)
On 22/02/2008, at 3:38 AM, nicolas de loof wrote:
Work in progress ...
I've created a PlexusClassPathXmlApplicationContext that accept both
Spring
context files and plexus descriptors as resources.
I also enhanced the XSLT to declare a bean alias for plexus
I've asked springsource guys for help on this topic.
I sent Chris Beams [EMAIL PROTECTED] a simplified project with
testcase to investigate.
Nico.
2008/2/22, Brett Porter [EMAIL PROTECTED]:
Wow, that's cool. :)
On 22/02/2008, at 3:38 AM, nicolas de loof wrote:
Work in progress ...
On 20/02/2008, at 6:33 PM, nicolas de loof wrote:
What about a Combined Plexus context, where the lookup method both
search in
the plexus components and the springFactory ?
This would make initialization more complex, but we could use @
plexus.requirement as is to get spring beans without
Could'nt Spring mimic the PlexusContainer ?
Archiva-webapp can be started with a spring context with support from
webwork/struts2 for IoC. We 'just' have to help the spring context retrieve
the components declared in plexus context files.
As spring and plexus IoC concepts are equivalent, we
I just added support for camelCase properties names using Xalan extension.
I don't know how to register a custom XpathFunction to a standard Trax
Transformer. This will be required to make code fully portable, or maybe we
can hard-code the use of Xalan in place of Trax API.
Nico.
2008/2/20,
This is way cooler than what I was doing :)
Can you replace the calls to the other factories so we can see this in
action with a spring bean and plexus component all wired up?
I wouldn't worry about the portability for now - maybe if it were
donated to Plexus itself that'd require some
Hi,
Given the discussion yesterday, I played around with some changes on a
branch when I got up early this morning to show how we could do a
partial migration to Spring without having to do it all at once.
https://svn.apache.org/repos/asf/maven/archiva/branches/springy
This shows:
-
Hi,
Interesting, could you move this Spring/Plexus to a component in the
plexus svn @ codehaus ?
Thanks,
--
Olivier
2008/2/20, Brett Porter [EMAIL PROTECTED]:
Hi,
Given the discussion yesterday, I played around with some changes on a
branch when I got up early this morning to show how we
What about a Combined Plexus context, where the lookup method both search in
the plexus components and the springFactory ?
This would make initialization more complex, but we could use @
plexus.requirement as is to get spring beans without having to know they are
managed by spring.
Nico.
12 matches
Mail list logo
