Forum Discussion
redfish4ktc2
11 years agoSuper Contributor
Hi,
it seems the problem comes from the class name. In your example, it starts with a lower case. I am definitely not a Groovy expert but I found what you try to achieve seems not supported in groovy (see http://groovy.329449.n5.nabble.com/Clas ... 72450.html)
I guess you should be able to reproduce this outside of SoapUI but not with a java main program as you previously did (use a real groovy script)
could you try to redo a test with a class starting with a upper case letter? This will also follow the Java/Groovy conventions so it should not be an issue in terms of naming :-)
you could also try to replace
it seems the problem comes from the class name. In your example, it starts with a lower case. I am definitely not a Groovy expert but I found what you try to achieve seems not supported in groovy (see http://groovy.329449.n5.nabble.com/Clas ... 72450.html)
I guess you should be able to reproduce this outside of SoapUI but not with a java main program as you previously did (use a real groovy script)
could you try to redo a test with a class starting with a upper case letter? This will also follow the Java/Groovy conventions so it should not be an issue in terms of naming :-)
you could also try to replace
access ac = new access()by
def ac = new access()(may work: http://osdir.com/ml/lang.groovy.user/20 ... 00159.html)
Related Content
- 6 years agosanj
- 4 years agoMarkSchofer
- 3 years agomlipanje
- 4 years agoFabriZio