Ok so from list in the WS binding next steps thread, we've already now done (4) and (6) and have someone looking at (5). It sounds like everyone agrees we should look at (7) but thats going to require mostly work by the core runtime people (though I'd like to be involved). So that leaves the most pressing things being (1), (2), and (3). I've already got the same (1), (2), and (3) to do for the JavaScript component so is anyone prepared to volunteer to at least starting to look at one of these exciting tasks? Rick? Raymond? Would you take (1) or (3) and we could all take JIRA's in (2) as they get raised and we have time?
The list of items was: >> 1) Documentation. At very least something simple explaining how components >> use externalServices to call remote services and how to use entryPoints >> expose components as Web service endpoints. >> >> 2) Fix bugs. There's a few JIRA's already, sure we can find some more if >> we play around using the axis binding. >> >> 3) Clean up the code and flesh out the tests. >> >> 4) Correctly configure the AxisService in ExternalWebServiceClient. As the >> TODO in the code says and several people have already commented, on this >> should not use the axis.xml but be configured programatically. The >> requires moving up from Axis2 0.94. >> >> 5) Java2WSDL tooling using the Axis2 tools. Also requires moving up from >> Axis2 0.94. >> >> 6) Move up to a later release from Axis2 0.94 to get several fixes and to >> support the last two items. >> >> 7) Support efficient (de)serilization and streaming between >> components/services. Ideally i'd like to be able to wire up a WS entryPoint >> to an externalService or e4x component and have the SOAP body pulled >> directly from the incoming StaX stream. >> >> 8) Policy. Once (4) and (5) are done it should be possible to use a WSDL >> with policy on an externalService and have things like WS-Security >> automatically configured by Axis2, so investigate this and see what can be >> done on the entryPoint. >> >> 9) look at using alternative WS impls to Axis2? XFIRE's just had a 1.0release, or JAX-WS? Maybe not a high priority but i'm sure we could learn >> things from trying this. 10) Support invoking simple rpc encoded remote services. Not proper rpc-enc support but tuscany working for things like xmethods stockquote which i'm sure lots of new users will try. Currently SDO barfs on the WSDL but if it could tolerate it those simple services often work even if the soap message doesn't have the xsi type stuff. 11) Open our data binding implementation and integrate it with the Axis2 data binding story. Currently our serialization/de-serialization code assumes SDO DataObjects. Application developers will also want to be able to use plain JavaBeans, Axis2 generated beans etc. On 3/23/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > ant elder wrote: > > Are there any _specific_ items people could suggest to improve the WS > > support for this upcoming release? The next steps thread from a while > back > > was pretty quiet. > > > > Axis2 already supports most things and interop's well so its 'just' a > mater > > of integration with Tuscany. Attachments? raw doc style? headers? > > rpc/encoded? WS-X? Whats important to you? > > > > ...ant > > > > On 3/22/06, Jim Marino <[EMAIL PROTECTED]> wrote: > > > >> That's great. Perhaps we could look at that as part of the Axis > >> "cleanup work" which needs to be done? > >> > >> Jim > >> > >> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote: > >> > >> > >>> Jim, > >>> > >>> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM > >>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with > >>> Indigo/WCF). > >>> > >>> thanks, > >>> dims > >>> > >>> On 3/22/06, Daniel Kulp <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> Jim, > >>>> > >>>> > >>>> > >>>>> 4. Additional bindings to Axis through integration with Celtix, > >>>>> particularly ws and JMS > >>>>> - Basic integration (p1) > >>>>> - Ability to retarget (p2) > >>>>> - Dan, would Celtix get us Indigo interop? > >>>>> > >>>>> > >>>> Good question regarding the Indigo stuff. We do have Indigo > >>>> interop on > >>>> the roadmap, but I don't know the complete timetable or what that > >>>> really > >>>> means (since I know nothing about Indigo). > >>>> > >>>> That said, post milestone 5 of Celtix (next week), we have someone > >>>> that > >>>> will be doing some interop testing using Celtix with Indigo to > >>>> test the > >>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability. > >>>> Obviously, > >>>> until the results of those tests come in, I don't know how far > >>>> away we > >>>> are. > >>>> > >>>> -- > >>>> J. Daniel Kulp > >>>> Principal Engineer > >>>> IONA > >>>> P: 781-902-8727 C: 508-380-7194 > >>>> [EMAIL PROTECTED] > >>>> > >>>> > >>>> > >>> -- > >>> Davanum Srinivas : http://wso2.com/blogs/ > >>> > >>> > >> > > > > > Ant, > > When I proposed to "improve our web services support" for JavaOne > earlier in this thread I was actually thinking about your list of 10 > TODOs + the 11th I had suggested in this thread: > > http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200603.mbox/[EMAIL > PROTECTED] > > Reading your list again, it maps pretty well to the priorities I had in > mind: Doc, bug fixing and more testing would be the highest priority, > RPC encoded the lowest. If you agree I would like to place my 11th item > "pluggable databindings" around the 7th position just before > (de)serialization optimizations. > > I think that your items (2) and (3) will help grow the todo list, I'm > pretty sure that once you start playing around with the WS binding > you'll find limitations and bugs that you'll want to fix :) > In particular I think we should look at the following areas: > - pure doc vs doc-wrapped, have we tested anything else than doc-wrapped > with one parameter? I'm sure that if you try various combinations you'll > find enough to get busy until JavaOne :) > - inline XSDs vs imported XSDs plus various combinations of WSDL imports > - get the WS binding to work with some of the test suites available out > there (at http://www.whitemesa.net/ and http://www.mssoapinterop.org/ > for example). > > -- > Jean-Sebastien > >
