W dniu 09.03.2010 06:35, Coder One pisze:
One Request class with all parameters inside...better for evolution of 
signatures...



----- Original Message ----
From: Ron Grimes<[email protected]>
To: "[email protected]"<[email protected]>
Sent: Mon, March 8, 2010 9:21:39 AM
Subject: RE: good practices for @WebParam

I would argue that 5 separate parameters would be best. If for no other reason, 
it's easier to build test requests with a tool like SOAPUI.

Ron



We use in our company separate parameters and it works good. Aggregation class for request is also good solution - probably worthy of consideration. Both solutions are easy to test with SoapUI.

Regards,
Bartłomiej Chmielewski

Reply via email to