I've recently updated a web service from JBoss 4.0.2 to 4.0.5 with JBossWS 1.2.1, and it's causing problems. The new setup enforces the proper naming of method parameters, instead of just taking them positionally.
Some older clients don't send the proper parameter names. For example, Axis generated clients just call them "in0", "in1", "in2", etc. Whereas the old server happily accepted this, the new one throws a NotFound exception because the WSDL lists them as "String_1", "String_2", and so on. Is there any way to stop enforcing parameter names? The WSDL specifies the proper order, and this is all we need. It is important so remain compatible with old clients without changing the WSDL. Thanks, Bruce View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051378#4051378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051378 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
