Our web services are developed from a WSDL file using JWSDP 1.6 and deployed into JBoss. Everything worked fine till we tried the new JBoss 4.0.3 SP1 version. SAXException: ?invalid parameter in <request type name>? was thrown when some of our methods were invoked. After investigation we figured out that the cause of the problem is a single lower case letter in front of the parameter name i.e. ?aParam? parameter name leads to exception, but ?anyParam? works fine.

You will find two files are listed below. It is a contract of simple test web service that has one method with two input parameters wrapped as a document literal request type. If a test web service will be build based on those two files then an exception is thrown (the exact exception is listed below). To avoid the exception the first parameter ?aFirstParam? should be renamed (e.g. ?firstParam?).