I LOVE OPEN SOURCE
It worked :)
just need to call following from service implementation when another
response needs to be sent (as long as you keep calling this your
method will get reinvoked to handle this incoming request; so you can
send as many responses to each request as you want)
Glen, you can find a further discussion here:
If i remember well in CXF there is a single interceptor that manages all the
logical handlers passed through the @HandlerChain annotation.
http://www.nabble.com/differences-between--CXF-Interceptors-and-JAX-WS-Handlers-tt13975552.html#a13975552
As a
Benson Margulies wrote:
Thank you.
I wonder if it's a bug in CXF that the JavaFirst trick doesn't work? Or
is there an @XmlElement trick to specify base64Binary for the string?
I got exactly the same behaviour from Metro. I think the only way to do
it is to write the request wrapper class
I reached the same conclusion. I'm surprised that the MtoM stuff works
at all on wrapped parameters. The only difference is that I've taken a
vow to use BARE services when I care to know exactly what is going on.
On Tue, 2008-01-15 at 11:05 +, Ian Roberts wrote:
Benson Margulies wrote:
On Tue, 2008-01-15 at 00:32 -0500, Liu, Jervis wrote:
First of all, you need to set wrapped style to false, wrapped style true
won't work with JSON (I noticed that you already set wrapped to false). What
happened is Jettison reads input stream to a W3C Document, then this W3C
Document is
Thank you for your replies.
I will try to change my code in a way that it will work :-(
dkulp wrote:
You've hit a known bug in XmlSchema:
https://issues.apache.org/jira/browse/WSCOMMONS-273
We're waiting for a new version of XmlSchema to be released that fixes
that bug (and a
I actually hadn't thought about it in that way, Benson. Generally,
we're looking to build some flexible libraries and services that will be
inter-operable amongst different applications, so we may have to support
calls from other libraries (like YUI, for example) for JSON format. I'm
just doing
Interesting - I'm going to try a few things, mayhap I am missing missing on my
end.
-Original Message-
From: Liu, Jervis [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 12:32 AM
To: cxf-user@incubator.apache.org
Subject: RE: Issues with JSON based Service and Jettison
First
Hello,
Odd question - I feel like I am missing something obvious. For some
reason, my IDE (intelliJ 7) won't recognize the snapshot of the main CXF
jar, and I can't use winzip to open it. I can extract single files from
it. I think the IDE code analyzer can't decompress it either - am I
For sever side, I add
@BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) to my
implementation class. When deploying in tomcat, I got the following
exception:
Jan 15, 2008 9:16:37 AM org.springframework.web.context.ContextLoader
initWebApplicationContext
SEVERE: Context
I want to write RESTful services, utilizing some of the same Service classes
I've written for our GWT client, and I need to be able to return either XML
or JSON based on something in the URL.
For instance:
http://myserver/someapp/json/person/{id}
or
I tried these:
@BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING)
@BindingType(value=org.apache.cxf.binding.soap.SoapTransportFactory.SOAP_12_HTTP_BINDING)
But neither of them work. I make it work by using the real String as below.
When deploying in tomcat, it's complaining about Caused by:
java.net.MalformedURLException: no protocol: /hello_world
Did I not get the schema for simple? where can I find it?
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean
with
Tony,
Are you grabbing the jar from a maven dependency (like cxf-bundle) or by
downloading the distribution and unpacking it? Also, 2.1 or 2.0.4?
Just wanted to know where to start looking.
Dan
On Tuesday 15 January 2008, Vespa, Anthony J wrote:
Hello,
Odd question - I feel like I
Sorry for not including more info, my bad.
I'm grabbing the zip version of the nightly 2.1 snapshot and just
unpacking the .jar and dropping it into my lib dir. I noticed this
occurred with the last 2 or 3 snapshots of 2.1.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
OK. Looks like a bug in the latest shade plugin.Using unzip, I see:
Length MethodSize Ratio Date Time CRC-32Name
-- --- - --
0 Defl:N2 0% 01-13-08 19:17 META-INF
...
but for a javadoc jar,
I'm sending files
Willem Jiang pisze:
Hi Pawel
Did you use CXFServlet transport which delegate the http transport to
a CXFServlet ?
If so , could you show me your Web.xml and Beans.xml?
In you case I think you still start a new Jetty engine for listening
the port.
Willem.
Pawel Janusz
Yep. Bug in shade plugin.I've just fixed it, but it will require a
new release of the shade plugin to get it working. :-(
Dan
On Tuesday 15 January 2008, Daniel Kulp wrote:
OK. Looks like a bug in the latest shade plugin.Using unzip, I
see:
Length MethodSize Ratio
I need to add these:
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
Can anybody tell me what they are and how they're found and referenced?
Those values on those interfaces are the Strings. For examle, if you
look at the code for javax.xml.ws.soap.SOAPBinding, you see:
public static final String SOAP12HTTP_BINDING
= http://www.w3.org/2003/05/soap/bindings/HTTP/;;
Thus, the annotation you should have written is:
Pawel,
When deploying in tomcat (or other war based thing), there are two
approaches to go to get it to work. You kind of mixed the two
approaches so now it doesn't work. :-)
Approach one:
1) Original CXF way of doing it: define your beans in
WEB-INF/cxf-servlet.xml and do NOT put any
I have been using it since I began use CXF. Eclipse STP Plugin helps me a lot
to do the annotation.
But STP sometime doesn't re-generate wsdl. Or once I click Generate Code on
wsdl, I don't know how to re-generate wsdl file/classes. So anytime I make
some changes to my SEI, I need to build a new
Well, the STP project does have a bunch of issues around Java first use
cases that they are planning to address.Mostly, the STP folks have
concentrated on the WSDL first things. For Java first, the
simple+aegis stuff does work quite well. However, it's useless for
wsdl first as there
Thanks for looking into this, I just thought it was me being crazy at
first. =)
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 15, 2008 1:33 PM
To: cxf-user@incubator.apache.org
Subject: Re: Snapshot JAR file
Yep. Bug in shade plugin.I've
I sent my example, can You translate my conf into correct one with 1st
option ?
Daniel Kulp pisze:
Pawel,
When deploying in tomcat (or other war based thing), there are two
approaches to go to get it to work. You kind of mixed the two
approaches so now it doesn't work. :-)
Approach
It looks like you're running into the same usage issue as Powel did.
See:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200801.mbox/200801151428.34207.dkulp%40apache.org
Dan
On Tuesday 15 January 2008, yulinxp wrote:
When deploying in tomcat, it's complaining about Caused
Hmm... interesting solution.I like it. :-)
One potential issue is the use of the ThreadLocal, but that's definitely
not an issue right now. The API's technically allow an interceptor
to pause the chain and then resume it on a separate thread. (for
example, to wait for a resource to
Guillaume,
The mapping of the operation to a wrapper type (assume wrapped doc/lit)
is part of the frontend, not databinding (unless there are
@Request/@ResponseWrapper annotations, but that's still JAX-WS only so
really is still frontend related).
Thus, it depends on which ServiceFactory
On your TransformationPortImpl.java, add a @WebService annotation with
the wsdlLocation specified there. The interface is kind of supposed to
be somewhat detached from the wsdl which is why the wsdlLocation
annotation is generated there. That said, it should have worked. I'll
need to
-Original Message-
From: Charles W. Stanton [mailto:[EMAIL PROTECTED]
Sent: 2008年1月15日 23:38
To: cxf-user@incubator.apache.org
Subject: REST with different return formats
I want to write RESTful services, utilizing some of the same Service classes
I've written for our GWT
Hi Pawel,
I think you just need to remove the below lines in the beans.xml
bean class=org.apache.cxf.transport.local.LocalTransportFactory
lazy-init=false
property name=transportIds
list
valuehttp://cxf.apache.org/transports/local/value
They are the spring description files of cxf components.
import resource=classpath:META-INF/cxf/cxf.xml / this is the cxf core
component.
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml / this is
the soap component configuration file.
import
Actually that is what I had tried initially. I added an interceptor at the
end and used a flag on the message to decide on reprocessing. But it didn't
work after 2 and half days of effort so I gave in to modifying cxf code.
It would be great if some of the interceptors could undo the change they
33 matches
Mail list logo
