Thanks, Daniel.
I tried 2.2.5 and it fails the same way. I had originally chosen 2.1.8
because the war size was 4MB smaller but neither works. (Incidentally,
is there a standard cxf guideline for the minimum runtime dependencies
needed merely to run generated code on the client side?)
The jaxb-
I find this problem in cxf2.2.5 when executing quartz's multithread.How to
avoid it?
Caused by: java.util.ConcurrentModificationException
at
java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
at java.util.AbstractList$Itr.remove(AbstractList.java:357)
I'm just trying to jump in with zero experience with CXF on websphere
and keep getting a java.lang.VerifyError when Spring tries to
instantiate org.apache.cxf.wsdl11.WSDLManagerImpl during a ?wsdl
request.
I've tried putting some of the jars into the ext-folder as prescribed,
but nothing has he
Thank you Daniel,
I was afraid there would be issues. Unfortunately the FAQ doesn't explain how
to do make the client calls threadsafe when using Spring.
I took a stab at combining your reply with the FAQ instructions and how I
currently make CXF service calls with Spring. Could you (or an
Just curious I know we chatted on IRC about this and you were thinking
about logging a JIRA with a patch. Were you ever able to get a patch
created? Anything I can do to help?
Dan
On Mon January 4 2010 11:22:06 pm James Carr wrote:
> Hi All,
>
> There's an abstract attribute on the
Just for completion on this list.
With 2.2.5 and 2.2.6, if you change the wrapper class to use getter/setter
methods and annotate the getter instead of using a public field, it should
work. I've fixed the issues for using the field on trunk, but that won't
make it until 2.2.7.
Also, the
I'd probably need to see a small example and the wsdl and such. Probably
would need to see the Rental class as well, at least any class level
annotations that are on it.
One common things that would cause this is if the Rental class has an
@XmlRootElement annotation, but not and @XmlType anno
Thanks, Daniel.
The first one was indeed the issue. I can't get this customer to modify their
response output (which they hand-code). So I ended up creating an
in-interceptor that modifies the XML doc and then reinserts it. Ugly but but
works.
Thanks!
Henk
On Jan 20, 2010, at 1:02 PM, Daniel
As Sergey alluded to, if the interceptors are configured on the Bus, they will
be applied to EVERYTHING in the Bus. Those interceptors generally have to be
a bit more generic so that they can apply to REST and SOAP endpoints and such.
Soap specific things should probably be configured on t
Two thoughts:
1) Technically, that soap message would be invalid:
that element is not namespace qualified and per soap spec, all direct
children of the soap:Body should be namespace qualified. That alone may be
the issue.
2) Try turning on schema validation:
((BindingProvider)proxy)
See the faq:
http://cxf.apache.org/faq.html
Basically, if you use the request context, you could have issues if you don't
set the request context to be thread local.
Dan
On Wed January 20 2010 12:49:22 pm Bruno Melloni wrote:
> The approach of relying on Spring to get the CXF client object
I hate to say this, but you are probably hitting:
https://issues.apache.org/jira/browse/CXF-183
which is one of the oldest open feature requests we have.:-(
This is probably going to be more possible with CXF 2.3 as the soap over tcp
spec gives us a jms: url format that can be used for the
If you can, try with 2.2.6:
The Maven staging area is at:
https://repository.apache.org/content/repositories/orgapachecxf-057/
The distributions are in:
https://repository.apache.org/content/repositories/orgapachecxf-057/org/apache/cxf/apache-
cxf/2.2.6
I'm HOPING this is fixed as a bunch of c
On Wed January 20 2010 11:41:08 am Steve Cohen wrote:
> A CXF-based client that worked under cxf 2.0.7 fails when it is built
> under cxf 2.1.8 with IllegalAnnotationExceptions.
First off, if updating, I definitely suggest going to 2.2.5 (or 2.2.6 on
Monday).2.1.9 which will be released by Mo
Thanks for info on that. Never dreamed of the fact that even without using
OSGi, i am getting problems with it :-) Seems one cant escape this topic ...
hehe.
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 20.01.2010 um 21:05 schrieb Daniel Kulp:
>
>
> Most li
Most likely, it has something to do with the newer versions of XmlSchema that
we now use being OSGi bundles.Those specs jars are also osgi bundles. It
looks like ivy is putting anything that looks like OSGi bundles in a separate
location.
Dan
On Wed January 20 2010 3:02:42 pm Marc Lo
One following up.
The type of these 3 Jars is not "JAR" but "BUNDLE". And i am placing the jars
in different directories according to the type. This also lets me differenciate
between SOURCE jars. Now it seems i must also watch out for "BUNDLE" jars.
Whatever these are
---
regards
Marc Log
BOY! Got it!
This one was weird.
You are right. its an ivy issue but something that seems new in the POM
structure starting somewhere after 2.1.4
TheXmlSchema-1.4.5.jar was picked up but its placed in a different directory
(on the client) than all my other jars. Its in a "bundles" directory.
cxf-rt-frontend-jaxws has a direct dependency on cxf-api which has a direct
dependency on XmlSchema.
cxf-common-utilities also has a direct dependency on XmlSchema. cxf-api has
a dependency on cxf-common-utilities so it should be picked up that way as
well.
Dan
On Wed January 20 2010
Hi,
bug in ivy? Hmmm. A bug that only arrives when using CXF deps greater version
2.1.4 ? ;-)
I added your snapshot CXF repository to my NEXUS installation and used 2.2.6
for testing.
Results:
- i dont get the wstx-asl not found issue -> this is good but this also wasnt
the case in 2.2.5, o
Hi Dan, Sergey,
I added the Interceptors, but it's still not working. Here's my
implementation:
first I added the interceptors:
I applied it in my endpoint config:
The approach of relying on Spring to get the CXF client object from the context
is so convenient that I rarely think much about it.
But I find myself needing to call the client from several concurrent threads
and I am not sure but I believe that when I call context.getBean() I am
retrieving a
On Wed January 20 2010 11:38:43 am Marc Logemann wrote:
> some more investigation:
>
> In version 2.1.4, everything was ok and the XmlSchema.jar was resolved
> automaticly. With 2.2.5 this is no longer the case. I wanted to try 2.2.4
> or 2.2.3 to see when things have changed but with other 2.2.
On Tue January 19 2010 5:16:43 pm easternwahoo wrote:
> I am writing a justification for use of CXF at my company, and I need to
> list any commercial companies that are using it. I've searched the Apache
> CXF site and the FuseSource site. The only company I found was Sabre, but
> they use the
Hi
Hello Sergey,
Thank you very much for response.
I am using SoapUI-3.0.1 for generating the client stubs. I am generating
client stubs for restful web services using DOSGI. I found that, with DOSGI
grammer tag is empty in wadl.
The grammar section will only be generated if the response or
A CXF-based client that worked under cxf 2.0.7 fails when it is built
under cxf 2.1.8 with IllegalAnnotationExceptions.
The code generated from the wsdl seems identical so that's not the
problem. All of the elements defined in the generated source as
JAXBElements have the problem. Those defined
some more investigation:
In version 2.1.4, everything was ok and the XmlSchema.jar was resolved
automaticly. With 2.2.5 this is no longer the case. I wanted to try 2.2.4 or
2.2.3 to see when things have changed but with other 2.2.x versions i am
getting wstx-asl-3.2.8.jar issues with the maven2
I am using 2.2.5. The weird thing is, if I read one stream in and
close it before the other, everything works fine. If I read the other
one in first, it throws an exception.
With this code:
http://gist.github.com/281463
reading the attachments in in this order works perfectly fine:
byte[] dbf =
Yes. Someone passed a URL without the ?wsdl to a client constructor
that wanted the WSDL.
On Wed, Jan 20, 2010 at 7:32 AM, Sergey Beryozkin wrote:
> Can it be that the client is attempting to get a WSDL but no WSDL has not
> been found yet, that is the CXF QueryHandler handling ?wsdl requests wa
Hello Sergey,
Thank you very much for response.
I am using SoapUI-3.0.1 for generating the client stubs. I am generating
client stubs for restful web services using DOSGI. I found that, with DOSGI
grammer tag is empty in wadl.
I tried to use tomcat for deployment and write below code:
Servlet
Can it be that the client is attempting to get a WSDL but no WSDL has not been found yet, that is the CXF QueryHandler handling
?wsdl requests was not able to satisfy a ?wsdl query and allowed the request to continue ?
Though may be they use some clients that do SOAP GETs (thus ignoring the
bind
I just delivered a CXF service to a customer. They created a client
with something (I don't know, yet, what), and tried to use it.
Bad things happen:
org.apache.cxf.interceptor.Fault: No such operation: (HTTP GET
PATH_INFO: /rex-ws/Extraction)
Now, the service's parameters are pretty simple, so
On 01/19/2010 11:04 PM, Dale Ogilvie wrote:
Does Redhat/Jboss count?
http://press.redhat.com/2009/03/25/red-hat-adds-muscle-to-apache-cxf/
Hmm, you need to read that page a bit more carefully before you start
making claims you cannot substantiate. It states that JBoss
_contributes_ to the C
Hi guys,
I have a question: how WS-Addressing feature is implemented in CXF in
conjuction with JMS transport for SOAP?
Especially I'm interesting about using of wsa:ReplyTo to specifying
destination for SOAP response.
It seems that wsa is ignored in case of JMS and only JMS headers are used.
But
In TomTom we use it for creating internal rest web services.
On Wed, Jan 20, 2010 at 10:41 AM, Cyrille Le Clerc wrote:
>Hello,
>
>One of the three big French telecommunications operator use CXF for
> its portal, one of the ten biggest French web portals.
>
> Sorry, I can't name it :-)
>
Hi,
after upgrading to 2.2.5 i am getting the error in the subject when
bootstrapping my app.
Here is my ivy.xml definition for getting the dependencies.
I really dont know why XmlSchema.jar is missing as it seems. In fact it doesnt
get downloaded with both dependencies in
Hi
Have you registered this interceptor with the jaxws:endpoint only ? Can you post the example showing how you configured the jaxws
and jaxrs endpoints
cheers, Sergey
- Original Message -
From: "Pydipati, Karuna"
To:
Sent: Tuesday, January 19, 2010 9:58 PM
Subject: SOAP intercept
Hello,
One of the three big French telecommunications operator use CXF for
its portal, one of the ten biggest French web portals.
Sorry, I can't name it :-)
We use CXF for:
* JAX-WS implementation on both client and server sides,
* JAX-RS implementation on server side : consumed by w
The BBC uses it
-Original Message-
From: Andrew Dinn [mailto:ad...@redhat.com]
Sent: 20 January 2010 09:33
To: users@cxf.apache.org
Subject: Re: What companies are using CXF?
On 01/19/2010 11:04 PM, Dale Ogilvie wrote:
>
> Does Redhat/Jboss count?
>
> http://press.redhat.com/2009/03/25/
On 01/19/2010 11:04 PM, Dale Ogilvie wrote:
Does Redhat/Jboss count?
http://press.redhat.com/2009/03/25/red-hat-adds-muscle-to-apache-cxf/
Hmm, you need to read that page a bit more carefully before you start
making claims you cannot substantiate. It states that JBoss
_contributes_ to the C
On 20/01/2010 06:42, Christian Schneider wrote:
Am 19.01.2010 23:16, schrieb easternwahoo:
I am writing a justification for use of CXF at my company, and I need
to list
any commercial companies that are using it. I've searched the Apache CXF
site and the FuseSource site. The only company I foun
41 matches
Mail list logo
