[ 
https://issues.apache.org/jira/browse/GERONIMO-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim McConnell updated GERONIMO-3006:
------------------------------------

    Attachment: GERONIMO-3006.patch

Added code to definitively distinquish between the two usages of @WebServiceRef 
annotation such that the proper DD tags are generated: 

1) To declare a generated service class, and 
2) To specify an SEI


> WebServiceRef injection ignored .value attribute
> ------------------------------------------------
>
>                 Key: GERONIMO-3006
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3006
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: webservices
>            Reporter: Jarek Gawor
>         Assigned To: Tim McConnell
>         Attachments: GERONIMO-3006.patch
>
>
> WebServiceRef annotation can be defined as the following:
> @WebServiceRef(name="accounting", 
>                                  value=AccountingService.class)
> AccountingPortType foo;
> or
> @WebServiceRef(name="accounting"
>                                   AccountingService.class)
> AccountingPortType foo;
> Currently, the above annotations will result in the following error message:
> AccountingPortType does not extend javax.xml.rpc.Service or 
> javax.xml.ws.Service
>         at 
> org.apache.geronimo.naming.deployment.SwitchingServiceRefBuilder.buildNaming(SwitchingServiceRefBuilder.java:130)
> Which looks like the WebServiceRef.value is ignored and the service-ref is 
> created incorrectly (service-interface should be set to AccountingService 
> class and service-ref-type should be set to AccountingPortType  class)
> Section 4.2.2 in JSR 109 to see how exactly the WebServiceRef annotation 
> attributes are translated into the DD. Also, section 7.9 in JAXWS 2.0 might 
> be helpful.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to