[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] EE4J Project for annotation scanning?

Certainly and fully intended the EG decided to make it _useable_ in Java SE, but that does not make a *Java SE API*. What was asked in the original thread was having an annotation scanning API *being part of Java SE*. But EE4J is *not* developing anything that is *part of Java SE* as this ONLY can be done by OpenJDK. I though Mike's recent email clarified this to full extend.

-Markus

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Guillermo GonzÃlez de AgÃero
Sent: Freitag, 1. Dezember 2017 09:29
To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

Yes, and even being contained only on EE, it still provides an SE API. So I suspect the EG thought it would be usable also outside EE.

 

El vie., 1 dic. 2017 9:25, Markus KARG <markus@xxxxxxxxxxxxxxx> escribiÃ:

JPA is _not_ contained in Java SE. It is contained _only_ in Java EE.

-Markus

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Guillermo GonzÃlez de AgÃero
Sent: Donnerstag, 30. November 2017 19:25


To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

JPA provides a Java SE API and it's still developed under Java EE umbrella. JSON-B and JSON-P are useful everywhere.

While annotation scanning is useful everywhere, application servers are probably one of the most benefited areas.

 

 

Regards,

Guillermo GonzÃlez de AgÃero

 

El jue., 30 nov. 2017 a las 18:41, Markus KARG (<markus@xxxxxxxxxxxxxxx>) escribiÃ:

As the name implies, EE4J is targeting *enterprise* applications, while annotation scanning is useful in other areas (desktop, mobile, games, etc.), too. Hence it would make more sense to open a JEP at OpenJDK. It could become part of Java SE then.

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Greg Wilkins
Sent: Donnerstag, 30. November 2017 13:58


To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

 

Markus,

 

I don't think the github project approach is going to work.   What I'm suggesting is more than just provide some kind of commonly used library that does annotation scanning.   I've already got a commonly used library that does annotation scanning - it's Eclipse Jetty.   I could spin out our code for annotation scanning to github, but it will still just be one of many many implementations with nothing to recommend it over any of the many other implementations.

 

This effort needs not to be code driven, but requirement/specification driven.  As the links given indicate, it should have been functionality that was included in Java 9, but it didn't happen.  Unless it does happen, then all the various projects are going to separately implement, with many differences and incorrect implementations and we are all going to suffer through lots of instability as java 10 and 11 are released on the proposed 6 monthly schedule.    So there needs to be a collaborative effort that has a bit more gravitas than some random github project.

 

Note that Eclipse Jetty as a servlet container is not limited to enterprise, yet we follow a specification that is driven by the EE effort, originally at the JCP and now here. So I don't really see why EE4J cannot consider coordinating this?

 

cheers

 

On 30 November 2017 at 13:33, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

If your intention is to simply provide some kind of commonly used library, Github is a good place to start. Once your project gains attention and you feel the need for some kind of official organization around it, start a project on Eclipse: https://www.eclipse.org/projects/handbook/#starting. If you found an existing Eclipse top level project that looks like what you want to be part of, ask them for adoption. :-)

-Markus

 

 

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Greg Wilkins
Sent: Donnerstag, 30. November 2017 13:28
To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

 

On 30 November 2017 at 13:26, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

I do not see that annotation scanning is limited to enterprise use, so I would say no.

 

So where would you suggest such an effort is coordinated?

 


 

--


_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community



 

--

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community