One more comment:
There are a lot of things in CXF that won't work without the JAXB jar. I'm
not even sure if config parsing or wsdl parsing will work with JAXB. Thus,
you may not be able to get rid of jaxb anyway.
That said, if you use Java 6, it SHOULD work with the jaxb stuff built into
On Thu May 21 2009 4:00:44 am Stevo Slavić wrote:
> Hello CXF Users,
>
> Because of licensing issues when using JAXB, I have to switch to XMLBeans
> as data binding provider.
Interesting. CDDL is normally not a "bad" license.
> Before making a switch, are there any known
> limitations or
Hi,
I've opened https://issues.apache.org/jira/browse/CXF-2231
to log the progress on this.
On Wed, May 20, 2009 at 7:55 PM, Valerio Schiavoni <
valerio.schiav...@gmail.com> wrote:
> I activated even deeper logs, and here's the result, maybe it can help
> understand the problem by some cxf gu
After making the API call the client is returning the response, can see the
inbound message. however the response for some reason is not being read...
below is the thread dump
"P1T0" prio=1 tid=0x2c949a10 nid=0x4b48 runnable
[0x41261000..0x41262b40]
at java.net.Soc
On Thu May 21 2009 6:24:08 am Marc Logemann wrote:
> Dan,
>
> you are right, XercesImpl 2.6.2 was in the lib path, but in fact it
> was requested by CXF itself :-)
Might be an ivy bug then.
> XercesImpl is a requirement of Neethi which itself is required by cxf-
> api.
Not really. Neethi doe
In order to use the tooling with maven deps (ivy is more or less the
same), one has to declare:
rev="2.1.4" conf="default">
rev="2.1.4" conf="default">
Dan,
you are right, XercesImpl 2.6.2 was in the lib path, but in fact it
was requested by CXF itself :-)
XercesImpl is a requirement of Neethi which itself is required by cxf-
api.
Is there any reason that one needs an XML parser as requirement
nowadays? I mean, this or a similar parser
I tried with 2.1.5 and observed the same i.e. null being passed to the service
implementation.
As suggested, I have entered info on JIRA (bugID below).
WSDL2XML generated binding not passing correct method arguments in service
implementation
Hello CXF Users,
Because of licensing issues when using JAXB, I have to switch to XMLBeans as
data binding provider. Before making a switch, are there any known
limitations or issues this switch could bring (e.g. lack or limitted
functionality, security, etc.)? Also, is it known why it was decided
