Wsdl2java ignores soapAction?
I tried to apply wsdl2java to the WSDL below. The WSDL operations
defined are both referring to the same type element as input message,
so the soap body are the same for both the messages. To solve this
collision, i added the soapAction to the binding, but the wsdl2java
seems to ignore it.
The message returned by the tool is:
WSDLToJava Error : Non unique body parts! In a port, operations must
have unique operation signaure on the wire for successful dispatch. In
port {urn:test}EchoTestPort, Operations "{urn:test}echoRequestB" and
"{urn:test}echoRequestA" have the same request body block
{urn:test}TRequestA
That's correct (if no soapAction is defined), but in my opinion
shouldn't be returned with the soapAction defined.
Marco.
xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns1="http://test.it";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:soap12="http://www.w3.org/2003/05/soap-envelope";
xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding";
xmlns:tns="urn:test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; targetNamespace="urn:test">
elementFormDefault="qualified" targetNamespace="urn:test">
name="dataBoolean" nillable="false" type="xsd:boolean"/>
name="dataString" nillable="false" type="xsd:string"/>
name="typeA" nillable="false" type="tns:TypeA"/>
name="typeB" nillable="false" type="tns:TypeB"/>
type="tns:TypeA"/>
type="tns:TypeB"/>
http://localhost/fake_location"/>
Re: item with xmlns="" testcase
I have attached the test case to the CXF 1407 issue (https://issues.apache.org/jira/browse/CXF-1407). Bye, Marco. On Fri, 2008-01-25 at 09:14 -0500, Daniel Kulp wrote: > On Friday 25 January 2008, Marco Piraccini wrote: > > I have created a test case for the problem, but every time i try to > > send to Dan or to cxf-user mailing list the mail with the TestCase, > > the mail returns back with the message: > > > > Remote host said: 552 Message rejected as it is spam (body) > > > > How can i send the zip (that's very small, 13k)? > > Marco. > > That apache spam filters tend to strip off all kinds of things and cause > issues. Two options: > > 1) Create a jira that describes the bug and attache the test case there. > Of course, that ends up being "public". > > 2) If the test case has some "private" data or schemas or something, I'm > happy to take a look if you send it to me directly. Unfrotunately, the > [EMAIL PROTECTED] and [EMAIL PROTECTED] address both have nast spam and > attachment filters. (btw: a tar.gz usually goes through easier than a > zip) I have several other email address though. [EMAIL PROTECTED], > [EMAIL PROTECTED], etc > > In general, if it can be attached to a JIRA, that's probably the better > option. Then the issue can get properly tracked. >
item with xmlns="" testcase
I have created a test case for the problem, but every time i try to send to Dan or to cxf-user mailing list the mail with the TestCase, the mail returns back with the message: Remote host said: 552 Message rejected as it is spam (body) How can i send the zip (that's very small, 13k)? Marco.
Re: item element with xmlns=""
Thank you Dan for your quick answer. I already tried with CXF-2.0.4 (RC) but the behaviour seems to be the same as the 2.0.3 version. Marco. Quoting Daniel Kulp <[EMAIL PROTECTED]>: Any chance you could check with the 2.0.4 release candidates available at: http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator/ There were definite issues with Exceptions not working correctly with qualified schemas in 2.0.3. They should (hopefully) be fixed there. Dan On Thursday 24 January 2008, Marco Piraccini wrote: I need to expose a service (java-first) with CXF with an exception (EchoComplexException ) that includes an array of object (of class EchoStruct). The service is setted with: anonymousWrapperType, qualifyWrapperSchema ad wrapped to true. The wsdl generated seems to be correct, with a wrapper EchoComplexException of the type: The problem is that, on object deserialization, the EchoComplexException is serialized in: http://www.w3.org/2001/XMLSchema-instance";> true ...that's correct, except for the xmlns="" item namespace. Of course the schema validation fails. Anyone meet the same problem? Marco. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
item element with xmlns=""
I need to expose a service (java-first) with CXF with an exception (EchoComplexException ) that includes an array of object (of class EchoStruct). The service is setted with: anonymousWrapperType, qualifyWrapperSchema ad wrapped to true. The wsdl generated seems to be correct, with a wrapper EchoComplexException of the type: nillable="true" type="tns:echoStruct"/> The problem is that, on object deserialization, the EchoComplexException is serialized in: xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> true ...that's correct, except for the xmlns="" item namespace. Of course the schema validation fails. Anyone meet the same problem? Marco.
Jaxb char mapping
I'm using CXF with jaxws and jaxb. My problem is that the "char" java types are mapped to xs:unsignedShort (instead of xs:string with size 1 as i expected). I read the jaxb 2.0 specs, but the char primitive type mapping seems not to be defined. There is a quick way to configure/customize jaxb to map char to xs:string? Bye, Marco.
CXF-2.0.4 release?
I'm waiting for CXF-2.0.4 (i'm interested in the correction of the CXF-1332 issue). According with the roadmap, this version was targeted for Jan 15, but it's not downloadable yet. It's a simply few day late, or the release has been postponed? Bye Marco.
