Yes it leverages Spring-DM.
The documentation is a bit rough, and if haven't had much time to test it on
a very clean platform aso, so if you have any problems, please report so we
can fix it asap.
See http://cwiki.apache.org/SMX4/cxf-examples.html
On Fri, Apr 4, 2008 at 3:32 AM, Glen Mazza
The documentation is a bit rough, and if haven't had much time to test it on
a very clean platform aso, so if you have any problems, please report so we
can fix it asap. See http://cwiki.apache.org/SMX4/cxf-examples.html
On Thu, Apr 3, 2008 at 1:48 PM, Guillaume Nodet [EMAIL PROTECTED] wrote:
On Thu, Apr 3, 2008 at 2:04 PM, [EMAIL PROTECTED] wrote:
Will Spring-DM also be a part of this example?
It really doesn't change much if it can be done with OSGi itself.
Spring-DM is just an additional layer that lets use biuld bundles yet
it could in turn complicate understanding of the real
Hi
CXF HttpBinding can be considered deprecated as it has not been supported for a
while.
I'd recommend you to try a JAX-RS approach, multiple query parameters are
supported there...
Cheers, Sergey
I have tried the rest style web service with http binding with CXF2.0.3
version. My
The example I gave leverages Spring-DM. Spring-DM is a small layer above
Spring that gives you a really simple way to build OSGi applications based
on Spring. Of course, if you don't like spring, don't use Spring-DM.
However, CXF is nicely integrated with Spring, so it makes sense.
If you
You were right.
I excluded a bunch of dependencies, and everything still works just fine.
Thanks for the prompt support !
As a side node, you might be interested to know that CXF is currently being
used as support to build the web-service based bindings in the
www.scorware.org project, which
I think this has to do with the XML jars in your path. What container are
you in?
Hmm I'm not familiar with Apache ServiceMix so it's a bit difficult
for me to understand how this can help me with an OSGi platform
like Equinox.
I understand that CXF is provided as a module for ServiceMix, right?
Can you provide some help on getting CXF to work on a normal OSGi
platform? I had a
Do the mailing lists have any problems ? I'm only receiving half of
the messages :-( Or sometimes a few hours later ...
On Fri, Apr 4, 2008 at 4:01 PM, Daniel Kulp [EMAIL PROTECTED] wrote:
On Friday 04 April 2008, [EMAIL PROTECTED] wrote:
Hmm I'm not familiar with Apache ServiceMix so it's a
On Friday 04 April 2008, [EMAIL PROTECTED] wrote:
Hmm I'm not familiar with Apache ServiceMix so it's a bit difficult
for me to understand how this can help me with an OSGi platform
like Equinox.
I understand that CXF is provided as a module for ServiceMix, right?
Can you provide some help on
Hi,
I'm trying to integrate the JAX-RS implementation now included in CXF 2.1
(snapshot).
The service is correctly called and the parameters arrive fine but then I
get a page with the message:
No message body writer found for response class : SimpleResponse.
Where SimpleResponse is my custom
Most likely, it's an element qualification issue. In 2.0.4, we had to
fix a bunch of issues with improper soap messages being
produced/consumed due to elements that should have been qualified not
being qualified and vice/versa. There were cases with 2.0.3 where a
VALID soap message
One more note: the default for the simple frontend is to use QUALIFIED
schemas. Thus, if you are doing java first stuff and use JAX-WS on the
server and simple on the client, if you don't reconfigure one or the
other, you will have problems as the client will send qualified, but the
server
In this case I do not have element that represents the attachment in WSDL.
It comes as part of the Soap message as multi part attachment. So not sure
how do I get the attachment. I could only find code that can easily get
attachment using axis1.1 for the request.
--Vijay
On 4/3/08 7:58 PM,
Looking at the CXF code it seems the problem is here:
private T MessageBodyWriterT chooseMessageWriter(
ListMessageBodyWriter writers, ClassT type, MediaType mediaType)
{
for (MessageBodyWriterT ep : writers) {
if (!ep.isWriteable(type)) {
continue;
Hi
MessageBodyWriter.isWriteable() checks if a given type can be
serialized, so if say you custom type has no JAXB annotations then no
matching writer will be found. You may want just to add @XmlRootElement
to the root of your class, alternatively you can register your custom
writer. Please check
SwA is different from MTOM. I don't know of CXF does SwA.
On Fri, Apr 4, 2008 at 11:07 AM, Vijay Allam
[EMAIL PROTECTED] wrote:
In this case I do not have element that represents the attachment in WSDL.
It comes as part of the Soap message as multi part attachment. So not sure
how do I get
Ick... If their wsdl properly declared the attachments like a good
contract would, it would be easy as the generated code would just handle
it.
I just spent some time trying to figure out something and I'm not
succeeding unless you write an interceptor. The Message object sent
into an
It worked! :-)
So now I'm just returning:
return Response.ok(simpleResponse).build();
where the SimpleResponse class has the @XmlRootElement annotation on top.
Thank you very much for your help,
V.
On Fri, Apr 4, 2008 at 5:51 PM, Beryozkin, Sergey [EMAIL PROTECTED]
wrote:
Hi
On Friday 04 April 2008, Benson Margulies wrote:
SwA is different from MTOM. I don't know of CXF does SwA.
It does for the jaxws frontend as the jaxws spec requires it. It's
pretty much tied to how the jaxws spec requires the code to be generated
which is why the code lives in the jaxws
This is covered in the jaxb spec. (section 6.7.5, see example 6-14) In
sort, there isn't a way. The main reason is that the subclasses of
AbstractFeatureType may not (actually, per spec, they WON'T) have
XmlRootElement declarations on them so the runtime would have idea what
the qname of
On Thursday 03 April 2008, jm1468 wrote:
...
WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception
caught writing response: Failed to configure TRaX
...
org.apache.cxf.interceptor.Fault: No such operation
Ick.. there are several things wrong that I need to dig into quite a
Thanks a lot. This is what I'm looking for to get the attachment from the
client. ((BindingProvider)proxy).getRequestContext().get(ATTACHMENTS);
It was a third party web service. I have already have the interceptor but I
did not know how to get the attachment back to the client.
This will
On Friday 04 April 2008, Daniel Kulp wrote:
On Thursday 03 April 2008, jm1468 wrote:
...
WARNING: org.apache.cxf.transport.http.WSDLQueryHandler Exception
caught writing response: Failed to configure TRaX
...
org.apache.cxf.interceptor.Fault: No such operation
Ick.. there are
Brad,
Are you using the older http binding or the newer JAX-RS stuff?
If using the older stuff, you probably could get it to work by writing an
interceptor that would wrap the XmlStreamWriter with one that would
strip off any namespace stuff. It would be a little bit of work, but
not too
When a SOAP request is submitted without the closing /soapenv:Envelope, the
Web Service is called and no errors are thrown.
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:v1=http://www.nortel.com/xmlprotocol/wsdl/data/protocol_interfaces/cisco_icm/v1_0;
Dan,
I was able to create the service dynamically. I have another related
question.
Is it possible to create one instance of JaxWsProxyFactoryBean server
and then add multiple endpoints to this instance dynamically? In
essence, I would like to run multiple instances of the same web service
Hello,
I am using CXF with RESTful services, configured with Spring. My
request objects (parameters to my service methods) and response
objects (return types on my service methods) have a common structure,
so I created some base classes with common members, which the actual
request and
I thought I'd add some sample code:
My superclass:
@XmlType
public abstract class ServiceRequest {
private String ssid;
@XmlAttribute
public String getSsid() {
return ssid;
}
public void setSsid(String ssid) {
this.ssid =
29 matches
Mail list logo
