Daniel Kulp <[EMAIL PROTECTED]> writes: > The last option would be to make the "Destination" stuff in http > plugable. The jetty stuff just provides a HttpDestinationProvider > or something into the http module. Jetty wouldn't subclass the http > factory or anything. It just provides functionality into the > existing http one. > > Any thoughts?
Without grasping too well what all these entities are, being too new to CXF, this last option still sounds like the best solution with the least coupling. I take it "destinations" are related to listening endpoints, or servers? If I'm writing a client, and I have no server-style behavior, then I should be able to use the HTTP module and have all I need. If the Jetty module wants to reuse or plug in to parts of the HTTP module, that's fine; one could combine the two of them or not, just like any other layered and dependent modules. -- Steven E. Harris
