All-- I've been doing a bit of digging into Axis to look at how we're wiring up an Axis SOAPService from an annotated Java file. The process basically works like this:
build-time: - check annotations - generate JavaBean model of the service - serialize JavaBean model into .ser files available in an application's classloader runtime: - load .ser files and convert into JavaBeans - convert JavaBean model into a SOAPService - load SOAPService into Axis While this generally works, Axis already has the .wsdd mechanism for being able to define the "shape" of a service from an annotated Java source file. WSM could simply generate the .wsdd files at build time and then those files would contain the operations, parameters, type serializer / deserializers, etc that are needed to execute a service in Axis. Seems like this would be simpler than a lot of the code that exists today to convert a .ser JavaBean into a SOAPService. It doesn't provide a quick iterative development experience, but personally, I'm more concerned with obtaining JSR-181 compliance and adding features second. We need to ship this thing. ;) Thoughts? Dims / Ias, know of any reason why this wouldn't work? Thanks for any input. Eddie
