Hi Dan, Cheers for letting me know. I've got a workaround in my code for now so I'll be waiting for the snapshot or the 2.0.2 release. Thanks for looking into it for me,
Regards, Lee Dan Diephouse-2 wrote: > > Hi Lee, > > Looks like we got ourselves a bug. I've implemented a fix for this which > I'll commit today. To get this to work you can either wait for us to > publish a new snapshot (this weekend? we really need to automate this), > build CXF yourself, or try the 2.0.2 release which will probably happen > in two weeks. > > Cheers, > - Dan > > Lee Theobald wrote: >> A bit of a bump to this topic as I'm still having issues. I'm trying >> things >> like below: >> >> <!-- Service endpoint --> >> <jaxws:endpoint id="searchlogger" >> implementor="com.oobjects.logging.SearchLogger" >> address="/SearchLogger"> >> <jaxws:properties> >> <entry >> key="com.oobjects.logging.tables.ILogEntry.implementation" >> value="com.oobjects.logging.tables.LogEntry"/> >> <entry >> key="com.oobjects.logging.tables.IPathWalker.implementation" >> value="com.oobjects.logging.tables.PathWalker"/> >> </jaxws:properties> >> <jaxws:serviceFactory> >> <ref bean="serviceFactory" /> >> </jaxws:serviceFactory> >> </jaxws:endpoint> >> >> This hasn't worked though. I'm still getting proxy objects though. >> Anyone >> out there got any ideas on how I can add these implementing classes? >> > > > -- > Dan Diephouse > MuleSource > http://mulesource.com | http://netzooid.com/blog > > > > -- View this message in context: http://www.nabble.com/Aegis%2C-Proxies---Interfaces-tf4297824.html#a12458267 Sent from the cxf-user mailing list archive at Nabble.com.
