Great Mike, this is probably aligned with the discussions we are having for the 2.0 milestone release contents where ws binding would be part of it. I'm just not so sure about policy, after looking at it and from previous discussions, it looks like we might need great amount of work there.
On Fri, Dec 5, 2008 at 1:06 PM, Mike Edwards <[EMAIL PROTECTED]> wrote: > Raymond Feng wrote: >> >> Hi, >> I added host-http to get the implementation-node-runtime compiled. I >> agree with you that we should probably refactor the web application part out >> of implementation-node-runtime. >> I'm starting to clean up the interface models. The interface-wsdl-??? >> modules have quite a lot references to the base interface module. I added >> the interface-wsdl-??? to take advantage of the Eclipse refactoring >> capability. On the other hand, interface.wsdl is part of the SCA assembly >> model. I think it would be nice to bring it up for the first milestone of >> 2.0 release as Luciano has proposed. I'll give more details in that thread. >> Thanks, >> Raymond >> > Folks, > > I've been doing some work quietly to get the Web services related modules > working in Trunk > - not putting them into any main build or anything, but enough to get the > following running: > > <interface-wsdl/> > <binding.ws/> > > My reason for doing this is that I am building a testcase suite for the > OASIS Specifications and I need to drive them via an interoperable binding > (ie binding.sca will not do...). > > This has involved the following modules: > > binding-ws > binding-ws-axis2 > binding-ws-wsdlgen > binding-ws-xml > > databinding-axiom > databinding-jaxb-axiom > > node-impl > > policy > policy-security > policy-xml > policy-xml-ws > > xsd-xml > > So far, it is mostly a case of tweak, tweak, tweak, adjusting dependencies > and OSGi MANIFEST files, but in a few cases, the 2.0 APIs are different from > the 1.x APIs and some changes are needed - this often affects testcases more > than mainline module code. One lesson from this is that I think we should > consider creating a tests-utils module to contain some of the sequences that > tests seem to need commonly - and to hide the testcase code from changes in > the base platform. > > > Yours, Mike. > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
