On Wednesday 05 September 2007, Matt Hogstrom wrote: > Also, it is my understanding that the WebServices bindings should be > part of Java 6 and as such it would seem to make sense that they live > in Harmony as well. That said, the expertise in this area is mostly > in CXF. I'm not sure who the committers are on this portion of Yoko > so it would be great to gather some input from those folks as well.
My expectation is that Harmony would be using CXF (or Axis, though I obviously would prefer they use CXF since CXF is already standalone JAX-WS certified compliant) for the WebServices stuff they need. I don't see why they would write another webservices stack. Or are you suggesting that CXF also get merged into Harmony? Are we following Sun's lead and jamming all the projects into the JRE? That doesn't make sense to me. Also, the WebServices stuff Harmony needs definitely does NOT include a CORBA binding for the JAX-WS stuff. That isn't part of the specs they need. Thus, it really doesn't make sense to me to put that part there. The commiters that have contributed to the binding since Jan are: bravi dmiddlem enolan mvescovi - 2 commits to add a couple tests and 1 commit to fix a build failure rickmcguire - 3 commits related to mvn build things (release preps) dblevins - 1 commit related to continuum setup lkuehne - 1 commit to apply a patch from JIRA adc - just some maven build things If you add the tooling that goes with the binding (idl2wsdl, wsdl2idl), then mvescovi and lkuehne have a few more. (Note, there isn't a idlj tool, so your mention of that is relatively irrelevant. There is a start of a pre-processor in the tools module that would be the first part of a idlj, but that's it.) In anycase, from the bindings part, it would just be the 3 or 5 of them, depending on if they are interested or not. (we'd obviously give them a chance to opt-out if they want). -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
