Hi Florent, I agree that we cannot easily create shared JAX-WS code here. But if don't use this opportunity to think about the models and the APIs/SPIs we will never merge the code bases.
- Florian -----Original Message----- From: Florent Guillaume [mailto:[email protected]] Sent: Friday, February 26, 2010 11:36 AM To: chemistry-dev Subject: Re: Chemistry Web Services Binding Hi, I'd be glad if we could do it, but I don't see how, when talking about JAX-WS bindings. The JAX-WS bindings are basically mechanical code that has in each method: - convert from JAXB to internal model - call SPI method - convert back from internal model to JAXB Given that our SPI methods have different signatures and that we have different internal models, I don't see what we can put in common in our JAX-WS code. Regards, Florent 2010/2/26 Klevenz, Stephan <[email protected]>: > Hi, > > This is a really a great opportunity to start a code merger. One idea could > be to build out one common library that contains the webservices binding code > used by both projects. > > What do you think? > > Regards, > Stephan > > > -----Original Message----- > From: Florian Müller [mailto:[email protected]] > Sent: Freitag, 26. Februar 2010 10:05 > To: [email protected] > Subject: Chemistry Web Services Binding > > Hi Florent, > > I had a look at the Web Services binding code you checked in yesterday. It is > pretty similar to the OpenCMIS server approach. > Before you start re-implementing what's already there, wouldn't it be a good > time to look if and how we can merge the code bases? > > > - Florian > -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
