[cdi-dev] Enhancement proposition to JSR 330

Werner Keil werner.keil at gmail.com
Mon Sep 8 17:24:58 EDT 2014


Antoine,

As seen, there could be Spring or other stakeholders who prefer either
minimum JDK, so let's see if they actually propose it what they suggest (or
in a draft upfront like some JSRs like MVC and others did)

Werner

On Mon, Sep 8, 2014 at 4:09 PM, Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:

> Werner,
>
> Java EE 8 target is JDK 8 as we said before. But te goal of this document
> is not to discuss with Bob and Juergen how they should use JDK 8 within
> their spec, but to see if are willing to discuss our suggestion. When we’ll
> find a general agreement it will be useful to go into such details.
>
> Antoine
>
>
> Le 8 sept. 2014 à 12:20, Werner Keil <werner.keil at gmail.com> a écrit :
>
> Antoine/all,
>
> Thanks for sharing. I also had a discussion (in his own Spring blog) with
> Jürgen mainly about modularity, and the JDK minimum requirements for Spring
> 4.x. He confirmed, the "core" components of Spring 4.1 still run under as
> low as Java 6, while some modules that can be dynamically (Spring-DM aka
> OSGi;-) added may directly refer to Java 8, in which case you must run SE 8
> or higher.
>
> So while for Java 6/7 or below version of @Inject.next this:
>
> public interface Provider<T> extends Iterable<T> {
>  /**
>   * Provides a fully-constructed and injected instance of {@code T}.
>   */
>  T get();
> [...]
>
> looks fine, it seemed more than consequent, if you  did
>
> public interface Provider<T> extends Iterable<T>, Supplier<T> {
> [...]
>
> in a Java 8+ case;-)
>
> Even without looking at Lambdas here in greater detail, it reused what
> Java SE 8 introduced.
>
> Again, that is something you, Bob, Jürgen and maybe the EE 8 Spec Leads
> should discuss, what the reasonable minimum requirements for  @Inject.next
> are, if it's SE 8 or a lower version, though those of course may always
> stick with the previous ones...
>
> Werner
>
> On Mon, Sep 8, 2014 at 12:06 PM, <cdi-dev-request at lists.jboss.org> wrote:
>
>> Send cdi-dev mailing list submissions to
>>         cdi-dev at lists.jboss.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://lists.jboss.org/mailman/listinfo/cdi-dev
>> or, via email, send a message with subject or body 'help' to
>>         cdi-dev-request at lists.jboss.org
>>
>> You can reach the person managing the list at
>>         cdi-dev-owner at lists.jboss.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of cdi-dev digest..."
>>
>>
>> Today's Topics:
>>
>>    1. [JBoss JIRA] (CDI-456) fix Bean#getBeanClass() definition
>>       (Romain Manni-Bucau (JIRA))
>>    2. Enhancement proposition to JSR 330 (Antoine Sabot-Durand)
>>    3. Re: With the end of Java Config... (Werner Keil)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 2
>> Date: Mon, 8 Sep 2014 12:03:36 +0200
>> From: Antoine Sabot-Durand <antoine at sabot-durand.net>
>> Subject: [cdi-dev] Enhancement proposition to JSR 330
>> To: cdi-dev <cdi-dev at lists.jboss.org>
>> Message-ID: <D8CD5D26-82DB-4F64-89C5-93AD467FBC0B at sabot-durand.net>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi all,
>>
>>
>> I received an answer from Bob Lee (off list). He likes te idea of us
>> providing a proposal document. So I worked on it this WE.
>> Here it is :
>> https://docs.google.com/document/d/1KCzqodA8uzXED5DJrEUyl0x3dOUB5mBwL4KcV8xUY_w/edit?usp=sharing
>> <
>> https://docs.google.com/document/d/1KCzqodA8uzXED5DJrEUyl0x3dOUB5mBwL4KcV8xUY_w/edit?usp=sharing
>> >
>>
>> Your comments and proposal are most welcome. I propose we discuss this
>> point during our next meeting, and if we agree on the final content send it
>> asap to have Bob and Juergen feeling about these suggestion.
>>
>>
>> Antoine
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140908/607a6499/attachment-0001.html
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>> Note that for all code provided on this list, the provider licenses the
>> code under the Apache License, Version 2 (
>> http://www.apache.org/licenses/LICENSE-2.0.html).  For all other ideas
>> provided on this list, the provider waives all patent and other
>> intellectual property rights inherent in such information.
>>
>> End of cdi-dev Digest, Vol 46, Issue 42
>> ***************************************
>>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> Note that for all code provided on this list, the provider licenses the
> code under the Apache License, Version 2 (
> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140908/65d022cc/attachment.html 


More information about the cdi-dev mailing list