Petals BC SOAP

Fix in branch petals-entreprise-3.1.x

To merge in trunk

The library isn't duplicate in trunk

bad copy/cut isn't StAX API but mail API -> StAX API is for http://jira.petalslink.com/browse/PETALSBCSOAP-90 issue

Into the trunk geronimo library has been replaced by javax.mail -> mail-1.4.4.jar because javax.mail was already taken

Who stated that we should prefer Apache licence to CDDL ? As far as I remember, Laurent said there was no problem with CDDL, and personally I would rather thrust Sun more than Apache to implement their spec correctly.

Thus, Could you elaborate on your "prefer Apache licence instead of CDDL".

Each SUN licence must be checked to be sure that we are authorized to redistribute the SUN artifact. If the SUN licence does not include the "Classpath exception" we can'nt distribute the artifact. That's why I prefer Apache licence than SUN licence.

This mention is necessary to be compliant with GPL v2.0.
AFAIK, this is not the license under which petals is distributed... These questions are not necessarily simple. No offense but I prefer relying on Laurent on this. I'll ask him to comment on the issue this afternoon.

Hi all.
Marc told me about this discussion, which is about a library that is dynamically linked to Petals at runtime, if I don't misunderstand.
In the CDDL, the point 3.5 allows distribution of executable form under any license, as long as user's rights on the library (code and executable) stay unharmed. As the LGPL is also an open source license, rights are kept.
Also, the definition of "covered software" clearly restricts its scope to reuse or modification of code ("files that contain"), so a plain runtime link has good chances to fall outside this scope (although no legal document/court decision decided this once and for all yet).
On the LGPL side, the article 6 permits the distribution of such a package (Petals + third party software) in executable form, under terms of our choice, as long as existing user rights are kept.

I found this page, that told that most source code was under CDDL and/or GPLv2 with CLasspat. But this source didn't seem very reliable.

I then checked the Oracle Development License which tells that it doesn't limit the rights granted under and open source license. I downloaded the component (javamail-1.4.4.jar), checked the license of every component, all were plain CDDL (except dsn.jar which had no license.txt).

So, unless I missed something, I don't see any incompatibility of linking this library with Petals.

Thank Laurent, therefore we don't need to change anything ?