Doh! Thats not very helpful - CXF depends on JAX-WS, so same problems there.
Looks like Apache Axis is AP2 licensed, but I really dont like Axis at all. Any
ideas?
Cheers, Tim
On 22 Dec 2009, at 01:04, Ross Mellgren wrote:
Looks like JAX-WS reference implementation is dual licensed CDDL or
It's been said ;-)
At work, I wrote our SOAP integration because as much pain as SOAP is,
it's less pain that SOAP + SOAP library, especially Axis (at least at
the time, when Axis2 was not out). To this day the only place we use a
SOAP library (Axis1, in a client) is broken due to bugs in
Sure, JAXB... im using JAX-WS heavily at work in one of my scala frameworks
that I wrote for working with a product API... on the whole, its pretty sweet
with the scala sugar and im bummed that the licensing is not helping us out on
this front.
Cheers, Tim
On 22 Dec 2009, at 16:46, Ross
Cool - I'll have a play overthe hols.
It's a SOAP api so I'd need to depend on CXF or JAXWS... Do you forsee
any license conflicts before I start work?
Cheers, Tim
On Dec 21, 6:58 pm, David Pollak feeder.of.the.be...@gmail.com
wrote:
On Sun, Dec 20, 2009 at 2:42 PM, Timothy Perrett
On Mon, Dec 21, 2009 at 4:28 PM, Timothy Perrett timo...@getintheloop.euwrote:
Cool - I'll have a play overthe hols.
It's a SOAP api so I'd need to depend on CXF or JAXWS... Do you forsee
any license conflicts before I start work?
As long as those libraries are Apache 2 or MIT/BSD licenses,
Looks like JAX-WS reference implementation is dual licensed CDDL or GPLv2.
-Ross
On Dec 21, 2009, at 7:32 PM, David Pollak wrote:
On Mon, Dec 21, 2009 at 4:28 PM, Timothy Perrett timo...@getintheloop.eu
wrote:
Cool - I'll have a play overthe hols.
It's a SOAP api so I'd need to
