Yes, it has been removed as there is no more requirement for application
code to lookup for dependencies from either PlexusFactory or SpringFactory.
All the spring-support related code has move to plexus-spring project (at
branch root).
plexus-spring will inject components/beans created in a
PlexusConfiguration support is now fixed.
archiva-configuration tests pass with no change required, except :
PlexusTestCase -- PlexusInSpringTestCase
add getSpringConfigLocation() to return path to the new
spring-context.xmltest resource
[INFO]
Support for plexus property to Properties added in plexus-spring,
Now have the following error when first access to /archiva webapp :
Caused by: java.lang.ClassNotFoundException:
redbackEnvironmentCheckInterceptor
at org.apache.catalina.loader.WebappClassLoader.loadClass(
That beeing said, with xwork xml files converted I can start archiva and
register my admin account RUNNING ON SPRING !
Hey Rahul, seems you can start using plexus-spring on Continuum !
Nicolas
2008/2/28, nicolas de loof [EMAIL PROTECTED]:
Support for plexus property to Properties added in
Awesome! Almost weekend, so I will get my hands dirty now.
Hopefully Brett will finish moving the SVN repo for Continuum :-)
Thanks Nicolas!
Rahul
nicolas de loof wrote:
That beeing said, with xwork xml files converted I can start archiva
and register my admin account RUNNING ON SPRING !
It's a bit of a hack, but if a bean lookup fails for
Something#something, can you just remove the trailing #something and
try again? I assume this is the problem?
- Brett
On 29/02/2008, at 3:46 AM, nicolas de loof wrote:
That beeing said, with xwork xml files converted I can start archiva
The problem is inverse :
The bean is registered in spring context as Interface#role-hint (for example
: id=action#searchAction for a webwork action bean) and the Spring
ObjectFactory ask for a bean with only the role-hint.
A hack solution would be to use a custom SpringObejctFactory and search
For your information, plexus-spring no handle plexus requirement without
filed-name set.
The -Dplexus-spring.debug=true option can be used to dump the translated
spring XML (using dom4j)
PlexusInSpringTestCase as been used as replacement for PlexusTestCase in
archiva-policies with no other
Hello,
I've repackaged and improved the spring support for plexus components in a
dedicated poject
--
https://svn.apache.org/repos/asf/maven/archiva/branches/springy/plexus-spring/
This new module provides runtime translation from plexus component
descriptors to a Spring XML context, using a
Can someone confirm the plexus behavior for IoC :
When the target field is a Map or a Collection and no role-hint is
specified, inject all component implementations
When the target field is the component interface and no role-hint is
specified, inject the no-hint component or the one with
On 25/02/2008, at 10:23 PM, nicolas de loof wrote:
Can someone confirm the plexus behavior for IoC :
When the target field is a Map or a Collection and no role-hint is
specified, inject all component implementations
When the target field is the component interface and no role-hint is
On plexus XML descriptors, the field-name seems to be optional... (
CacheFailuresTransferTest.xml)
This makes things more complex on the spring side. Is this a common use case
or can we live without this feature ?
I've found the bug in archiva-proxy CacheFailuresTransferTest : there was
some
On 26/02/2008, at 1:46 AM, nicolas de loof wrote:
On plexus XML descriptors, the field-name seems to be optional... (
CacheFailuresTransferTest.xml)
Yes, I think it will attempt to guess based on the interface type if
there is only one.
This makes things more complex on the spring
This makes things more complex on the spring side. Is this a common
use case
or can we live without this feature ?
If that's not doable, can we throw an unsupported exception if it's
not given?
An ApplicationContextException is thrown in such case on current codebase. I
will
archiva-proxy CacheFailuresTransferTest and archiva-policies
CachedFailuresPolicyTest no pass running under spring applicationContext.
I've added a minimal Contextualizable support for components that do lookup
in the plexusContainer.
Some more work required to build full archiva with spring ;-)
Hi Nicolas,
Sorry, I have looked at the recent updates to the code, hence my
question. Is this 'ready' enough to be used outside Archiva? I'd like to
integrate this into Continuum.
I think it might make sense to have this module in Plexus SVN repo - wdyt?
Good stuff!
Cheers,
Rahul
nicolas
Opps, I meant...
I haven't looked at the recent updates to the code...
PS: Sorry about the earlier empty msg.
/me slaps wrist - need to reinstall my mail client!
Rahul
On Tue, Feb 26, 2008 at 9:47 AM, Rahul Thakur
[EMAIL PROTECTED] wrote:
Hi Rahul,
Thanks for yout interest for this plexus-to-spring migration helper.
The code is still early experimental and requires some more testing : it
only has been tested on 2 archiva testcases and requires many fixes and
testcases to get stable.
Please give me one week to test it more, add
nicolas,
This is way cool!
A very slick way of helping the transition.
I'm looking forward to some free time to dive into it.
- Joakim
nicolas de loof wrote:
Hi Rahul,
Thanks for yout interest for this plexus-to-spring migration helper.
The code is still early experimental and requires
19 matches
Mail list logo
