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

Given the fact that the majority of new software will not be running on Application Servers anymore, but are Microservers, Mobile Apps, or Serverless functionality, there is a real need to have such a scanner not only in EE4J but also in e. g. Android, Microprofile, and Oracle FN. This would not be possible if being part of EE4J / not being part of OpenJDK.

-Markus

 

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Emily Jiang
Sent: Freitag, 1. Dezember 2017 11:13
To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

I like the idea. Annotation scanning is widely used in Application servers. It is quite relevant to EE. However, the annotation scanning is only used for application servers internally, not by end users. It is pretty much SPIs to be introduced under this proposal. I think it falls between JavaSE and JavaEE as it is to be used by application servers not by end users. Having that said, I suggestion to propose this idea under EE4J (after EE4J settles or maybe experiment in git first), with the focus on proposing SPIs for application servers. Hopefully with this effort, the application servers can boost their startup performance.

Emily

 

On Fri, Dec 1, 2017 at 8:28 AM, Guillermo GonzÃlez de AgÃero <z06.guillermo@xxxxxxxxx> wrote:

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


_______________________________________________
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




--

Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx