XFire

@SOAPBinding isn't checked on the endpointInterface if one is given

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.2-RC
  • Fix Version/s: 1.2
  • Component/s: Annotations
  • Labels:
    None
  • Number of attachments :
    0

Description

In the method AnnotationServiceFactory.create(Class, String, String, Map), the code that checks if a SOAPBinding annotation exists (and sets the style and use properties accordingly) doesn't look for the annotation in the endpointInterface.

A solution would be to move the code below the part that sets the endpoint interface to either the supplied class or that class' @WebService.endpointInterface annotation and do the check on that class instead.

A workaround is to put the @SOAPBinding on the implementation, but that is illegal according to the spec.

Activity

Hide
Dan Diephouse added a comment -

It seems you are right. I must have misread the spec the first time down.

This seems really odd as an interface really corresponds to the port type of the web service, so it doesn't make sense to put the SoapBinding annotation there. How I hate JSR 181

Show
Dan Diephouse added a comment - It seems you are right. I must have misread the spec the first time down. This seems really odd as an interface really corresponds to the port type of the web service, so it doesn't make sense to put the SoapBinding annotation there. How I hate JSR 181
Hide
Dan Diephouse added a comment -

I've just committed fixes to this in SVN. Thanks a lot Olof!

Show
Dan Diephouse added a comment - I've just committed fixes to this in SVN. Thanks a lot Olof!

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: