Are the annotations for the WSDL documentation (and logging, .... of course)
intended for the use with the AEGIS binding as well? Or will it only work
with the JAXB binding?
We are generating our sources with AndroMDA, so another possibility is the
use of *.doc.xml files that were used by XFire, these files can easily be
generated ...
Additionally, it would be great to document all parts of the WSDL:
operations, parameters, types, type parameter, responses, exceptions ...
Cheers, Juergen
On Wed, 2008-06-18 at 11:17 -0400, Daniel Kulp wrote:
...
> 4) Extension via annotation - Benson and I have chatted about this off
> and on. Basically, we'd like to add hooks into the
> ReflectServiceFactoryBean so that registered listeners can get events
> about when things happen. Like when an interface is mapped to a
> ServiceInfo, a method is mapped to a OperaionInfo and
> BingingOperationInfo, etc... The listeners can then examine the
> Method object or Class object or whatever for any additional things
> it's interested in at runtime. This would allow for some custom
> annotations. Examples:
> Configure some logging:
> @Logging(in = "in.log", out = "out.log", fault = "<stderr>")
> Configure and IDL location for the corba binding:
> @IDLLocation("file:/foo.idl")
> Add documentation to the wsdl:
> @WSDLAnnotation("This operation does XXX")
> etc...
> Some of the stuff in the JAX-WS frontend could then be re-written to
> use that. Processing of the @WebServiceFeature annotations and stuff
> could be re-implemented that way. The main thing here is to make
> some of the java-first things work a bit better/easier. (our own
> @Features annotation could be deprecated in favor of explicit
> annotations for the features we have)
...
--
View this message in context:
http://www.nabble.com/Ideas-for-2.2-tp17985028p17998530.html
Sent from the cxf-dev mailing list archive at Nabble.com.
