Results 1 to 2 of 2

Thread: Spring web services version implemnetation approach

  1. #1
    Join Date
    Oct 2011
    Posts
    1

    Default Spring web services version implemnetation approach

    Hi,

    I have a requirement to maintain the different versions of particular web service.There is a chanse of having multiple versions(unbounded) for single web service. I have read in spring documentation recommending to implment PayloadTransformingInterceptor, which will based on xslt transformations.

    How can we implement to transform the multiple versions of old messsages to new messages For ex:- we have the following versions
    1) V1.0
    2) V1.1
    3) V1.2
    4) V1.3
    Here the question is, Do i need to have xslt file for each version? If that is case where should register the xslt files per each version.
    We are prefering message transaformations using JAXB. Is there any other solution to implement versioning using JAXB objects?

    Sydaiah N

  2. #2

    Default

    You cann add an interceptor to do the xslt transformation. We have tried it. It is a pain to write/debug...

    A more easy way to do it is to create a new webservice for the new version.

    Precise that OldWebService is depretaced in V2 should be used. So the old one still exist with the new version.
    But if your boss think that XSLT Transformation is THE THING todo do because Uncle ExpertOFTheDay tell him that it is the case, tell him to write it


    Omar EL Mandour
    Need help on Spring WS ? Do you want to shift gears and build the architecture of your spring ws with half of the price that will be for your company ? I have worked on Spring Ws 1,5 year at full time and build around80 WS with full dao testing and integration tests with Soapui with Maven 2 on hudson

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •