[#MULE-3434] CXF Transport doesn't work for frontend

Mule

CXF Transport doesn't work for frontend

Created: 05/Jun/08 06:44 AM Updated: 12/Nov/08 08:59 PM

Component/s:

Transport: CXF / XFire

Affects Version/s:

2.0.0

Fix Version/s:

2.1.x Backlog

Time Tracking:

Not Specified

File Attachments:	1. CXFTests.java (0.9 kB) 2. mule-config.xml (0.8 kB) 3. SimpleService.java (0.1 kB)
Environment:	Mule 2.0.0 and Mule 2.0.1, JDK1.6.0_06, Windows XP SP2

Labels:	20-ws
User impact:	High
Effort points:	4
Configuration:	« Hide <cxf:connector name="cxf" defaultFrontend="simple" /> <cxf:endpoint name="PatientList" address="http://localhost:8888/services" synchronous="true" /> <model name="MuleService"> <service name="Database"> <inbound> <cxf:inbound-endpoint ref="PatientList" serviceClass="db.GenerateRandom"/> </inbound> </service> </model> Show » <cxf:connector name="cxf" defaultFrontend="simple" /> <cxf:endpoint name="PatientList" address="http://localhost:8888/services" synchronous="true" /> <model name="MuleService"> <service name="Database"> <inbound> <cxf:inbound-endpoint ref="PatientList" serviceClass="db.GenerateRandom"/> </inbound> </service> </model>
Log Output:	« Hide org.apache.cxf.interceptor.Fault: NO_MESSAGE_FOR_PART. There is no problem to get the WSDL file. Show » org.apache.cxf.interceptor.Fault: NO_MESSAGE_FOR_PART. There is no problem to get the WSDL file.
Affects Docs:	Yes

Description

« Hide

When deploy a POJO Web Service through CXF, Client can't send request to it. This error will occur at server side:org.apache.cxf.interceptor.Fault: NO_MESSAGE_FOR_PART.

There is no problem to get the WSDL file.

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Daniel Feist added a comment - 10/Jul/08 07:28 AM

Can you review this quickly Dan?

[ Permlink | « Hide ]

Dan Diephouse added a comment - 10/Jul/08 09:43 AM

It looks like there is some mismatch between the client and server configuration. Can you tell me how you configured the client?

[ Permlink | « Hide ]

Antoine Borg added a comment - 18/Jul/08 07:57 AM

mule-config.xml = Bare-bones Mule config containing one service that has a CXF inbound endpoint.

[ Permlink | « Hide ]

Antoine Borg added a comment - 18/Jul/08 07:58 AM

SimpleService.java = the hosted component for the test Mule config

[ Permlink | « Hide ]

Antoine Borg added a comment - 18/Jul/08 07:59 AM

CXFTests.java = FunctionalTestCase for the test Mule config

[ Permlink | « Hide ]

Antoine Borg added a comment - 18/Jul/08 08:04 AM

I've uploaded three files to replicate this issue.

01 - the Mule config is enough to cause this error. This Mule app hosts the class in SimpleService.java.
02 - The FunctionalTestCase will use the Mule config; run everything and it will pass. This is important as it suggests that the problem may be a browser related issue.

If you launch Mule with the attached config and invoke it from a browser like this:

http://localhost:1234/myService/processInput/myInput/Antoine

the result in the browser window is:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>NO_MESSAGE_FOR_PART</faultstring></soap:Fault></soap:Body></soap:Envelope>

The WSDL works w/o problems

I'm using Firefox 2.0.0.16 running on WinXP but the fault appears on IE 7 too.

Mule 2.0.1
Java 1.6.0_03

What else do you need Dan?

[ Permlink | « Hide ]

youhaodeyi added a comment - 18/Jul/08 08:46 PM

I use your code and invoke the server in both Firefox 2.0.0.14 and IE 7 and got the same error:
org.apache.cxf.interceptor.Fault: NO_MESSAGE_FOR_PART

[ Permlink | « Hide ]

Dan Diephouse added a comment - 19/Jul/08 08:37 AM

There is a bug in CXF where the simple frontend doesn't work with the HTTP GET. Please see https://issues.apache.org/jira/browse/CXF-1471 and vote on it.