Hi All,
I've seen a number of related threads but nothing which will suit exactly. I
have 2 service classes, one needs to bind to "/" the other binds to say
"/a".
Now the first has operations like "/b" but also "a/123/blah" and the second
has operations at "/a" and "/a/123" (never a direct overl
Hi
I posted this in a separate thread today. Sorry. After some
investigation, I found this. Please help me.
I see a strange behavior in HTTP PUT (REST). When I tried CXF-2.2.2
deploying userapi.ear (with "user" as context-root in jboss), it is
failing with following error. If I rename same ear fi
Hi Sergey,
Was there a JIRA issue opened for this or has it been added as a feature?
Regards,
Kynan
Sergey Beryozkin-2 wrote:
>
> Hi
>
> It's just a JAXRS selection algorithm that dictates it, or rather, it does
> not allow for selecting between multiple resource classes
> which have the sa
Hi
I am having this error. Could you help me? Why am I getting this error?
I tried both CXF-2.2.2 and cxf-2.2.3
17:28:54,290 ERROR [STDERR] Sep 14, 2009 5:28:54 PM
org.apache.cxf.interceptor.LoggingInInterceptor logging
INFO: Inbound Message
ID: 3
Address: /userapi/us
On Mon, Sep 14, 2009 at 5:09 PM, Daniel Kulp wrote:
>
> Couple thoughts:
>
> 1) Turn on schema validation - an invalid value would result in a fault sent
> back to the client.
How can I do that?
> 2) Try with the latest CXF 2.2.4-SNAPSHOT code - we added a validation
> handler thing to the JAXB
Couple thoughts:
1) Turn on schema validation - an invalid value would result in a fault sent
back to the client.
2) Try with the latest CXF 2.2.4-SNAPSHOT code - we added a validation
handler thing to the JAXB marshaller that will propagate some errors up.
3) Register your own validati
Any chance you can create a small testcase that shows this? We definitely
have several tests that echo rather large attachments back and forth and
everything seems OK. (at least with CXF 2.2.3, might try upgrading)
Dan
On Mon September 14 2009 10:13:53 am Michael Albrecht wrote:
> Hi @
This seems to be a bug in the mule bundled version of CXF which is quite old.
I would recommend taking it up with Mule to get a newer version of CXF.
Dan
On Sun September 13 2009 2:48:47 am manoj.java wrote:
> I am using cxf at server side to expose the web service.
> I have used the org.apa
I generated a CXF Web Service based on a WSDL using WSDL2Java. One of
the requests has an optional element which is restricted to an
enumeration using an XML facet on the schema.
The problem is that whenever the client sends an invalid value on this
element, the related field is set to null and si
The easiest way is to add a package-info.java to the package the beans are in
that has something like:
@javax.xml.bind.annotation.XmlSchema(namespace = "http://domain.test.com/";)
package com.test.domain;
That should take care of it. If not, you'll need to add @XmlRootElement and
@XmlType ann
Any Suggestionsthis is driving me to my wits end?
--
View this message in context:
http://www.nabble.com/Bad-namespace-in-WSDL-when-adding-custom-classes-tp25410793p25439577.html
Sent from the cxf-user mailing list archive at Nabble.com.
As Sergey said, the binding files are a code gen type thing. Basically, the
binding files affect the annotations and such that are generated on the
generated .java files and those annotations then affect the runtime.
What types of things are you trying to control from the bindings file?
S
> -Original Message-
> From: Sergey Beryozkin [mailto:sergey.beryoz...@iona.com]
>
> We've chatted with Dan on IRC about it... The external binding files
> can
> only be used for code-gen purposes. They can not be utilized during
the
> marshalling time. But there's always an option to regi
Hi
We've chatted with Dan on IRC about it... The external binding files can
only be used for code-gen purposes. They can not be utilized during the
marshalling time. But there's always an option to register a custom
XMLStreamWriter. Please let us know how you'd like the output be affected by
an e
> -Original Message-
> From: Daniel Kulp [mailto:dk...@apache.org]
> Sent: Monday, September 14, 2009 9:08 AM
> To: users@cxf.apache.org
> Cc: Sergey Beryozkin
> Subject: Re: How to have CXF work with external JAXB bindings file?
>
>
> As Sergey said, the binding files are a code gen type
On Mon September 14 2009 11:19:03 am KARR, DAVID (ATTCINW) wrote:
> The lib directory of CXF contains Spring 2.5.5, as opposed to 2.5.6, the
> latest 2.5.x release. Is there any reason to expect issues if I use
> 2.5.6?
There aren't any real "issues" that I'm aware of.
The reason we use 2.5.5
Following the various conversations in relation passing data objects to
remote OSGi Services I've enhanced the Greeter demo to show how you can do
this.
The new GreeterService API is as follows:
public interface GreeterService {
Map greetMe(String name); // was already there
GreetingPhrase
The lib directory of CXF contains Spring 2.5.5, as opposed to 2.5.6, the
latest 2.5.x release. Is there any reason to expect issues if I use
2.5.6?
Hi @all!
I've got a single web service routine (implemented with the BPM Suite
inubit 5.*) which is sending a PDF file as a mtom attachment of the ws
call.
If I test this method with soap UI everything is ok. I can read the
PDF file as a soap attachment.
If I test this method with my JS
19 matches
Mail list logo
