Return-Path: Delivered-To: apmail-ws-juddi-dev-archive@www.apache.org Received: (qmail 82131 invoked from network); 1 Dec 2008 22:19:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2008 22:19:46 -0000 Received: (qmail 94348 invoked by uid 500); 1 Dec 2008 22:19:57 -0000 Delivered-To: apmail-ws-juddi-dev-archive@ws.apache.org Received: (qmail 94324 invoked by uid 500); 1 Dec 2008 22:19:57 -0000 Mailing-List: contact juddi-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: juddi-dev@ws.apache.org List-Id: Delivered-To: mailing list juddi-dev@ws.apache.org Received: (qmail 94313 invoked by uid 99); 1 Dec 2008 22:19:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 14:19:57 -0800 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [207.172.157.102] (HELO smtp02.lnh.mail.rcn.net) (207.172.157.102) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 22:18:28 +0000 Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 01 Dec 2008 17:19:14 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.8.6-GA) with ESMTP id PHB50284; Mon, 1 Dec 2008 17:19:13 -0500 (EST) Received: from 24-148-56-77.snb-bsr1.chi-snb.il.cable.rcn.com (HELO faath) ([24.148.56.77]) by smtp01.lnh.mail.rcn.net with ESMTP; 01 Dec 2008 17:19:12 -0500 From: "Jeff Faath" To: , References: <001c01c9518f$3cb35a50$b61a0ef0$@org> <506037.89962.qm@web52102.mail.re2.yahoo.com> In-Reply-To: <506037.89962.qm@web52102.mail.re2.yahoo.com> Subject: RE: jUDDI web services Date: Mon, 1 Dec 2008 16:19:02 -0600 Message-ID: <004401c95402$d0ff7480$72fe5d80$@org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01C953D0.86650480" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AclT/b7RC5VTwkgnTbulPIWV10eHGAABICKg Content-Language: en-us X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090201.493462E1.01F1,ss=1,fgs=0, ip=207.172.4.11, so=2007-10-30 19:00:17, dmn=5.7.1/2008-09-02 X-Junkmail-IWF: false X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0045_01C953D0.86650480 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit No, it's for the v3 release. We are attempting to make the project WS-stack agnostic by using JAX-WS. However, given this is an Apache project, we feel it is important to get it to work with Axis2 and using that as the default runtime. From: Anil Saldhana [mailto:anilsaldhana@yahoo.com] Sent: Monday, December 01, 2008 3:42 PM To: juddi-dev@ws.apache.org Subject: Re: jUDDI web services the JAX-WS enabled WS is for your testing? or juddi testsuite will have it? If it just for you to proceed, then why not just try to make it JAX-WS and users will deploy it on their favorite runtime. --- On Fri, 11/28/08, Jeff Faath wrote: From: Jeff Faath Subject: jUDDI web services To: juddi-dev@ws.apache.org Date: Friday, November 28, 2008, 1:26 PM All, I was able to get further along in the investigation of getting the JAX-WS web services to work with Tomcat and Axis2. Turns out it wasn?t working before because Axis2 couldn?t properly deploy the services when classes were compiled into a jar. I think there is a way to configure Axis2 to deploy within a jar, but unfortunately there is a bigger issue. When trying to bring up the WSDL, I get a namespace conflict issue. Upon further investigation, it turns out we are getting hit by a flavor of WSCOMMONS-377. And this issue doesn?t look like it?s going to get fixed anytime soon. So, I?m not sure where to go from here. Any suggestions? -JF ------=_NextPart_000_0045_01C953D0.86650480 Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable

No, it’s for the v3 release.

 

We are attempting to make the project WS-stack agnostic = by using JAX-WS.=A0 However, given this is an Apache project, we feel it is = important to get it to work with Axis2 and using that as the default = runtime.

 

From:= Anil = Saldhana [mailto:anilsaldhana@yahoo.com]
Sent: Monday, December 01, 2008 3:42 PM
To: juddi-dev@ws.apache.org
Subject: Re: jUDDI web services

 

the JAX-WS enabled WS is for your testing?  = or juddi testsuite will have it? 

If it just for you to proceed, then why not just try to make it JAX-WS = and users will deploy it on their favorite runtime.

--- On Fri, 11/28/08, Jeff Faath = <jfaath@apache.org> wrote:

From: Jeff Faath <jfaath@apache.org>
Subject: jUDDI web services
To: juddi-dev@ws.apache.org
Date: Friday, November 28, 2008, 1:26 PM

All,

 <= /o:p>

I was able to get further along in the investigation of getting the = JAX-WS web services to work with Tomcat and Axis2.  Turns out it wasn=A2t = working before because Axis2 couldn=A2t properly deploy the services when = classes were compiled into a jar.  I think there is a way to configure Axis2 = to deploy within a jar, but unfortunately there is a bigger = issue.

 <= /o:p>

When trying to bring up the WSDL, I get a namespace conflict issue.  = Upon further investigation, it turns out we are getting hit by a flavor of WSCOMMONS-377.  And this issue doesn=A2t look like it=A2s going = to get fixed anytime soon.

 <= /o:p>

So, I=A2m not sure where to go from here.  Any = suggestions?

 <= /o:p>

-JF

 =

------=_NextPart_000_0045_01C953D0.86650480--