We could leverage Spring here if we wnated to. I'm in the midst of writing a Spring 2.0 handlers so we can handle things like:
<beans ...> <jaxws:endpoint implementor="foo.bar.MyEndpoint"/> </beans> If we didn't want to be dependent on the Spring syntax, we could write a simple transformation that takes something like this format and converts it into Spring format: <endpoints> <endpoint implementor="foo.bar.MyEndpoint"/> </endpoint> Or whatever our current syntax is :-) - Dan On 2/4/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
On Sunday 04 February 2007 20:27, Willem Jiang wrote: > 2. cxf-servlet.xml > Adding a publisher attribute in the endpoint element. > It should be publisher="org.apache.cxf.jaxws.EndpointPublisherImpl" > > You can find the example from the systest or the kit's samples hello_world > . Please feel free to get touch with me if you have any issue about the > CXF Servlet. I really don't like this part of this. You end up forcing people to embed internal class names into the XML file and thus know internal details about the implementations. It also prevents us from refactoring things, renaming classes, etc... without breaking the users apps. This needs to change to some sort of registry system where the frontends can register a handler to the servlet/bus and the XML just has some sort of key for the XML. I'd prefer a namespace qualified thing where the frontend could provide an entire schema for their section of the XML. If the frontend needs some additional elements in the XML file, they can do it. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED]
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
