RE: [OS-webwork] Pico/Nano integration and Velocity/Sitemesh

[Jason Carreira]

Title: Message

Matt Ho had integrated Pico into XWork... His approach (the right one I think considering Pico's... *ahem*... "unique" design constraints) was to replace the ActionProxyFactory implementation to be able to control Action instantiation. This still won't fix your serialization / deserialization issues, but I think they're planning to make the DefaultPicoContainer serializable and handle those issues. Then the main issue will be that you cannot re-wire dependencies, meaning you can't ship Actions across the wire to execute them remotely (like the ClientDispatcher does) -----Original Message----- From: Christian Meunier [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 7:40 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Pico/Nano integration and Velocity/Sitemesh Hi all,   now that pico stuff have been removed from xwork, what is the best way to plug pico into xwork ? Reading few Jason's posts on the pico dev list, it seems near impossible to do it the interceptor way. Is someone working on an xwork integration for nano ? ( i saw webwork1 stuff in the cvs)   On my next project, i am planning doing it all with velocity and i wonder how i can use sitemesh with it ( i dont want any jsp), i remember someone said he has some velocity directive or something to do the "trick".   Regards Chris