I agree with Mauro's analysis. We had the same issues in our implementation, but Axis2 is getting better with respect to POJO services with each release (some of the recent resolved jiras have greatly increased WSDL quality, but there are still namespace issues, WS-I BP 1.1 compliance issues, etc.)
Bottom-line: Though code-first is convenient initially, contract-first is the way to go with Axis2 and an accepted best practice. -----Original Message----- From: Mauro Molinari [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2008 11:17 AM To: [email protected] Subject: Re: Is it wise to deploy a service as a POJO with Axis2? Nate Roe ha scritto: > I wonder this in part because of the issue that I reported > (https://issues.apache.org/jira/browse/AXIS2-3655, where a service > returning a List<Person> fails to generate appropriate WSDL.) My > attempts to correct the WSDL and then regenerate the client resulted > in other difficult-to-diagnose (for me) problems. > > So I wonder if this is a common approach? Have I chosen a rough road? > > Thanks, Nate Roe IMHO, Axis2 is not mature enough to be used to publish bottom-up services in a production-quality environment. There are too many almost blocking issues with it. After trying to do that, we actually changed our direction and opted for the top-down approach. Not easy, anyway, but you can have much more control on what you expose and implement. -- Mauro Molinari Software Developer [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
