| Summary: | Argument List with Nil | ||
|---|---|---|---|
| Product: | gRAVI | Reporter: | Josh <JRBoverhof@lbl.gov> |
| Component: | gRAVI | Assignee: | Josh <JRBoverhof@lbl.gov> |
| Status: | NEW | ||
| Severity: | normal | CC: | madduri@mcs.anl.gov |
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
The generated client code produces a "example" argument list which contains an array with the last item not initialized. This causes an problem on the server-side when one attempts to actually use them. This is easy enough to fix, but why should the schema even allow a "null" argument to be transmitted. String [] arguments = new String [6]; arguments [0] = "-file"; arguments [1] = "{ipfile}"; arguments [2] = "-testparam"; arguments [3] = "value"; arguments [4] = "-testparam2"; <soapenv:Body> <LsRequest xmlns="http://helloworld.introduce.cagrid.org/HelloWorld"> <arguments>-file</arguments> <arguments>{ipfile}</arguments> <arguments>-testparam</arguments> <arguments>value</arguments> <arguments>-testparam2</arguments> <arguments xsi:nil="true"/> </LsRequest> </soapenv:Body>