-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Samuel Cheung
Sent: Friday, November 21, 2003 6:42 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [OS-webwork] Spring & WW2 -- Status UpdateSorry, I have a newbie question.
Could you please tell me what are the advantages of integrating Spring into WebWork2?
My understanding is both spring and Webwork2 are IoC framework for Web application. Why we need to integrate Spring into WebWork2?Thank you.
-----Original Message-----
From: Matthew E. Porter [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 21, 2003 11:22 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Spring & WW2 -- Status Update
First, thanks to Ross and the Atlassian guys for their work on
integrating Spring into WebWork. A number of people, myself included,
have been wanting this for a few months. They took the initiative and
time to implement this.However, the code in Jira is incomplete at this time. The external
reference code has been integrated into XWork's head. As previously
noted, the sample Spring resolver is missing a ServletContextAware
class. This is trivial to recreate as it is a single interface, but
nothing is currently setting the ServletContext on the class
implementing the interface. Or am I just missing something?Does anyone have any update on this?
Cheers,
matthew
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Title: RE: [OS-webwork] Spring & WW2 -- Status Update
It
dependends on if you want to take advantage of the IoC enhancements that Spring
has. WW2 has a very simple IoC framework, that is part of it's
charm! But, if you want to be dynamically combining components together
with other components, or are using components in non WW environments, then
having a single IoC framework makes life easier.
Also,
different IoC frameworks do different things better or worse. Spring
leverages lots of metadata in XML to hook things together. PicoContainer
uses everything a component needs passed in via a constructory.
Avalon has it's API's that you code against. Not trying to start an
argument/discussion on which are better etc, for more info there are some links
at the bottom.
As an
aside, once the hooks are in for Spring, I'd like to contribute some code to
lookup components from the ECM and Merlin containers from the Avalon
project.
Eric
- [OS-webwork] Spring & WW2 -- Status Update Matthew E . Porter
- Re: [OS-webwork] Spring & WW2 -- Status Updat... Ross Mason
- RE: [OS-webwork] Spring & WW2 -- Status Updat... Samuel Cheung
- RE: [OS-webwork] Spring & WW2 -- Status U... Eric Pugh
- RE: [OS-webwork] Spring & WW2 -- Status U... Drew McAuliffe
- Re: [OS-webwork] Spring & WW2 -- Stat... Matthew E . Porter