Hi Dan,
Yes, If we expose too much detail to the user , it will be painful for
us when we are doing the refactoring stuff.
Current CXF Servlet refactoring just make the Servlet decouple with the
jaxws front end. In this way the servlet need to get to know which
publisher implementing could be used in the servlet.
We can take the publisher as the transport factory and load different
publisher by the namespace which is defined in the cxf-servlet.xml.
But we also need to write the servlet class name in Web.xml. Can we make
it parent to the user ?
Here is another thought that CXF Servlet also support create the service
by Spring configuration xml. I think we also need to make it
sophisticated to support different front-end.
Cheers,
Willem.
Daniel Kulp 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.
