there ist a related JIRA bug (http://jira.jboss.com/jira/browse/JBWS-442) that is marked as resolved in version 1.0RC3 but I have the same problem in version 1.0.0.GA.
Is this still an open issue?
Workaround: The temporary wsdl files in SERVER_DIR/data/wsdl are correct.
Thanks Klaus for the information. It seems like I can never get a response from anyone on this forum, I guess I do not ask advanced enough questions.
We are still having the problem even though we have seen it as being resolved as well. We are actually investigating using the WSDL to Java approach instead.
I think the question was enough advanced, but I am only a JBoss user. I still want to now, if this is a bug our a just a wrong way to use it.
We want to change our WSDL2Java aproach (based on AXIS) to Java2WSDL to make the development easier.
There is a testcase that covers @WebParam
tdiesler@satellite /cygdrive/d/svn/jbossws/trunk/src/test $ ant -Dtest=org.jboss.test.ws.jsr181.webparam.JSR181WebParamTestCase one-test one-test: [junit] Running org.jboss.test.ws.jsr181.webparam.JSR181WebParamTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.45 sec
Note, the test uses RPC. Are you seeing this issue with DOCUMENT?
No in our case it's RPC/LITERAL.
The testcase checks the services itself. We have the problem with the generated wsdl with a <wstools ... /> ant task.
The runtime wsdl generation works well.
I hope, this helps to understand the problem.