Hello All,

Can anyone suggest a design approach for managing the state of a object as it is shared between two different web applications that are deployed on separate application servers but using the same database?

Scenario:
- AppA creates a request object
- AppB approves the request object
- AppA can not modify the request object if AppB is reading the object


Possible approach:
Use a "state" attribute in the object that is persisted to the DB which will be checked by both apps when reading and writing the object. Depending on the state you can read and then modify the request object.

Can anyone suggest an alternate approach? Something clever maybe with Spring/Hibernate ?

Thanks!

Well I Dont know about that problem but First time I used these parameter hibernate.hbm2ddl.auto=create-drop for error appears because table exists, so I think, that parameter hibernate.hbm2ddl.auto=update will solve it.

These information which you can share is one of the great. But I used these parameter hibernate.hbm2ddl.auto=create-drop for error appears because table exists, so I think, that parameter hibernate.hbm2ddl.auto=update will solve it.

Yes actually I also new to use hibernate so I dont have knowledge about it and can any one give me its manual or how to use it. because normally I use it but I dont know more about its features.

To create an error = expression takyi drop due to the presence of these parameters appears hibernate.hbm2ddl.auto use, so I think that hibernate.hbm2ddl.auto = parameter to the update may solve the problem.