Mailing-List: contact tuscany-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tuscany-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of for.svkrish@gmail.com
 designates 72.14.204.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=WprSF/MKUvbvABrjOPGB12waXHSVZlfzchgEzhMLVLERrk+fEuOJEaflO0kA7xkWmJYXgECxvpKMHs3DeO1j4pwT79YzX335VxWEEoahHUEnefHui7QkM9zKXcDFSixD/gVnUqo4Pdhic78FkZCLJ4EIbLIn4SOifFJdQl9bZ38=
Message-ID: <33e260400802292335g43d9d525odff2a5a9868b2714@mail.gmail.com>
Date: Sat, 1 Mar 2008 13:05:22 +0530
From: "Venkata Krishnan" <for.svkrish@gmail.com>
To: tuscany-dev@ws.apache.org
Subject: Re: Trouble with aggregating definitions.xml in distro
In-Reply-To: <47C836EE.7000604@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_37704_28112932.1204356922743"
References: <33e260400802241712l2124bedbw89873921aa2bebba@mail.gmail.com>
	 <71e1b5740802282339u505f060u6ebb0d6ecddf602b@mail.gmail.com>
	 <c0c051b50802290108g5e0fa556lb579a2f95e1d5a1a@mail.gmail.com>
	 <33e260400802290358o7f237832s7978ee90fa163442@mail.gmail.com>
	 <c0c051b50802290422q91c9a59q4548f4f4ade4683b@mail.gmail.com>
	 <33e260400802290452m5d02de05ka0009eafc9aa030c@mail.gmail.com>
	 <47C82FFC.2090302@apache.org>
	 <CEB3BB1D648341DF933B59D2015E41F6@rfengt60p>
	 <47C83620.3050409@apache.org> <47C836EE.7000604@apache.org>

------=_Part_37704_28112932.1204356922743
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Sebastien,

Yes, I will try the scenarios you have mentioned and see if things work fine
with the transformer.

Please see my comments inline for the discussion specific to this thread.

Thanks

- Venkat

On Fri, Feb 29, 2008 at 10:16 PM, Jean-Sebastien Delfino <
jsdelfino@apache.org> wrote:

> Jean-Sebastien Delfino wrote:
> > Raymond Feng wrote:
> >> My understanding is that there are two different issues here:
> >>
> >> 1) Where definitions.xml should be packaged in a SCA contribution?
> >> 2) How do we merge multiple definitions.xml when we build the
> >> all-in-one binary distro?
> >>
> >> So I assume Sebastien's proposal is for 1) and the maven/shade
> >> discussion is for 2).
> >>
> >> Am I right? If yes, we should have two separate threads as it becomes
> >> confusing.
> >
> > My proposal handled 1 (not forcing definitions.xml to be in a fixed
> > location in the JAR) and 2 (as it didn't require any XML merging).
> >
> > My latest comments below in this email apply to 2 (I'm basically saying
> > "if you really want to do this XML merging, then make sure it works").
> >
> > I'm branching a new thread for 1 :)
> >
>
> Here's your new thread, starting with two statements:
>
> I think that contributors should be able to place their definitions.xml
> files wherever they want in an SCA contribution JAR.


I suppose that's the way it is right now.  The definitions.xml is processed
as any other artifact in a contribution and can be anywhere.

Its only for the definitions.xml file we are packaging in the tuscany
modules - as part of the runtime do we have the issue of placing them in a
well know place.  This is because these definitions.xml  1) don't get to be
treated as a contribution artifact 2) they need to be read before
contribution artifacts are read and resolved.  So to load them during the
runtime startup we are using the ServiceDiscovery to locate all
definitions.xml across Tuscany modules and the ServiceDiscovery needs to be
give a specific location.


>
> I also think that we'll have to support external policy attachments at
> some point (see the Open CSA POLICY-15 JIRA already discussed on
> tuscany-dev on other threads), and these policy attachments won't be in
> a fixed place in the contributions either.
>

I guess these attachments would get to be treated the same way as
definitions.xml in the sense, as any other artifact.


>
> --
> Jean-Sebastien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

------=_Part_37704_28112932.1204356922743--