Implement integration module for Google AppEngine

[jerseyrobot]

The module needs to provide custom org.glassfish.jersey.spi.RuntimeThreadProvider implementation that delegates the Thread creation to AppEngine-provided ThreadFactory instances as discussed in #2111.

Environment

Google App Engine

Affected Versions

[2.1]

[jerseyrobot]

@glassfishrobot Commented
Reported by @mpotociar

[jerseyrobot]

@glassfishrobot Commented
Issue-Links:
is related to
JERSEY-1839

[jerseyrobot]

@glassfishrobot Commented
@shamoh said:
There is gae-integration extension module prepared. That module implements mentioned SPI.

But currently there is a blocker because Jersey 2.0 uses Servlet API v3 and GAE supports Servlet API v2.5 only. It means it is not possible to finish the gae integration module now.

Sources are places in my personal GitHub branch (#2125) - https://github.com/shamoh/jersey/tree/JERSEY-1853/ext/gae-integration

There is also base of GAE test web application prepared. But it is not finished jet because of mentioned issue about Servlet API version. Currently it just tests it is possible to inject RuntimeThreadProvider or ScheduledExecutorService instances. But @ManagedAsync does not work.

Sources are places in same personal GitHub branch - https://github.com/shamoh/jersey/tree/JERSEY-1853/examples/gae-webapp

[jerseyrobot]

@glassfishrobot Commented
@shamoh said:
I sent an email to Ludovic Champenois (ludovic.champenois@gmail.com) for advice (16/May/2013 2:58 PM CEST):

Hello Ludo.

I'm a new member of Oracle's Glassfish/Jersey team. I'm currently working on Jersey 2.0 and Google App Engine integration and I have some troubles. Marek Potociar pointed out you could help me with it.

Jersey 2.0 uses Servlet 3.0 and it seems GAE supports just Servlet 2.5. I found out there is a feature request (https://code.google.com/p/googleappengine/issues/detail?id=3091) about this issue. And "Java Servlet 3.0 support" is also mentioned in GAE roadmap (https://developers.google.com/appengine/docs/features#Roadmap_Features).

May I ask if there is any progress with this issue? Or is there a way how to set up for example GAE dev server to support Servlet 3.0? Just to test both technologies together now.

Thanks in advance for any suggestions.

Best regards,
Libor Kramolis

[jerseyrobot]

@glassfishrobot Commented
@shamoh said:
Integration module moved to incubator.

[jerseyrobot]

@glassfishrobot Commented
@shamoh said:
Currently it is necessary to programmatically register GaeFeature. It could be nice to create GaeAutoDiscoverable to be GaeFeature registered automatically whenever GAE integration module is on classpath.

[jerseyrobot]

@glassfishrobot Commented
@shamoh said:
Ludovic (24/May/2013 7:38 AM CEST):

Servlet 3.0 is on the work, not pushed yet.

[jerseyrobot]

@glassfishrobot Commented
ciscox83 said:
I see that the last update about this is dated a year ago. Is there any ongoing development or any news about this?

Thank you!

[jerseyrobot]

@glassfishrobot Commented
@mpotociar said:
Closed by filer.

[jerseyrobot]

@glassfishrobot Commented
Marked as won't fix on Thursday, September 10th 2015, 12:28:05 pm

[jerseyrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA JERSEY-1853