5 Replies Latest reply on Jun 24, 2008 8:20 AM by Alessio Soldano

    @WebServiceRef default name

    Alessio Soldano Master

      This is related to http://jira.jboss.com/jira/browse/JBMETA-64.

      Well, considering the api doc says the default name should be as is now in trunk, I was thinking it's probably better to close the issue as "won't fix" (thus changing the behavior we had in Beta4). On my side I would have changed the tests, in order not to use the default name (i.e. I'll always use the name attribute) to pass on both containers. My only concern now is that the old naming default was probably used to cope with cases of multiple class having different attribute annotated with @WebServiceRef with the same name:

      ...
      public class A
      {
      @WebServiceRef
      private ServiceOne prettyService;
      ...
      }


      ...
      public class B
      {
      @WebServiceRef
      private ServiceTwo prettyService;
      ...
      }


      What do you think about this Emanuel?