[picocontainer-dev] Progress on picocontainer-script and -web
Mauro Talevi <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi all,
just an update on the progress of the Nano components.
The script and web components (previously nanocontainer and nanowar)
have been branched to sandbox and re-branded to live under pico-brand:
https://svn.codehaus.org/picocontainer/java/sandbox/picocontainer-script
https://svn.codehaus.org/picocontainer/java/sandbox/picocontainer-web
picocontainer-web components now use picocontainer-script.
Each still has its independent release cycle and separate groupId
(org.picocontainer.script and org.picocontainer.web respectively).
All unit tests and example webapp now work (with minor binding caveat
with Struts2 example, mentioned in previous email).
Things to note:
- the Nano booter, deployer and webcontainer have been dropped for the
moment as they are not really script-related - more likely a new
deployer-related group. They are of course still accessible in
https://svn.codehaus.org/picocontainer/java/2.x/trunk/nano
- A new WebappComposer interface has been added to web-core, which
effectively superceeds the ContainerComposer - which as always been
intended for webapp composition. Do people feel it's worth to keep
ContainerComposer, and if so what is the use case? Comments on the
WebappComposer approach are most welcome - eg the webapp examples.
- Similarly for ContainerRecorder, which has for the moment been moved
to web-core from script-core. Kostantin, would you happy to loose
recorder and friends (ScopedContainerComposer)?
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email