I'm not clear if you're creating a SOAP client or web service provider.
Generally speaking, use cxf.xml only for SOAP clients; for web service
providers, unless you're doing some big-time CXF surgery,
cxf-servlet.xml or anythingelse.xml as shown in Steps #7 and #8 here is
preferable: http://www.jr
Still looking for help on this.
I want to learn where to place my custom cxf.xml in my source tree so that
is does get picked up during wsdl2java.
After some more googling, I see that others have reported a similar error
and that the problem is seen with 2.0.6 and 2.1 (not with 2.0.2).
Any poin
I can easily invoke a resource passing in a single value, for example:
/products/123
Is it possible to bind a url like this:
/products/123;456;789
to a method signature? Basically I'd like to return multiple products at
once.
I tried defining an @PathParam on an array parameter, but that d
You would probably be happier with the DynamicClientFactoryBean, unless you
have exactly the same Java code on the two sides of the service.
On Fri, Jun 6, 2008 at 4:43 PM, RichT <[EMAIL PROTECTED]> wrote:
>
> I'm trying to use CXF to invoke a simple soap service without using a Java
> interface
This 2008-04-01 snapshot is all I have to work with here. Is there
any way to get it to work with this code?
Chris W.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2008 5:13 PM
To: users@cxf.apache.org
Subject: Re: Bug CXF-830 closed, but I still
Not really sure what would cause that. That said, with CXF 2.1, you
don't need to configure in the SAAJInInterceptor. The
WSS4JInInterceptor will automatically do that if needed.I'm not
sure if that would change anything (it shouldn't).
Dan
On Jun 6, 2008, at 5:03 PM, Wolf, C
I am trying to configured the out-of-the-box CXF security interceptors,
but I am getting a NullPointerException:
INFO: Interceptor has thrown exception, unwinding now
java.lang.NullPointerException
at
org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:658)
at
org.apa
On Jun 6, 2008, at 4:37 PM, Wolf, Chris (IT) wrote:
Dan,
You mentioned that CXF interceptors have a performance advantage over
JAX-WS interceptors, such as SOAPHandler implementations because
CXF interceptors don't read in the whole message into DOM.
However, I notice that in the code for SAA
I'm trying to use CXF to invoke a simple soap service without using a Java
interface or WSDL to generate a proxy. I'm assuming CXF provides a generic
soap client with which I can tell it which operation to invoke, and give it
in the inputs.
This is the code I expected to work in CXF:
ClientFa
Dan,
You mentioned that CXF interceptors have a performance advantage over
JAX-WS interceptors, such as SOAPHandler implementations because
CXF interceptors don't read in the whole message into DOM.
However, I notice that in the code for SAAJInInterceptor that, in fact,
this CXF interceptor do
I recommend not touching the "schemaLocation" settings. You can
override this externally with an
XML catalog, which can redirect to a local copy. In Eclipse:
Window=>Preferences=>Web and XML=>XML Catalog, then press "Add".
Also see:
http://www.eclipse.org/webtools/community/tutorials/XMLCata
I have fixed the problem. It seems the behavior of WSS4JOutInterceptor has
changed, so I have to call super.handleMessage(message) from my interceptor and
add my real interceptor to the interceptor chain as it does in
WSS4JOutInterceptor.
Boxiong
- Original Message
From: Boxiong Ding
H
We updated to XmlSchema to 1.4.2 in the latest releases (2.0.6/2.1) as
it fixes a WHOLE bunch of blocker bugs that users were hitting.
Example, if any of your jaxb beans were final, it would barf.
However, in your stack trace, I see:
org
.apache
.cxf
.service.factory.Reflect
Hi,
If you comment the jaxws endpoint definition, do you have a rest service
accessible ?
Cheers, Sergey
- Original Message -
From: "Frank Ittermann" <[EMAIL PROTECTED]>
To:
Sent: Friday, June 06, 2008 4:42 PM
Subject: rest services and soap services with cxf and tomcat
Hello anyon
Hello anyone,
I've tried to develop soap services with cxf. Thats work and rocks. But i've
also tried rest (jaxrs) services to devlop with cxf.
Develop work means compile and deploy to tomcat but I can't call the rest
service and after a debug session i saw that the soap services overrided the
res
Has anyone been able to get CXF working with JBoss 5? I can't get the JBoss
container to use CXF instead of the JBossWS implementation.
--
View this message in context:
http://www.nabble.com/CXF-with-JBoss-5-tp17693924p17693924.html
Sent from the cxf-user mailing list archive at Nabble.com.
On Jun 6, 2008, at 9:20 AM, Nikolaj A. wrote:
Sorry for the delay, but I've been stuck on other projects.
I tried with the apache-cxf-2.1.1-20080530.191058 snapshot and it
did not
solve the stack overflow issue (see the trace below). But I'm not
sure if I
tried with the correct snapshot t
Ups, I forgot the trace:
java.lang.StackOverflowError
at java.lang.System.checkKey(System.java:742)
at java.lang.System.getProperty(System.java:626)
at sun.security.action.GetPropertyAction.run(GetPropertyAction.java:66)
at java.security.AccessController.doPrivileg
Sorry for the delay, but I've been stuck on other projects.
I tried with the apache-cxf-2.1.1-20080530.191058 snapshot and it did not
solve the stack overflow issue (see the trace below). But I'm not sure if I
tried with the correct snapshot that you generated for me Dan, could you
verify?
Thank
Hi
Current JSON provider on the trunk works with a JAXBContext in tandem and it
can only acquire a JAXBContext
if XMLRootElement annotation is available. Once the patch I'm slowly working upon is commited, it will be able to acquire contexts
if an ObjectFactory is available in a package and thu
Hi,
I'm using SOAP Headers to send Authentication tokens.The Security
implementation technique is same as described on
http://cwiki.apache.org/CXF20DOC/ws-security.html
i want to expose my services as REST do this existing Authentication soap
header work with REST services or what changes are req
Hi,
I'm using SOAP Headers to send Authentication tokens.The Security
implementation technique is same as described on
http://cwiki.apache.org/CXF20DOC/ws-security.html
i want to expose my services as REST do this existing Authentication soap
header work with REST services or what changes are req
Hi Dan, unfortunately I can't send a test case due to the IP on the
wsdl. However, here is the full stack trace:
testRetrieveParties(xxx.xxx..xxx.service.party.PartyManagerServiceIm
plTest) Time elapsed: 1.719 sec <<< ERROR!
org.apache.ws.commons.schema.XmlSchemaException: Schema name c
Hi,
I'm using SOAP Headers to send Authentication tokens.The Security
implementation technique is same as described on
http://cwiki.apache.org/CXF20DOC/ws-security.html
i want to expose my services as REST do this existing Authentication soap
header work with REST services or what changes i are r
On Jun 6, 2008, at 2:38 AM, jfougere wrote:
Hi Dan,
I tested my full project with your workaround in 2.1.1-SNAPSHOT and
everything works correctly.
Cool. Thanks for the verification.
Thanks a lot.
I assume this correction will be in official 2.1.1 release ? release
date in
june, a
Would you happen to have xalan on the classpath or in your war? The
loss of the namespace prefix is a xalan bug. It's SUPPOSEDLY fixed
in xalan 2.7.1, but that version has other problems that makes it not
usable (and isn't in maven either).In most cases, you can remove
xalan jar an
Hello,
this worked for me:
> 2) Update the element in your config to add the
> qnames for the service name and portname.
I changed my configuration like this...:
...and now my service responds properly and is accessible from the clients.
Thanks a lot for your support!
There is one
27 matches
Mail list logo
