<div dir="ltr"><div>So cdi-se-api is larger than the (core) EE API?<br><br></div><div>An SE implementation should hopefully have a smaller footprint than current EE ones (e.g. Weld)?<br><br></div><div style="font-family:arial,helvetica,sans-serif">Werner<br><br></div><div><div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><span lang="EN-GB"></span></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Oct 18, 2016 at 11:09 AM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.<wbr>org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Spliting SE package in an independent jar (Martin Kouba)<br>
2. [JBoss JIRA] (CDI-45) Optional Injection Points<br>
(Martin Kouba (JIRA))<br>
3. [JBoss JIRA] (CDI-638) Introduce a new xsd for CDI 2.0<br>
(Antoine Sabot-Durand (JIRA))<br>
4. [JBoss JIRA] (CDI-638) Introduce a new xsd for CDI 2.0<br>
(Antoine Sabot-Durand (JIRA))<br>
5. No meeting tomorrow (Antoine Sabot-Durand)<br>
6. Re: Spliting SE package in an independent jar (Emily Jiang)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Thu, 13 Oct 2016 09:56:24 +0200<br>
From: Martin Kouba <<a href="mailto:mkouba@redhat.com">mkouba@redhat.com</a>><br>
Subject: Re: [cdi-dev] Spliting SE package in an independent jar<br>
To: John Ament <<a href="mailto:john.ament@spartasystems.com">john.ament@spartasystems.com</a>><wbr>, Antoine Sabot-Durand<br>
<<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>>, cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID: <<a href="mailto:616fdc4e-26f6-a8d7-16d3-fdceb71faa1f@redhat.com">616fdc4e-26f6-a8d7-16d3-<wbr>fdceb71faa1f@redhat.com</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
+1 for John's proposal.<br>
<br>
So there will be two API artifacts:<br>
* cdi-api<br>
* cdi-se-api (depends on cdi-api)<br>
<br>
Martin<br>
<br>
Dne 12.10.2016 v 12:40 John Ament napsal(a):<br>
> the way I've envisioned it:<br>
><br>
><br>
> - There is no dedicated EE API (none that I could find that is EE only,<br>
> except for perhaps session scoped)t<br>
><br>
> - There is SE specific API and the current API could be considered "core"<br>
><br>
><br>
><br>
> Take the current API module and create two submodules, one for core and<br>
> one for SE. SE depends on core. EE still refers to core as the same<br>
> existing coordinates (create new coordinates for the parent).<br>
><br>
> ------------------------------<wbr>------------------------------<wbr>------------<br>
> *From:* <a href="mailto:cdi-dev-bounces@lists.jboss.org">cdi-dev-bounces@lists.jboss.<wbr>org</a><br>
> <<a href="mailto:cdi-dev-bounces@lists.jboss.org">cdi-dev-bounces@lists.jboss.<wbr>org</a>> on behalf of Antoine Sabot-Durand<br>
> <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
> *Sent:* Wednesday, October 12, 2016 5:18 AM<br>
> *To:* cdi-dev<br>
> *Subject:* [cdi-dev] Spliting SE package in an independent jar<br>
><br>
> to avoid including CDI SE features in Java EE, we already talk about<br>
> creating a specific SE jar.<br>
><br>
> Any thought on this approach?<br>
><br>
> Antoine<br>
> ------------------------------<wbr>------------------------------<wbr>------------<br>
> NOTICE: This e-mail message and any attachments may contain<br>
> confidential, proprietary, and/or privileged information which should be<br>
> treated accordingly. If you are not the intended recipient, please<br>
> notify the sender immediately by return e-mail, delete this message, and<br>
> destroy all physical and electronic copies. Thank you.<br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/<wbr>licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
><br>
<br>
--<br>
Martin Kouba<br>
Software Engineer<br>
Red Hat, Czech Republic<br>
<br>
______________________________<wbr>_________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/<wbr>licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 71, Issue 29<br>
******************************<wbr>*********<br>
</blockquote></div><br></div></div></div></div>