<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Thats why cdi-se-api depends on cdi-api.</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Werner Keil <werner.keil@gmail.com><br>
<b>Sent:</b> Tuesday, October 18, 2016 6:37 AM<br>
<b>To:</b> John Ament<br>
<b>Cc:</b> cdi-dev<br>
<b>Subject:</b> Re: [cdi-dev] Spliting SE package in an independent jar</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div>Yes, but on SE you can't just use the "cdi-se-api" on its own.<br>
<br>
So SE on the API level needs 2 JARs not just one. That's what I mean.<br>
</div>
I trust the sum of all JARs for an implementation would be somewhat smaller on SE, otherwise the "Micro" idea of using a self-executable or "Fat" JAR in those places would be ad-absurdum, if you end up with a "Fat JAR" that's bigger than most existing app servers;-)<br>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I would have expected a <br>
</div>
<div class="gmail_extra">core-api<br>
</div>
<div class="gmail_extra">se-api<br>
</div>
<div class="gmail_extra">ee-api<br>
<br>
</div>
<div class="gmail_extra">kind of setup, but if it won't blow implementations on the SE side, I also understand that.<br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="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">
<p style="margin:0px; border-collapse:collapse"><font size="1" face="arial, helvetica, sans-serif"><span lang="EN-US">Werner</span></font><br>
</p>
<span lang="EN-GB">
<div style="font-family:arial,helvetica,sans-serif"><br>
</div>
</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 12:19 PM, John Ament <span dir="ltr">
<<a href="mailto:john.ament@spartasystems.com" target="_blank">john.ament@spartasystems.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">
<div id="m_4651217999031558913divtagdefaultwrapper" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Opposite Werner, EE API is larger and has the bulk of the content. SE API at this point has two classes.</p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr style="display:inline-block; width:98%">
<div id="m_4651217999031558913divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b>
<a href="mailto:cdi-dev-bounces@lists.jboss.org" target="_blank">cdi-dev-bounces@lists.jboss.<wbr>org</a> <<a href="mailto:cdi-dev-bounces@lists.jboss.org" target="_blank">cdi-dev-bounces@lists.jboss.<wbr>org</a>> on behalf of Werner Keil <<a href="mailto:werner.keil@gmail.com" target="_blank">werner.keil@gmail.com</a>><br>
<b>Sent:</b> Tuesday, October 18, 2016 5:27 AM<br>
<b>To:</b> cdi-dev
<div>
<div class="h5"><br>
<b>Subject:</b> Re: [cdi-dev] Spliting SE package in an independent jar</div>
</div>
</font>
<div> </div>
</div>
<div>
<div class="h5">
<div>
<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="m_4651217999031558913gmail_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.<wbr>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" target="_blank">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/mailma<wbr>n/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" target="_blank">cdi-dev-request@lists.jboss.or<wbr>g</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org" target="_blank">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" target="_blank">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" target="_blank">john.ament@spartasystems.com</a>><wbr>, Antoine Sabot-Durand<br>
<<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>>, cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a>><br>
Message-ID: <<a href="mailto:616fdc4e-26f6-a8d7-16d3-fdceb71faa1f@redhat.com" target="_blank">616fdc4e-26f6-a8d7-16d3-fdceb<wbr>71faa1f@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" target="_blank">cdi-dev-bounces@lists.jboss.or<wbr>g</a><br>
> <<a href="mailto:cdi-dev-bounces@lists.jboss.org" target="_blank">cdi-dev-bounces@lists.jboss.o<wbr>rg</a>> on behalf of Antoine Sabot-Durand<br>
> <<a href="mailto:antoine@sabot-durand.net" target="_blank">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" target="_blank">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/mailma<wbr>n/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/license<wbr>s/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" target="_blank">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/mailma<wbr>n/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/license<wbr>s/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>
</div>
</div>
</div>
</div>
</div>
<hr>
<span class="">NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail,
delete this message, and destroy all physical and electronic copies. Thank you. </span>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
<hr>
NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this
message, and destroy all physical and electronic copies. Thank you.
</body>
</html>