Jerome Louvel <contact <at> noelios.com> writes: > > > Hi there, > > Thanks for providing such a detailed feed-back. That helps to understand how > people actually use the framework and what are the pain points. > > Your approach works but has a drawback. If at some point later you prefer to > run your application as a standalone application instead of embedded in a > Servlet container, then you will have to port it to use the provided > SpringContext which works in both cases. > > Best regards, > Jerome >
Hello, I do agree, porting might pose an issue. But here's the scenario: I have an existing application, that provides much of the functionality as services. My front access layer simply uses these services. This already exists. There's MVC [jsp/html] that exists, DWR for Ajax. All of them use the service interface, which basically consists of POJO's and access data layer [Hibernate] if and whenever needed. My attempt was to just add 1 more front-access, exposing certain services based on REST [re-using existing service interface, by simply wiring them to Restlets]. I could not find any good solution to do it. If I use XMLBeanReader, can I still access my already wired Services, by simply <ref bean="statsService" /> ? Maybe I will have to try. Has anyone tried it? Is there any better way, cause anyways having dependency on services makes it hard to port / unembed and deploy as standalone...
