>
> I wonder if the harness can scan all the server source files, look for
> handlers (they extend from a known classes, right?), then generate
> necessary pieces.
But there's nothing in the handler code that says how/where it's used.
The same handler could be used multiple times in more than one handler
list for the same service (e.g., in different ports, or in a list
depending on what binding is being used, etc.). It's really the xml
descriptor that we need to do this. In the fromjava case, it could be
simple at least since the service impl class will have an annotation
pointing to the file.
Cheers,
Bobby