[
https://issues.apache.org/activemq/browse/CAMEL-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48956#action_48956
]
William Tam commented on CAMEL-1254:
------------------------------------
@Charles
I think that is the case. That's one of the reasons I suspect in
most usecase, users are better off spelling out the service endpoint
interface class. Other edge cases includes bean object being a
proxy. Willem addressed the case that the bean is a Spring AOP proxy
but we don't handle other type of proxies.
On Mon, Jan 26, 2009 at 10:55 AM, Charles Moulliard (JIRA)
> camel-cxf: URI option for serviceClass does not support lookup in registry
> --------------------------------------------------------------------------
>
> Key: CAMEL-1254
> URL: https://issues.apache.org/activemq/browse/CAMEL-1254
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 1.5.0
> Reporter: Claus Ibsen
> Assignee: William Tam
> Priority: Minor
>
> Having an endpoint such as:
> {code}
> String cxfEndpoint =
> "cxf://http://localhost:8080/part-five/webservices/incident"
> +
> "?serviceClass=org.apache.camel.example.reportincident.ReportIncidentEndpoint"
> + "&wsdlURL=report_incident.wsdl";
> {code}
> The serviceClass option currently only supports defining a FQN for the class.
> I think we need to support Registry lookup as well using the # notation. So
> you can do:
> {code}
> String cxfEndpoint =
> "cxf://http://localhost:8080/part-five/webservices/incident"
> + "?serviceClass=#reportService"
> + "&wsdlURL=report_incident.wsdl";
> {code}
> And then have it defined in Spring XML:
> {code}
> <bean id="reportService" class="...">
> {code}
> The # notation is already supported if you use the cxf Spring XML
> configuration. We need this in the Java DSL as well.
> Sorry if it already exists. But I got a hint from a Camel end user that it
> didn't
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.