Currently i am working on web service application using java. The web service caters for 3 major types one each for Property, Liability and Auto. The internal java program workflow and program logic is built in a modular fashion and shared across the 3 types down till the database queries.
Now I have a need to split each type as a separate web service like AutoWebService, PropertyWebService and LiabilityWebService.
Could you provide your thoughts on what is the best approach for this.
posted 8 years ago
Can someone throw broad ideas based on practical experience or share best practices
Vijitha - May be I am way off but my thought process was to leverage as much of the application code base as possible for the 3 different scenarios I illustrated and not have the need to spawn 3 separate applications but rather have 3 different web service wrappers sitting on top of the same application and each using it in respective ways.
There is lot of collateral in the application which can be shared across the 3 different scenarios and very few subtle differences.
This is a new application so we are open to make design changes. One approach i was thinking was to have separate controller class for each scenario and slam web service annotations on each of them and this way have 3 separate web service implementations generated out of single application code base (ear).