Mailing-List: contact scout-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: scout-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=45dHj/zY1IMiObWNECRDv05tYdrtGrDk7yHsTAjC7UcEXMtacND7RdQdqIkUVKFPIHJawzFrdt269t4IvWI/kp+pvPC0UOW8w+9BKlHu1KNaX6EjUDa7Z2i4al9buSj3LSTcH20/MzZgPyQX4R7zxeuyh2AzfYr2Kx+IQflN7/M=
  ;
Message-ID: <20050818151412.40178.qmail@web52113.mail.yahoo.com>
Date: Thu, 18 Aug 2005 08:14:12 -0700 (PDT)
From: Anil Saldhana <anilsaldhana@yahoo.com>
Subject: Re: Scout and jUDDI
To: juddi-dev@ws.apache.org, scout-dev@ws.apache.org
In-Reply-To: <679af1b505081807144cfd025@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

The goal for Scout is to be Level 0 Jaxr compliant.
Lets get that to work satisfactorily.  For that to
happen, users have to use it in production.

I do not see any immediate need for Apache Scout to be
Level 1 compliant (read ebxml compliance). There is an
open source implementation of ebxml (ebxmlrr) that
provides JAXR capabilities also.

We will propose Level 1 work in Scout when there are
users asking for it.

Scout/jUDDI combo passes the J2EE 1.4 TCK (JAXR
Tests). This has been confirmed by seperate tests from
Apache and JBoss.

Steve,  I did not get your point about jUDDI does not
intend to support ebxml (apples and oranges.  ;)  )  I
presume you were talking about the juddi proxy.

--- Steve Viens <sviens@gmail.com> wrote:

> Initially we developed Scout on top of jUDDI in
> order to quickly produce a 
> type 0 JAXR provider. Type 0 (zero) providers
> support accessing UDDI 
> registries only. The goal however is for Scout to
> become a type 1 provider 
> which would include support for both UDDI and ebXML
> registries. 
>  As you would probably expect, there are no plans
> for jUDDI to support 
> ebXML. If a move to an XMLBeans would enable Scout
> to support both UDDI and 
> ebXML (a type 1 provider) then I'm in favor of a
> move to XMLBeans and 
> eliminating Scout's dependency on jUDDI.
>  Steve 


____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org