[
https://issues.apache.org/jira/browse/CXF-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506751
]
Jervis Liu commented on CXF-735:
--------------------------------
Note, the injection stuff does not work properly as well. Below is quoted from
Eoghan's email:
"
After an amount of head-banging-on-desk, I noticed that the
<jaxws:client> config isn't picked up via the non-specific
Service.getPort(), even when the actual port selected matches the bean
ID of the configured <jaxws:client>.
By the non-specific Service.getPort(), I mean the form of this API where
a specific port name is not provided explicitly by the app, instead the
Service impl handles the selection of an appropriate port.
This is easily seen by removing the @Ignore from the
ServiceImplTest.testNonSpecificGetPort() unit test that I just
committed.
This should this work, right? I mean, what does it matter if endpoint is
selected by the Service impl or specified explicitly by the app, either
way a matching <jaxws:client> bean should be wired in, or?
"
> javax.xml.ws.Service.getPort(java.lang.Class<T> serviceEndpointInterface)
> does not work
> ----------------------------------------------------------------------------------------
>
> Key: CXF-735
> URL: https://issues.apache.org/jira/browse/CXF-735
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Reporter: Jervis Liu
> Assignee: Jervis Liu
>
> javax.xml.ws.Service.getPort(java.lang.Class<T> serviceEndpointInterface)
> does not work, see test case:
> org.apache.cxf.jaxws.ServiceImplTest.testNonSpecificGetPort
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
