On May 25, 2009, at 12:28 PM, Sergiu Dumitriu wrote:

Vincent Massol wrote:

...

Hi,

I'd like to switch to using the Embedded Container Manager for our tests. The main reason is that I want to introduce the ability to register dynamic mocks from our tests rather having to create static stubs (the MockDocumentAccessBridge classes and co).

Note that our functional tests would still use plexus as the CM thus ensuring that Plexus is correctly initialized.

Here's my +1

+1

Question: Is it possible to replace Plexus completely with our container?

It's possible but: 1) our implementation is far from as robust as the plexus one (multithreading, leaking, etc) 2) the plexus implementation can bring us other advantages such as OSGi support 3) the Embedded version is not supposed to evolve to be complex since I don't think it's our role to implement a DI system. If we can configure an existing and simple DI system to be used instead of our Embedded version I think we should use it in the future.The pb is that we're going to add DI events + Realms soon so it's going to be more complex already... I wouldn't drop it right now. In addition it validates our system can work with different DI systems. Note that I've also started reading up on OSGi and I'm starting to see how we could implement an OSGi adapter that would work for us (using Apache Felix for ex). This is still in research on my side. So right now I'm in favor of keeping plexus and upgrading to the latest release (which is what I'm working on - I need a fix on plexus from jason for that). Thanks -Vincent