• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

Rest with spring video course question II

 
Greenhorn
Posts: 13
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I like the sound of this video.

As someone starting from scratch on RESTful WS, I have the following question.

I have a wicket web app, and it is managed as a spring application, where I use IoC, annotations and spring-hibernate.

Should I create a separate application to handle RESTful WS? Would adding spring REST make my application less modular?

Thanks in advance,
Lucas
 
Rest with Spring Software Support
Posts: 35
5
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That depends. Overall, and without knowing more about your architecture, goals and constraints - I would lean towards modularity. More concretely - using most of the layers you already have and packaging them in a separate deployable unit that exposes the REST API. That generally affords you the mist flexibility if you're OK with having a separate deploy process.
Hope that helps - and keep in touch.
Cheers,
Eugen.
 
reply
    Bookmark Topic Watch Topic
  • New Topic