On Mon, Sep 14, 2009 at 8:07 PM, Agustin Barto wrote:
> 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 tha
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
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
On Wed, Aug 12, 2009 at 6:21 PM, Daniel Kulp wrote:
>
> Actually, I would call that bug. Can you log an issue?
>
> It kind of gets worse. If you have a namespace of v1.1, it ALSO would just
> map to v1. Thus, two namespaces mapping to the same place. Not good.
>
> That said, the RI does the
I'm generating the server code for a WSDL which namespace ends with a
version number "http://foo.bar.com/service/v1.0";, and the generated
java package is com.bar.foo.service.v1. The service refers to types
defined on the namespace "http://foo.bar.com/service/v1.0/types"; and
the generated package
