Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 21045 invoked from network); 28 Mar 2008 22:59:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Mar 2008 22:59:57 -0000 Received: (qmail 84494 invoked by uid 500); 28 Mar 2008 22:59:49 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 83668 invoked by uid 500); 28 Mar 2008 22:59:46 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 83657 invoked by uid 99); 28 Mar 2008 22:59:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2008 15:59:46 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nate.roe@vegas.com designates 192.5.73.230 as permitted sender) Received: from [192.5.73.230] (HELO mail.vegas.com) (192.5.73.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2008 22:59:06 +0000 DomainKey-Signature: s=vegas.com; d=vegas.com; c=nofws; q=dns; h=From:X-IronPort-AV:Received:To:Date:Subject:Thread-Topic: Thread-Index:Message-ID:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage: Content-Type:Content-Transfer-Encoding:MIME-Version; b=S9EQo+E+jVUO2rVLmHRGKTvYQ9EUfVSQg7u8yMPHbzCMvt/4g+zpEiyb 1rDVOALETGnkxLQtwwQuV7D2xpmcQeLFyg/7a7YzwH4GwOoph03TIUQmh su2MA6YT4KhbVuxlmUXYtB8Mph/LcSKjbBTaDAStWJOewm7YVYY2TO2eA U=; From: Nate Roe X-IronPort-AV: E=Sophos;i="4.25,572,1199692800"; d="scan'208";a="16345588" Received: from CORP-EXCHMAIL.corp.vegas.com ([10.25.16.65]) by corp-exchht02.corp.vegas.com ([10.25.16.62]) with mapi; Fri, 28 Mar 2008 15:59:18 -0700 To: "'axis-user@ws.apache.org'" Date: Fri, 28 Mar 2008 15:59:18 -0700 Subject: Is it wise to deploy a service as a POJO with Axis2? Thread-Topic: Is it wise to deploy a service as a POJO with Axis2? Thread-Index: AciRJ1ozn3wFV99PQjmunG4dQA/yyA== Message-ID: <104359CE43F38E40AEEEB91286AA749C47248E9E85@CORP-EXCHMAIL.corp.vegas.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org 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= 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 --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org