Hi Ivan,
If you want to contribute any changes, open an improvement issue in JIRA
[1] and attach your code to this issue. We will review, discuss and, if
applicable, merge it into the OpenCMIS code.
- Florian
[1] https://issues.apache.org/jira/browse/CMIS
I wouldn't be so sure that relative URLs work with all Web Services stacks.
The servlet can be coded to process URLs from commons instead of
placeholders from templates
I don't have the time or the requirement to support or test other stacks.
But this is an open source project and contributions are welcome.
How to contribute properly is subject for this email thread.
If contribution will eliminate wsdl templates and will push wsdl's/xsd's
into maven and then use maven repo to fill out war for bindings, would this
approach be fine?
Regards,
Ivan
2013/7/3 Florian Müller<[email protected]>
Hi Ivan,
I wouldn't be so sure that relative URLs work with all Web Services
stacks. There are many programming languages with dodgy stacks out there.
JAX-WS stacks are not a good benchmark because they are popular and
therefore have been adapted to many scenarios. That's not the case for many
less popular stacks.
But you are right. The OpenCMIS server framework has not been written for
Axis. It has written for the Metro stack. And all the template files are
necessary to bypass issues with this stack and wouldn't be necessary for
other stacks. (The Metro stack is not able to generate two different WSDLs
for the same service [same = same namespace and name] in the same web
application. Now the CMIS web services servlet generates the WSDLs instead.)
And I agree it would be great to have support for all other JAX-WS stacks.
Unfortunately, all stacks need some sort of proprietary tweaking. Some need
more and some need less.
I don't have the time or the requirement to support or test other stacks.
But this is an open source project and contributions are welcome.
- Florian
