There is a testcase that covers @WebParam
| [EMAIL PROTECTED] /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]
yep, 4.0.4.CR2 fixed the array problem.
It introduced problems with the JSR-181 annotations not working completely,
specifically the @webparam was not working correctly resulting in generated
wsdl that has arguments like DATE_1, or STRING_1
E
View the original post :
http://www.jboss.com/ind
"esvehla" wrote :
| We ended up moving to JBoss 4.0.4.CR2 which gets you past this problem but
we have a new set of problems.
|
Actually, that was going to my next question. Does 4.0.4 fix the problem with
arrays?
I have not considered starting from WSDL since I am actually exposing a bun
I feel your pain!
I have been through your problem on my current project. What we found is that
you had to manually manipulate the files which is not a solution for us.
We ended up moving to JBoss 4.0.4.CR2 which gets you past this problem but we
have a new set of problems.
Have you done any
