RE: [picocontainer-dev] Argumentative PC

--- Jörg Schaible <[email protected]> wrote:

> The existing JMX code also provide a quite complex
> solution for the name
> mapping. I'd really dislike to have a second
> implementation like we have
> now two XML based Nano dialects.

I would propose to split remoting so there are  clear
subproject boundaries - jmx by itself is not really
remoting and this stuff is better in gems (as jmx is 
core feature of java) 

as for 2 xml based dialects - neither of them is
trully complete. they should be merged - great feature
of xstream is to provide primitives / simple constants
of 
various types.  but there is no way to play around
with behaviours - but it should.  

the only way to use all features is to go groovy. 

as for JNDI - I propose:
1. JNDI Object reference
2. Behaviour based on it ( registering ) - this could
be even generic behaviour which stores component in
whatever reference is provided upon creation
3. JNDI component adapter, as current EJBClientAdapter
is tied to EJB spec and is not what we really need
there ( this new adapter could be base for EJB stuff )


I would propose everything shall go into gems, but
nano-jndi would also do. 

regards,

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


       
____________________________________________________________________________________
Choose the right car based on your needs.  Check out Yahoo! Autos new Car Finder tool.
http://autos.yahoo.com/carfinder/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email