• Post Reply Bookmark Topic Watch Topic
  • New Topic

multiple WSDL deployments from one application code  RSS feed

 
manish ahuja
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All,

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.


Regards,
 
manish ahuja
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can someone throw broad ideas based on practical experience or share best practices
 
Vijitha Kumara
Bartender
Posts: 3973
24
Chrome Fedora Hibernate
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The internal java program workflow and program logic is built in a modular fashion and shared across the 3 types

What dependencies exist here with each other that you cannot execute a service individually?
Now I have a need to split each type as a separate web service like AutoWebService, PropertyWebService and LiabilityWebService.

What are the modifications/additions you are allowed to do here? And you may need to add more details about the current design.
 
manish ahuja
Ranch Hand
Posts: 312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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).

Hope this gives you a better picture. Thanks,
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!