• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Non-disk data persistence for MessageBoard RESTful Web Service App

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am working on a Java Web Application very similar to the 'MessageBoard RESTful Web Service App.' that the NetBeans 7.0.1 has. There will be view pages, web service(s) based on JAX-WS or JAX-RS, data persistence mechanism, etc. From the start page, the user can select any service from createMessage, listMessage, deleteMessage.

But the problem is that I should not use EJBs, Database or any other type of disk/file persistence. The user will input name, title & content of the message, I will have to add a valid URL where this message will be viewable. I have to persist the data until the server shuts down. Other fine details which MUST be followed are:

1- The build should produce a war file that can be deployed on Tomcat (web-container).
2- No OS dependencies.
3- No Database or file/disk persistence, I have to persist the data until the server shuts down.
4- App. should be extendable and scalable.
5- Other GUIs are able to use this app.

What I am looking for is:

1- Persistence mechanism, JavaBeans, POJO. I was not able to do it with the JavaBeans option.
2- Solution that takes into account the services / messages properties of the architecture SOA.
3- I know that if I succeeded to write the solution in Java with SOA considerations, I will have no OS dependency and the solution will be extendable and scalable while other GUIs will be able to use the services of my app.
 
Never trust an airline that limits their passengers to one carry on iguana. Put this tiny ad in your shoe:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic