Announcement Announcement Module
No announcement yet.
contract-first wsdl deployment issues Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • contract-first wsdl deployment issues

    I am trying to use XFire/Spring to do contract-first ws and I'm running into a few problems.

    First, I'm using the xsd:import in WSDL "best practice". I am using a JSR181 WebService wsdlLocation attribute to tell xfire where to get the WSDL when I ask for it with /services/WebServiceName?wsdl.

    The problem is that the xsd:import does not work because I guess it is trying to get it from /services/.

    Second, since I wrote my own WSDL, I don't want to use xfire's automatic WSDL generation (surprisingly, it doesn't look like the WSDL I used to generate the XML Binding classes).

    So the soap:address endpoint url is hard coded rather than being generated dynamically by the container. This presents some added difficulty when deploying to different platforms (dev/stg/prod).

    How do other people deal with this?

    It is enough to make me use the automatic wsdl generation feature of xfire. Even though it does not match the wsdl I created, it seems to work just fine with the JAXB classes that were generated.

    Thanks --Joachim