I am getting the following exception when running a simple CXF 2.1.4 dynamic
client test using maven surefire plugin. The strange thing is, this test
works fine if I run it standalone.
Any clues why this fails when run using surefire?
public void testWsdl2Java() throws Exception {
Jax
Can you try with the latest snapshots? I think I fixed the attribute thing
last week. I'd like to double check that.
Dan
On Tue April 7 2009 5:02:30 am Valerio Angelini wrote:
> Hello,
>
> I'm using CXF through the JAX-WS Provider interface. I set the
> parametric parameter of the interfac
Hi
I checked, it supports it on the output only, when File is returned.
I need to verify if File has to be supported on the input - probably
yes...
in which case we'd need to copy the input stream to some temp storage...
Using InputStream is another option as a temp measure till I fix using
File o
I'm encountering the following exception at application startup following an
attempt to upgrade from 2.0.8 to 2.2:
2009-04-07 11:49:58.221::WARN: Nested in
org.springframework.beans.factory.BeanCreationException: Error creating bean
with name 'org.apache.cxf.wsdl.WSDLManager' defined in class pat
Here's the jira. Sorry for taking a while to get to it. It's been a crazy week.
https://issues.apache.org/jira/browse/CXF-2162
Thanks,
John
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Friday, April 03, 2009 5:21 PM
To: users@cxf.apache.org
Cc: John Hite
Subject
In reading the documentation for JAX-RS it says "By default, CXF supports
String, byte[], InputStream, Reader, File ...". I'm trying to create a
service that will accept a file upload using the following signature:
@POST
@Path("/upload/")
@Consumes("application/octet-stream")
public Response up
I'm trying to use the smaller cxf modules in my project and I'm running into a
problem. I keep getting the attached exception. I am including the following
modules;
modules/cxf-api-2.2.jar
modules/cxf-rt-core-2.2.jar
modules/cxf-common-utilities-2.2.jar
modules/cxf-rt-bindings-soap-2.2.jar
modul
Eoghan Glynn wrote:
I guess the only justification for not decoding the is that
we don't use it internally in the CXF dispatch logic.
But I guess applications or custom interceptors may be interested in
this header, so we should really decode it.
Yes indeed. For example, the WS-AT spec (which
Hi,
CXF HTTP Binding described at http://cwiki.apache.org/CXF20DOC/http-binding.html
has been deprecated but we need to update the docs to make it clearer.
JAXRS implementation described at http://cwiki.apache.org/CXF20DOC/jax-rs.html
is what we're working upon now. There're few basic demos in
Hi everybody.
I'm a French new user of Apache CXF.
I've tried the RESTful HTTP Binding Demo published with CXF package,
described at these pages :
http://cwiki.apache.org/CXF20DOC/http-binding.html
http://cwiki.apache.org/CXF20DOC/jax-rs.html
The example is located at this repertory:
./apache-cx
Hi Chris
it's great :-)
that code though may get a bit brittle if other XML-aware providers are
registered/found.
I do like the idea of updating teh JAXBElementProvider to check the injected
context for well-known marshaller properties
such that the only thing you do is to
message.put(XML_HEAD
Many thanks Sergey, that helped hugely!
Attached is my (skeletal) code which may help other beginners like myself.
Please point out obvious errors.
import java.util.HashMap;
import java.util.Map;
import javax.ws.rs.core.MediaType;
import org.apache.cxf.jaxrs.model.OperationResourceInfo;
import
Jose,
Not sure I understand when you say the WSDL specifies soap12, but the
server only supports soap11. If the WSDL specifies soap12 then I'd
hope the server would support soap12.
If you want to pick up different soap endpoints in the WSDL we did it
in GroovyWS in this way ...
pro
Hi Chris
I just sent you the other email...
May be what you find unnatural about this code is that is's not XML-centric, something similar to using regular
expressions for transforming XML :-).
cheers, Sergey
- Original Message -
From: "Chris Marshall"
To:
Sent: Tuesday, April 07,
Hi,
You can set up a JAXRS endpoint like this :
JAXRSServerFactoryBean factory = new JAXRSServerFactoryBean();
factory.setResourceClasses(myService.class);
JAXBElementProvider provider = new JAXBElementProvider();
p.setMarshallerProperties(properties);
factory.setProviders(provider);
factory.cre
Hi Ian,
Thanks so much.
The problem is that the service WSDL specifies soap12 but the server only
supports soap 1.1 requests.
SoapUI was using SOAP 1.1. When I changed it to 1.2 I had the same error.
Is there a way to force the cxf client to use soap 1.1 without changing the
wsdl file? I have
Hi SergeyTo clarify my earlier post I can achieve the result I want via an
interceptor with the following code:
public void handleMessage(Message message) {
try {
OutputStream os = message.getContent(OutputStream.class);
byte[] b = "".getBytes();
os.write(b);
message.setContent(OutputStream.class,
Hi
Hi there,
I'm starting to use Continuations in my code... I'm presuming that they're
all nicely working. ;-)
thanks for experimenting and hope they'll work nicely for you.
I noticed the following code on Sergey's blog:
Continuation c = provider.getContinuation();
synchronized (c) {
You might be sending a SOAP 1.1 request to a SOAP 1.2 port. I've seen
a 415 thrown from WCF for this reason. 415 essentially means an
unsupported media type - http://www.w3.org/2000/xp/Group/2/03/11/soap-1.2-conformance.html#http-415
Cheers,
Ian
On 7 Apr 2009, at 11:09, Rodriguez, José wr
Hi Daniel,
thx for pointing out.
Will exclude the catalog stuff as soon as i upgrade to 2.2.1. And i
also wondered why mail is there :) Perhaps i will exclude this too.
BTW i just read about the JAX-RS api in CXF and that i can simply
expose services with jax-ws AND jax-rs. Thats nice! As a
Hi,
I have a cxf 2.0.10 client and I try to use a service with WS-Security and SSL.
The service is based on the Microsoft implementation.
It works just fine with soapUI but using CXF I have the following exception:
7 avr. 2009 11:33:58 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO
Hi
I've got an issue with arrays and inheritance using remote services.
Note that I've got a remote service working over 6 different protocols
using
the Spring remoting stuff. These protocols are: RMI, JMX, Hessian,
Burlap, SOAP (CXF 2.2) and HttpInvoker.
Model objects:
public class Order i
Thanks - using JAXRSOutInterceptor was part of my experimentation ;-)I am
still battling to find out how to set marshaller properties
programmatically.
My ultimate goal is to set the xsl stylesheet depending on runtime data.
Thanks for your patience.
Regards Chris
2009/4/6 Sergey Beryozkin
> Hi,
Hello,
I'm using CXF through the JAX-WS Provider interface. I set the
parametric parameter of the interface to javax.xml.transform.Source.
The XML results of marshalling a DOMSource or a JAXBSource are
different: in particular some attrubute names marshalled with
JAXBSource are wrong.
T
Hello everyone,
I use Spring 2.5.6 with CXF 2.2 create web services with Tomcat 6.0.18.
Everything is fine with HTTP, but with HTTPS, there are a lot of problems.
I've configured Tomcat to serve request with SSL like this:
I can access the WSDL with Firefox just fine (after adding my serve
25 matches
Mail list logo
