Announcement Announcement Module
Collapse
No announcement yet.
Using @RequestPayload without parameters Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Using @RequestPayload without parameters

    I'm using JaxB2 for marshalling/unmarshalling on the server and would like to take advantage of the new @RequestPayload to infer my endpoint method mappings.

    How does this work for requests which have no parameters, i.e. where I don;t have a generated JaxB2 class to marshal and therefore annotate. Ideally I would like to be able to map my endpoints without mixing mapping strategies.

    Also, what is there any special endpoint mapping configuration to enable this JaxB2 inferring? I haven't been able to find any documentation on this.

    Thanks

  • #2
    I think a little investigation of the latest trunk source has answered my own question.

    - The no-args services obviously have a response which can be annotated with @ResponsePayload which flags the service for inference.

    - The new org.springframework.ws.server.endpoint.mapping.jax b.XmlRootElementEndpointMapping is provided to trigger this JaxB endpoint mapping inferring

    Comment


    • #3
      Originally posted by strykker View Post
      I think a little investigation of the latest trunk source has answered my own question.

      - The no-args services obviously have a response which can be annotated with @ResponsePayload which flags the service for inference.

      - The new org.springframework.ws.server.endpoint.mapping.jax b.XmlRootElementEndpointMapping is provided to trigger this JaxB endpoint mapping inferring
      How does the XmlRootElementEndpointMapping trigger a JaxB endpoint if you don't have the JaxB-mapped classes yet?

      Comment


      • #4
        Originally posted by skram View Post
        How does the XmlRootElementEndpointMapping trigger a JaxB endpoint if you don't have the JaxB-mapped classes yet?
        I do have the jaxb-mapped classes generated. It just that some requests have no parameters - ie. no jaxb request class. In these cases though, there is always a jaxb response class, thust the discovery of the @ResponsePayload attribute.

        Comment


        • #5
          Originally posted by strykker View Post
          I do have the jaxb-mapped classes generated. It just that some requests have no parameters - ie. no jaxb request class. In these cases though, there is always a jaxb response class, thust the discovery of the @ResponsePayload attribute.
          That's good to know I thought you found a way not to generate any JaxB classes

          Comment

          Working...
          X