Problem getting unexpected element name returned to client

[acxsjones]

I have work through examples and have a simple hello world working gen'd from an EJB.

I am trying to get a complex EJB, with my objects in and out, working. I am able to get the server deployed and get the client compiled. The client sends the request server. The server prints out the information.

The client gets an error "Caused by: unexpected element name: expected=result, actual=(http://helloworld2.ejb.test.acxiom.com/types}HelloReply

It looks like the client is looking for a "result" but getting my actual object.

Any help would be great

[acxsjones]

Let me add the wscompile from server and client

server wscompile

<wscompile fork="true"
 base="${build.dir}"
 features="rpcliteral"
 sourceBase="${src.dir}"
 keep="true"
 server="true"
 model="${src.dir}/com/acxiom/test/ejb/helloworld2/META-INF/HelloWorld.xml.gz"
 mapping="${src.dir}/com/acxiom/test/ejb/helloworld2/META-INF/mapping.xml"
 nonClassDir="${src.dir}/com/acxiom/test/ejb/helloworld2/META-INF/wsdl"
 config="${config.dir}/HelloWorld2-config.xml"
 verbose="true"
 xprintstacktrace="true">
 <classpath refid="build.classpath"/>
 </wscompile>

client wscompile

<wscompile keep="true"
 client="true"
 base="${build.dir}"
 sourceBase="${src.dir}"
 verbose="true"
 xprintstacktrace="true"
 features="rpcliteral"
 config="${wsdl.dir}/HelloWorld2-config.xml">
 <classpath refid="wspack.classpath"/>
 </wscompile>

[md5georg]

Hello,

I am guessing you are using jboss 4.0.0 or 4.0.1sp1? In this case, it is a bug and it is fixed in the 4.0.2RC1 which you can find here:

http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942


If you can not, for legacy reason or you just do not want to use an RC :), change to 4.0.2 you can implement an type mapping override with the correct 'result' in the ws4ee-deployment.xml descriptor as described here:

http://www.jboss.org/wiki/Wiki.jsp?page=WSTypeMapping

The easiest way of doing it is to copy the type mapping from an already deployed wsdd file (JBOSS_HOME/server/<server nam>/data/wsdl//...), then change the 'returnQName' as follows:

returnQName='result'

This did resolve my problems.

Best regards,

Georg

[thomas.diesler]

The override mechanism to the generated WSDD is the ws4ee-deployment.xml descriptor. You can create this additional descriptor and copy your modified type-mapping to it.

[platinumdragon]

"md5georg" wrote:

I am guessing you are using jboss 4.0.0 or 4.0.1sp1? In this case, it is a bug and it is fixed in the 4.0.2RC1 which you can find here:

http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942

I am running across the same problem, but 4.0.2RC1 produces the same error. Is this planned for the 4.0.2 final?

Thanks,
Mike

[platinumdragon]

Hmm,

I can't get the ws4ee-deployment.xml override to work either. Rather, it works in that it replaces the instances in the wsdd file on the server, but I get the same message. It looks like "result" is still in the "message-part" tag in the jaxrpc-mapping.xml.

Thanks,
Mike

[md5georg]

That is strange.... I did not have any problems at all using 4.0.2 RC1 (+others if you search this forum).

Can you please post some information about it, client error message (stack trace), wsdd snippet for the returned object, soap response, etc...


Best regards,

Georg