Return-Path: 
 <dev-return-45130-apmail-tuscany-dev-archive=tuscany.apache.org@tuscany.apache.org>
Delivered-To: apmail-tuscany-dev-archive@www.apache.org
Received: (qmail 91477 invoked from network); 3 Feb 2010 19:40:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 3 Feb 2010 19:40:14 -0000
Received: (qmail 86944 invoked by uid 500); 3 Feb 2010 19:40:13 -0000
Delivered-To: apmail-tuscany-dev-archive@tuscany.apache.org
Received: (qmail 86891 invoked by uid 500); 3 Feb 2010 19:40:13 -0000
Mailing-List: contact dev-help@tuscany.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@tuscany.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@tuscany.apache.org>
List-Post: <mailto:dev@tuscany.apache.org>
List-Id: <dev.tuscany.apache.org>
Reply-To: dev@tuscany.apache.org
Delivered-To: mailing list dev@tuscany.apache.org
Received: (qmail 86883 invoked by uid 99); 3 Feb 2010 19:40:13 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 19:40:13 +0000
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 luckbr1975@gmail.com
 designates 209.85.216.202 as permitted sender)
Received: from [209.85.216.202] (HELO mail-px0-f202.google.com)
 (209.85.216.202)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 19:40:07 +0000
Received: by pxi40 with SMTP id 40so1839771pxi.21
        for <dev@tuscany.apache.org>; Wed, 03 Feb 2010 11:39:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=hcTVH+Z5PijiFrn9jJnz3maP68awUnEfS1sVVfz4sqs=;
        b=r8NeJ7VYoXgFauJp6MuB7oUE07NxIz7kuTRu/3zCc5Dd9E4MVLpPe8r7F30BsN/tQQ
         qRhB30oZZRxcq7zumrl5aKjp53i/HDzqftKp84xle9b+M449aCcai/bNG4k9LVtrSsKP
         P9fwUtfHiiVl1biHi1FzLQ1tY71gHbYxK71Gs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=qiFL8QZIpf+ByMXN1zGq8Tb52V5oKtrdSnJQTB/LQ+rzNGx0dMsAlZqpUUuyEf0lmX
         4IVpA8aVIfy0k9lQnt6IPsQegd6D/aykaNLO7jkoJmXGivJjfR3mBkIP115rGOk7ojf+
         0/NGb+9AIo7wlxUVjpemTWizvORz8sMsGC5s0=
MIME-Version: 1.0
Received: by 10.140.56.14 with SMTP id e14mr48572rva.19.1265225986825;
 Wed, 03
	Feb 2010 11:39:46 -0800 (PST)
In-Reply-To: <c0c051b51002031116v88b05c6wbb47d91676cc216e@mail.gmail.com>
References: <5a75db781002021551y3094f918pa16aa09c75d2187a@mail.gmail.com>
	 <c0c051b51002031116v88b05c6wbb47d91676cc216e@mail.gmail.com>
Date: Wed, 3 Feb 2010 11:39:46 -0800
Message-ID: <5a75db781002031139s1bc47766l365c70cbeba2abe4@mail.gmail.com>
Subject: Re: Handling Extensions with latest OASIS 1.1 Schema
From: Luciano Resende <luckbr1975@gmail.com>
To: dev@tuscany.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 3, 2010 at 11:16 AM, Simon Laws <simonslaws@googlemail.com> wro=
te:
> I suppose the potential confusion is that
>
>
> =A0 =A0 =A0 <component name=3D"Catalog">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 <implementation.java class=3D"services.Fruits=
CatalogImpl"/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 <property name=3D"currencyCode">USD</property=
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 <service name=3D"Catalog">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <tuscany:binding.jsonrpc/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 </service>
> =A0 =A0 =A0 </component>
>
> Wouldn't warn the user that they've put the binding in the wrong place
> (what does the spec say about this?).
>
> Simon
>

In this case specific, the XML is valid, because there is a XSD
specifying the JSON-RPC binding, but the runtime might not find a
processor for handling this, and in order to allow the runtime to
produce semantically same xml output when writing it back, we store
this in the element extension list which causes the confusion when
writting it back.

--=20
Luciano Resende
http://people.apache.org/~lresende
http://lresende.blogspot.com/