On Wednesday 25 July 2007 22:41:12 Corey Puffalt wrote: > Chris, Daniel, > > I don't suppose there's any chance of CXF introducing a configurable option > to use non-conforming (but more reasonable IMHO) default parameter names? > Am I the only one that sees the default parameter names as something akin > to obfuscation of the WSDL file? I've sent a comment to the JSR224 email > address but I doubt anything will come of it.
I would also like to see something such as this in a future release. While one may say CXF is conformant to the spec, the spec does seem a bit lacking in this specific matter. Having "argN" parameter names isn't very descriptive when auto-generating frontends to SOAP services, and having to document each parameter with @WebParam(name="Xyz") to overcome this is quite excessive. Especially with large services with several hundred parameters -- the interface classes become quite messy with all the extra annotations, and prone to problems of names going out of sync when adding/modifying parameters. Having a single on/off flag (default off) in the CXF configuration to allow the "non-conformant" behaviour of mirrored interface/WSDL parameter names would be exceptionally useful for circumstances such as these. ______________________________________________________________________ Complinet Ltd is registered in England. Registered office at Vintners Place, 68 Upper Thames Street, London EC4V 3BJ. Company number 3170722. VAT No. 749 324 021. Complinet Inc is a corporation registered in Delaware, USA. This email has been scanned by the MessageLabs Email Security System.
