rpc/literal generates soap encoded array

[rparree]

Hi,

I have a basic example that is not doing what it is suppose to do. I am running a few tests on multiple WS platforms, and I can?t get this one to work with JBossWS (JBoss 4.0.2 have tried 4.0.3 RC1 as well)
I am using org.jboss.axis.wsdl.Java2WSDL with flags turned on for RPC and LITERAL. The only method in my SEI looks like:

public String[] doIt(Customer i) throws RemoteException;

When running the Java2WSDL it is generating a soap encoded array for th String[].

Is the JBossWS based on Axis1.1 or on 1.2? Using Java2WSDL from Axis1.1 gives same results, Axis1.2 produces the expected result (which is a BP1.1 compliant web service description).

I am aware that i could (or is it should) be using wscompile, but in this scenario i have no special requirements for the WSEE mapping file.

Is this as expected or i am missing something?

Raphael

[jason.greene]

Dont use the axis tools, use wscompile.

-Jason

[rparree]

Hi,

Thanks Jason for your reply.

Are there any licensing problems using and relying on wscompile. Wscompile is part of the jaxrpc-impl.jar which is listed on http://java.sun.com/webservices/docs/1.6/ReleaseNotes.html#RedistributableComponents
and further explained in the
http://java.sun.com/webservices/docs/1.6/LICENSE SUPPLEMENTAL LICENSE TERMS. It seems that it is all or nothing, and that extending the functionality is not allowed without approval from sun.

Tx.,

Raphael

[thomas.diesler]

We recommend to use the Sun tool wscompile (like you would use javac) until we have our own tool set ready to be used with jboss.

The Axis toolset does not generated J2EE compliant artifacts.