This page last changed on Jul 14, 2011 by cortextual.

It looks like the Controller is using Spring 2.x (although I had to extract spring.jar and look at MANIFEST.MF to figure that out ...)

Is there any resistance to moving to Spring 3? Spring MVC has great support for REST (so we wouldn't need RESTEasy, not that RESTEasy isn't good). Also, Spring 3 has a very convenient REST client, which should simplify the ISY-99 protocol implementation a bit (not that writing a REST client with the Apache HTTP client is that complicated).

I'd rather not tie any of our REST to Spring for the time being, as it makes replacing Spring more complicated if we need to slim down to smaller runtimes (e.g. pure HTTP parsing) – so no do not want to increase dependencies there beyond IOC use of Spring (the other uses should stay the same or faded out if needed, until we have a more clear idea what OR Box will look like).

Posted by juha at Jul 14, 2011 22:35

That's an excellent reason, which also reminds me that I need to make a post about using Google Guice for the Android Console. If all we're using Spring for is dependency injection, than it could easily be replaced with Guice. Additionally, Spring might be available in a smaller form (meant for J2ME) for use on an Android device, but I haven't tried that out.

Posted by cortextual at Jul 14, 2011 23:08

I need to make a post about using Google Guice for the Android Console. If all we're using Spring for is dependency injection, than it could easily be replaced with Guice.

Yes, please do.

Posted by juha at Jul 14, 2011 23:36
Document generated by Confluence on Jun 05, 2016 09:32