On 1/4/06, Jongjin Choi <[EMAIL PROTECTED]> wrote: > Hi, Eddie. > > On 1/5/06, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > Sanjiva-- > > > > On 1/4/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > > Hi Eddie, > > > > > > > The near term goal is to ship a WSM 1.0 that has passed the JSR-181 > > > > TCK and then start adding additional features like: > > > > > > > > - supporting web service runtime specific annotations for type > > > > mapping, message buffering, configuration, etc > > > > - generating JAX-RPC source artifacts > > > > - drop-in deployment > > > > - Axis2 support > > > > - etc. > > > > > > Excellent! > > What do you mean 'message buffering'?
Good point -- a somewhat esoteric term. Specifically, this could be metadata that declares a service operation as asynchronous. Something similar is descrbed in Section 1.5.1 of the SCA client programming model specification. > > > > > > > > For the folks working on the jaxws module, any chance that you'd be > > > > interested in reusing the annotation processing infrastructure that > > > > we've built? > > > > > > +1, but, um, do u force XMLBeans support on anyone using the annotation > > > stuff u guys have done? Sorry I haven't looked at what's there so > > > apologies if its a dumb question. If you do that's bad from Axis2's POV > > > because we're very strictly data binding agnostic. > > > > Absolutely not. :) XMLBeans is one of the types that is (partially) > > supported, but it is by no means required. Developers should be able > > to use generated Axis types, JavaBeans, etc for data binding. > > > > We do have a binary dependency on XMLBeans for WSDL parsing when in > > top-down web service development using a prototype tool called > > "wsdl2ajava" for converting WSDL to an annotated Java file. But, I'm > > planning on switching this to wsdl4j and make the XMLBeans JAR > > *entirely* optional. > > > > It's good to remove the dependency of xmlbeans from wsdl2ajava. Agreed. :) Should have this done when WSM goes 1.0-final. > > > > > > > > Also would be great to have some Axis community feedback on what we > > > > have currently built and any input / patches to take it forward. :) > > > > If needed, I'd be happy to cut a milestone release and add it to Maven > > > > to make it easier to get started building annotated web services. > > > > > > We're working hard to get the base system completed and at or near 1.0 > > > status ASAP. So I'd say this'll have to come after that .. we're not > > > targeting SAAJ and JAX-WS support in 1.0 - that'll come ASAP after that. > > > (SAAJ may be ready but basically its not a requirement for 1.0 .. so if > > > its ready it'll ship but if not it won't!) > > > > > > > No problem -- just wanted Axis users to be aware of the existence of > > our project. Since it's not hosted under ws.apache.org, it's not as > > discoverable. Would be happy to contribute to the evolution of Axis2 > > post 1.0 with annotation processing infrastructure for 181, JAX-WS, > > etc. Will keep watch over this. > > > > Would also welcome any feedback on what we've got today for Axis 1.x > > from anyone who's interested. > > > > Eddie > > > > > Sanjiva. > > > > AFAIK, JAX-WS includes JSR-181 annotations. An JAX-WS implementation > will support JSR-181 as well. I don't know it is possbile (or > desirable) to mix JAX-WS impl (without JSR-181) from one project and > JSR-181 impl from other project into one stack. I'm not terribly familiar with JAX-WS, so I need to educate myself more before spouting off too much. :) That being said, if both JAX-WS and JSR-181 need to check similar annotations at build time and / or at runtime, one metadata processing infrastructure could be useful. It's not as big of a dependency as it seems -- mostly just about feeding some metadata (from Java 5 annotations, Javadoc metadata, WSDL, etc) and a service implementation into a system and producing a wiring a service. But, again, I need more education. :) > > Anyway, I think annotation framework of Beehive will help JAX-WS impl of > Axis2. > Definitely. I'm looking forward to seeing how that goes. > Thanks. > > /Jongjin >
