Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of linsun.unc@gmail.com
 designates 74.125.82.182 as permitted sender)
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=wENLdZbJDkHR7U0IubTdwH/RoXilhoO9B+NTXOedv+eWpoEgMd/lhN3+rojNZcmEG1
         vW0tmNJe1b7dQqYG9yzI6zeRZ6ZMm2LDmXQz4MHtZ4/3gc4OY9nocnl8FMzDSulP8H6g
         9sqzw+DJCbkRQwWr108NFpTxAWuKc+oVFEcE0=
MIME-Version: 1.0
In-Reply-To: <AANLkTimJqphYwyie2wmk_hBdYa0E0uPUBQx24HhVErAS@mail.gmail.com>
References: <AANLkTim7Q-oKhH8L+ea1P0inzqZ7V4pDGCeXwFP1Xc3i@mail.gmail.com>
	<AANLkTims6_34dkXUuG2v=u7afuPW8bc+agz+Tib8AY2k@mail.gmail.com>
	<AANLkTimJqphYwyie2wmk_hBdYa0E0uPUBQx24HhVErAS@mail.gmail.com>
Date: Fri, 20 Aug 2010 14:29:07 -0400
Message-ID: <AANLkTi=kqQNa2cfRG8pMwoTbYaRJ5iNQaNUS9vo+X5rK@mail.gmail.com>
Subject: Re: [discuss]Web profile assemblies
From: Lin Sun <linsun.unc@gmail.com>
To: dev@geronimo.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Ok, regarding tranql RAs, the derby ones are pulled in by
system-database.  The other RAs are pulled in as part of the
db-connectors plugin which is part of the eba-tomcat plugin group.

I think we are fine to keep these RAs in, if we want to support these
different dbs like db2, oracle, sql server, etc in our web profile
assembly.

Lin
> 2. tranql: i cannot think of a reason why these resource adapters are
> needed for web profile... I can see geronimo-connector are needed but
> not the RAs. =A0 Maybe people who knows more about tranql could comment
> on this?
>
> Anything else I missed on this topic?
>
> Thanks
>
> Lin
>
> On Fri, Aug 20, 2010 at 11:30 AM, Jarek Gawor <jgawor@gmail.com> wrote:
>> On Fri, Aug 20, 2010 at 10:09 AM, Lin Sun <linsun.unc@gmail.com> wrote:
>>> Hi
>>>
>>> I am checking at our web profile assemblies to ensure it met the
>>> requirements for Java EE 6 web profile and prune the unnecessary
>>> artifacts. =A0 I've been mainly look at the tomcat7-javaee6-web and I
>>> have some comments/questions:
>>>
>>> felix core: i assume we'll always ship 2 osgi runtime?
>>
>> Yep, that's the plan.
>>
>>> connector (geronimo-connector, geronimo-connector-builder, connector
>>> spec): =A0I think openejb uses connector, so we may have to keep it in.
>>>
>>> java ee management 1.1: =A0 Unchanged from Java EE 5. =A0I assume this =
is
>>> provided by geronimo-management. =A0Not sure if we could remove this?
>>>
>>> java ee deployment 1.2 related: =A0Unchanged from Java EE 5. =A0 we may
>>> have to keep it in, to keep existing deployment work.
>>>
>>> geronimo-javamail: can we get rid of it? =A0think the answer is yes.
>>
>> Maybe. Might be nicer to include it.
>>
>>> geronimo-jaspi: can we get rid of it? =A0think the answer is yes.
>>
>> Maybe. Might be nicer to include it.
>>
>>> geronimo-webservices, geronimo-webservices-builder: =A0think we could
>>> remove these.
>>
>> Yes, i think so.
>>
>>> geronimo-yoko, yoko: think we could remove these.
>>>
>>> spec jars: we seems to include all specs in web profile assembly.
>>> things that can be removed: =A0aspic, jaxr, jaxrpc, jaxws, dims, saaj,
>>> ccpp?
>>
>> I don't think this is very important. A lot of specs have dependencies
>> on each other. So this might be a mess to sort it all out. I think we
>> should be able to include them all even though we don't provide all of
>> that functionality. At runtime an user should see an error that a
>> given provider is not found.
>>
>>>
>>> mina: think we could remove it... not sure which web profile function
>>> it related to.
>>
>> It's not related to web profile. It used so one can remotely login to
>> Karaf/Geronimo shell. So this should be totally ok.
>>
>>> ops4j, pax-loggin-api, pax-url-mvn, pax-url-wrap: think these are just
>>> test dependencies that were put into the assembly incorrectly.
>>
>> Again, not related to web profile. And these are used at runtime. We
>> need them. Expect maybe pax-url-wrap.
>>
>>> tranql: think we could remove it.
>>>
>>> openejb: anything we could do so that we can just have the ejb-lite fun=
ction?
>>>
>>> pluto/portal: I assume these are needed for admin console so we need it=
.
>>
>> Right. Shouldn't matter for web profile.
>>
>> Jarek
>>
>