Return-Path: Delivered-To: apmail-ws-juddi-dev-archive@www.apache.org Received: (qmail 7522 invoked from network); 1 Dec 2008 23:49:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2008 23:49:52 -0000 Received: (qmail 94970 invoked by uid 500); 1 Dec 2008 23:50:04 -0000 Delivered-To: apmail-ws-juddi-dev-archive@ws.apache.org Received: (qmail 94946 invoked by uid 500); 1 Dec 2008 23:50:04 -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 94935 invoked by uid 99); 1 Dec 2008 23:50:04 -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 15:50:04 -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 23:48:34 +0000 Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 01 Dec 2008 18:48:21 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.3-GA) with ESMTP id KME19516; Mon, 1 Dec 2008 18:48:14 -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 18:48:13 -0500 From: "Jeff Faath" To: , References: <004401c95402$d0ff7480$72fe5d80$@org> <182905.61027.qm@web52111.mail.re2.yahoo.com> In-Reply-To: <182905.61027.qm@web52111.mail.re2.yahoo.com> Subject: RE: jUDDI web services Date: Mon, 1 Dec 2008 17:48:03 -0600 Message-ID: <005801c9540f$413a1d20$c3ae5760$@org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0059_01C953DC.F69FAD20" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AclUBBqfCptWOH6/RrSkuZezwf+XlwACwO6Q Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0059_01C953DC.F69FAD20 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Yea, we'll probably test CXF out as well. Right now, I'm working on getting Axis2 to work which I am close to completing. From: Anil Saldhana [mailto:anilsaldhana@yahoo.com] Sent: Monday, December 01, 2008 4:27 PM To: juddi-dev@ws.apache.org Subject: RE: jUDDI web services http://cxf.apache.org/ supports JAX-WS. --- On Mon, 12/1/08, Jeff Faath wrote: From: Jeff Faath Subject: RE: jUDDI web services To: juddi-dev@ws.apache.org, anilsaldhana@yahoo.com Date: Monday, December 1, 2008, 4:19 PM 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_0059_01C953DC.F69FAD20 Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable

Yea, we’ll probably test CXF out as well.=A0 Right = now, I’m working on getting Axis2 to work which I am close to = completing.

 

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

 

http://cxf.apache.org/ supports = JAX-WS.  

--- On Mon, 12/1/08, Jeff Faath = <jfaath@apache.org> wrote:

From: Jeff Faath <jfaath@apache.org>
Subject: RE: jUDDI web services
To: juddi-dev@ws.apache.org, anilsaldhana@yahoo.com
Date: Monday, December 1, 2008, 4:19 PM

No, it=A2s 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

 <= /o:p>

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,

 

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.

 

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.

 

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

 

-JF

 

 =

------=_NextPart_000_0059_01C953DC.F69FAD20--