Conversation with Dan: File a JIRA and I'll do my best this next week to get rid of the ugliness. I agree its weird and we shouldn't have to show this in the examples. It was a rush job when we were getting 2.0.0 out. Dan On Fri, Jun 20, 2008 at 5:34 PM, Andreas Guenther <andreas.guenther@mulesource.com> wrote: Dan, Is this a workaround or real feature then? How about we introduce a new and custom component in the echo example after all or modify the EchoComponent to solve the issues. It's a bit confusing otherwise to see two different interfaces used and a concrete implementation on apparently just one. I believe that a new concrete implementation of the example interface, let's call it EchoComponent, under examples would make the serviceClass attribute obsolete because it then can be used in a component element. Something like the following is what I would expect how it would work: <service name="EchoUMO"> <inbound> <cxf:inbound-endpoint address="http://localhost:65082/services/EchoUMO"/> </inbound> <!-- Implements org.mule.example.echoEcho interface --> <component class="org.mule.example.echo.EchoComponent"/> </service> Will the above work and is this how it's supposed to be or do we always have to specify the serviceClass (which apparently is an interface!) in the endpoint? Thanks, -Andreas Dan Diephouse wrote: If you look at the EchoComponent it has a bunch of extra methods. CXF was picking up those methods, so I created a service class that is used to construct the WSDL which didn't have those methods. I believe Axis is having similar issues; see this issue from Angelo: http://mule.mulesource.org/jira/browse/MULE-3295 Regards, Dan On Fri, Jun 20, 2008 at 12:51 AM, Andreas Guenther <andreas.guenther@mulesource.com <andreas.guenther@mulesource.com>> wrote: I am wondering why two components are specified in the echo-example in 2.0, serviceClass attribute and echo-component element? Is this a CXF specific thing? -Andreas