what about adding spring ?

Hi;

I have been working a bit with Spring now on other projects. From all 
i can see, it should be possible to use the framework for Scarab's future 
development. Since Spring also promises to support a smooth and silent 
migration path, we could start slowly, then continue migration as 
needed/wanted...

What do you think ? Shall we decide to go to spring now and start with
the following baby steps for preparation and warmup ?

1.) Add Spring to the Scarab distribution (place the jars at WEB-INF/lib)
2.) Start by replacing YAAFI services by Spring services (as a warm up)
3.) remove yaafi

Then it is time to start a serious refactoring. When i look at some classes,
like ScarabRequestTool.java and ScarabGlobalTool.java i have the strong
feeling, that we need to clean up more than only a bit ...

The general master plan is to 

- clean up Scarab
- rework the GUI and refactor business logic out of velocity into ...
spring-beans ?
- allow better integration of third party products (rework/add the API's)
- ...

I am not (yet) a Spring-"expert" and maybe there is a better way to
get things done, but i have the strong feeling, that making this move
can help us a lot. Especially because we do not need a huge refactoring
beforehand to introduce it. We really could start immediately without
breaking anything...

Please tell me your opinion. Would it be a clever move ? Or am i introducing
just another layer of complexity ? 

regards,
Hussayn
-- 
View this message in context: http://www.nabble.com/what-about-adding-spring---tp21418409p21418409.html
Sent from the Scarab - Dev mailing list archive at Nabble.com.

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=1019536

To unsubscribe from this discussion, e-mail: [[email protected]].