Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement integration module for Google AppEngine #2125

Closed
jerseyrobot opened this issue Apr 17, 2013 · 12 comments
Closed

Implement integration module for Google AppEngine #2125

jerseyrobot opened this issue Apr 17, 2013 · 12 comments
Labels
gae Priority: Major Type: New Feature

Comments

@jerseyrobot
Copy link
Contributor

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
Copy link
Contributor Author

@glassfishrobot Commented
Reported by @mpotociar

@jerseyrobot
Copy link
Contributor Author

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

@jerseyrobot
Copy link
Contributor Author

@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
Copy link
Contributor Author

@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
Copy link
Contributor Author

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

@jerseyrobot
Copy link
Contributor Author

@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
Copy link
Contributor Author

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

Servlet 3.0 is on the work, not pushed yet.

@jerseyrobot
Copy link
Contributor Author

@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
Copy link
Contributor Author

@glassfishrobot Commented
@mpotociar said:
Closed by filer.

@jerseyrobot
Copy link
Contributor Author

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

@jerseyrobot
Copy link
Contributor Author

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

@jerseyrobot
Copy link
Contributor Author

@dmatej dmatej mentioned this issue Mar 4, 2021
Merged
dmatej added a commit to dmatej/jersey that referenced this issue May 2, 2021
@dmatej
GrizzlyHttpServerTest - testing stability with HTTP, HTTPS and HTTP/2
0c57776 
- parallel execution on random free ports
- disabled for jdk8
- possibility to use three different clients
  - jersey-client - but it doesn't support HTTP/2
  - jdk11+ HttpClient - but it is not available in older JDK versions
  - jetty-client - but version compatible with jdk8 uses different classes
      than version compatible with jdk11
- each test creates a configured server, then creates several clients
  which are sending GET requests for given time.
- all responses must be HTTP 200
- after the test then number of processed requests is written to the STDOUT
- if there will be just one non compliant response, all clients are stopped
  and the test fails.
- originally created to reproduce the issue eclipse-ee4j#2125 of the Grizzly project,
  which used Jersey and Grizzly together.

Signed-off-by: David Matějček <dmatej@seznam.cz>
dmatej added a commit to dmatej/jersey that referenced this issue Sep 8, 2021
@dmatej
GrizzlyHttpServerTest - testing stability with HTTP, HTTPS and HTTP/2
883db8a 
- parallel execution on random free ports
- disabled for jdk8
- possibility to use three different clients
  - jersey-client - but it doesn't support HTTP/2
  - jdk11+ HttpClient - but it is not available in older JDK versions
  - jetty-client - but version compatible with jdk8 uses different classes
      than version compatible with jdk11
- each test creates a configured server, then creates several clients
  which are sending GET requests for given time.
- all responses must be HTTP 200
- after the test then number of processed requests is written to the STDOUT
- if there will be just one non compliant response, all clients are stopped
  and the test fails.
- originally created to reproduce the issue eclipse-ee4j#2125 of the Grizzly project,
  which used Jersey and Grizzly together.

Signed-off-by: David Matějček <dmatej@seznam.cz>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
gae Priority: Major Type: New Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jerseyrobot