required arguments in Flex 1.5 - kills webservice

[Bob A]

I am running Flex1.5 with Tomcat 5.0. I dropped the samples.war file in webapps
and everything worked great.

I am planning to use on example, the NamedWebServiceDemo, with mods as my
first application. I simply recompiled the EmployeeManager.java file in
{tomcat}\webapps\samples\WEB-INF\classes\samples\explorer in preparation for
actually changing it a bit. NOW the application fails with the message:

Required parameter 'in0' not found in input argument.

I did find one reference to this error
([url]http://www.macromedia.com/support/documentation/en/flex/1_5/migration.html[/url])

message stating that 1.5 enforces arguments. I did not change arguments for
anything and this should still work. I decompiled the included class file and
it is, except for variable names, identical to the file EmployeeManager.java
file that I have.

I am stuck! I do not see how to get around this behavior.

[thymecd@sina.com]

I met the same problem.
My previous code:
<mx:operation name="updateUser">
<mx:request>
<id>{dg.selectedItem.id}</id>
<name>{txtname.text}</name>
<password>{txtpass.text}</password>
<age>{txtage.text}</age>
</mx:request>
</mx:operation>
But it did not work.
My current code:
<mx:operation name="updateUser">
<mx:request>
<in0>{dg.selectedItem.id}</in0>
<in1>{txtname.text}</in1>
<in2>{txtpass.text}</in2>
<in3>{txtage.text}</in3>
</mx:request>
</mx:operation>
It runs correctly now.
I am not sure why. But I think, user who invoke the web service should
not know the arguments' name of the remote method. So we should depend
on the position of the arguments, not the name of the arguments to
match the remote method.