bbilger / jrestless Goto Github PK

Add support for dynamic headers in non-default responses.

I saw comments on issues #27 and #34 with @injeniero and @vikrampatankar regarding running dropwizard. I think @injeniero may have a working example, and I see a repo was created but never filled.

Has jrestless ever been used for dropwizard? If so, any hints on how to do that?

Many thanks

Oracle launched their serverless Function As A Services project:

http://fnproject.io/

one aws-core project is enough; jrestless-aws-gateway-core and jrestless-aws-service-core is overkill

check for existence of the @ApplicationPath on the ResourceConfig/Application and filter accordingly
(#21 (comment))

Im trying to use 0.4.0 but can't locate GatewayResourceConfig class. What jar is it contained within?

What is the best way to run the lambda service locally? say inside tomcat or some? So to rest the endpoints like localhost:8080/api
thanks

baseUri is not equal to the basePath => handle correctly
deprecate constructors expecting baseUri

Upgrade to JUnit 5

I've found that even when a request fails (eg. an exception is thrown in my handler), the onRequestSuccess hook is called with a status code of 500.

Is this what is meant to happen? What is the preferred method for dealing with exceptions? My desired approach would be to catch any exception in onRequestFailure and return an appropriate response.

I've noticed that in line 357 of JRestlessHandlerContainer.java, commit() is called. If I throw a RuntimeException here instead, my onRequestFailure hook is triggered and I can go on my merry way.

Hope this makes sense, and you can help!

In order to Weld work with Jrestless I needed to change the packages to include META-INF/beans.xml.

Is it possible to include those files in next release?

Thanks!

Add CORS filter (for APIGW)

introduce common AWS* response object

Hi,

Wondering how one can go about enabling Guice based dependency injection? So the rough equivalent to https://jersey.java.net/nonav/apidocs/1.8/contribs/jersey-guice/com/sun/jersey/guice/spi/container/servlet/GuiceContainer.html

Now that AWS lambda supports proxy integration the code can be simplified massively.

• drop differentiation between default and non-default response
• adjust response / request objects
• remove swagger
• remove jrestless-core

https://aws.amazon.com/blogs/aws/api-gateway-update-new-features-simplify-api-development/

requestContext.authorizer.claims (Map<String, String>)
requestContext.authorizer.principalId (String)

https://aws.amazon.com/blogs/mobile/integrating-amazon-cognito-user-pools-with-api-gateway/

Thanks so much for this software, looks really nice so far!

While going through the examples I was wondering if there was any chance of connecting with twitter/github/amazon oauth login, so one does not have the burden of managing users himself/herself.

note: I am pretty much a AWS newbie, so I might be just missing or misunderstanding things, so feel free to close if appropriate.

GatewayRequest and GatewayResponse must handle isBase64Encoded

add AWS gateway security module that deals with authorizer data

Jrestless is not compatible with Jersey 2.26 due to removing ServiceLocator and replacing InjectionManager:

http://javaarm.com/file/glassfish/jersey/doc/userguide/Jersey-2.26-User-Guide.htm#mig-2.26-injection-manager

add new event handler that support SNS events and passes them to Jersey

• support injection of SNSEvent.SNS
• use the message as body (headers: "Content-Type: application/json / text/plain?)
• the topic name would be the name of the endpoint

(that's the point where we need a common AWS module)

add custom encoding filter that encodes binary, only!

Add support for multiple content-types for one endpoint.
This depends on #2 to be implemented.

Hi bbliger,

It seems you forgot to update the changelog to include 0.5.0 release.

Thanks for the great work!!

PS: I was able to integrate dropwizard 1.0.6 with your project and deploy to AWS Lambda :-)

use the newly introduced RequestAndBaseUri in SNS and Service Functions and remove the baseUri constructors (see #25)

jrestless sounds really promising. Unfortunately it's not straightforward to get it running with Maven.

With the following pom.xml:

    <dependencies>
        <dependency>
            <groupId>com.jrestless.aws</groupId>
            <artifactId>jrestless-aws-gateway-handler</artifactId>
            <version>0.3.0</version>
        </dependency>
        <dependency>
            <groupId>org.glassfish.jersey.media</groupId>
            <artifactId>jersey-media-json-jackson</artifactId>
            <version>2.23</version>
        </dependency>
    </dependencies>
    
    <repositories>
        <repository>
            <id>jcenter</id>
            <url>http://jcenter.bintray.com</url>
        </repository>
    </repositories>

The build results in [ERROR] Failed to execute goal on project ***: Could not resolve dependencies for project ***: Could not find artifact org.glassfish.jersey.containers:project:jar:2.23 in jcenter (http://jcenter.bintray.com) -> [Help 1].

The problem is that org.glassfish.jersey.containers:project is being referenced within com.jrestless.core:jrestless-core-container as a dependency. Maven then thinks this is a dependency of type jar, where in fact it is of type pom. When trying to download the corresponding jar file, it gets a 404 from both jcenter and Maven Central and throws the error above.

The following workaround fixes the issue:

    <dependencies>
        <dependency>
            <groupId>com.jrestless.aws</groupId>
            <artifactId>jrestless-aws-gateway-handler</artifactId>
            <version>0.3.0</version>
            <exclusions>
                <exclusion>
                    <groupId>org.glassfish.jersey.containers</groupId>
                    <artifactId>project</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.glassfish.jersey.core</groupId>
            <artifactId>jersey-server</artifactId>
            <version>2.23</version>
        </dependency>
        <dependency>
            <groupId>org.glassfish.jersey.media</groupId>
            <artifactId>jersey-media-json-jackson</artifactId>
            <version>2.23</version>
        </dependency>
    </dependencies>

It would be great if you could fix the dependencies to use jersey-server directly instead of relying on the project parent POM, so that the workaround is no longer needed in future versions. Thanks!

When trying out version 0.4.0, I cannot get my previously running JerseyTests to work. They were running fine with 0.3.0. Sample code:

public class ResourceTest extends JerseyTest {
    @Override
    protected Application configure() {
        return new ResourceConfig()
                .register(GatewayFeature.class)
                .packages(RequestHandler.class.getPackage().getName());
    }

    @Test
    public void healthcheck() throws Exception {
        Response response = target("/health").request().get();
        assertThat(response.getStatusInfo()).isEqualTo(Response.Status.OK);
    }

With the following log output:

2016-12-17 11:56:40 ERROR ExceptionMapper:15 - Failure when processing request.
MultiException stack 1 of 1
java.lang.IllegalStateException: Proxiable context org.glassfish.jersey.process.internal.RequestScope@3e4f2b4d findOrCreate returned a null for descriptor SystemDescriptor(
	implementation=com.jrestless.aws.gateway.GatewayFeature$ReferencingGatewayRequestFactory
	contracts={com.jrestless.aws.gateway.io.GatewayRequest}
	scope=org.glassfish.jersey.process.internal.RequestScoped
	qualifiers={}
	descriptorType=PROVIDE_METHOD
	descriptorVisibility=NORMAL
	metadata=
	rank=0
	loader=org.glassfish.hk2.utilities.binding.AbstractBinder$2@3a21dd9e
	proxiable=true
	proxyForSameScope=false
	analysisName=null
	id=125
	locatorId=1
	identityHashCode=310202442
	reified=true) and handle ServiceHandle(SystemDescriptor(
	implementation=com.jrestless.aws.gateway.security.CognitoUserPoolAuthorizerFilter
	contracts={javax.ws.rs.container.ContainerRequestFilter}
	scope=javax.inject.Singleton
	qualifiers={org.glassfish.jersey.internal.inject.Custom}
	descriptorType=CLASS
	descriptorVisibility=NORMAL
	metadata=
	rank=2000
	loader=null
	proxiable=null
	proxyForSameScope=null
	analysisName=null
	id=141
	locatorId=1
	identityHashCode=1492979664
	reified=true),531579585)
	at org.jvnet.hk2.internal.MethodInterceptorImpl.internalInvoke(MethodInterceptorImpl.java:92)
	at org.jvnet.hk2.internal.MethodInterceptorImpl.invoke(MethodInterceptorImpl.java:125)
	at org.jvnet.hk2.internal.MethodInterceptorInvocationHandler.invoke(MethodInterceptorInvocationHandler.java:62)
	at com.sun.proxy.$Proxy32.getRequestContext(Unknown Source)
	at com.jrestless.aws.gateway.security.AuthorizerFilter.getAuthorizerData(AuthorizerFilter.java:50)
	at com.jrestless.aws.gateway.security.AuthorizerFilter.filter(AuthorizerFilter.java:40)
	at org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:132)
	at org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:68)
	at org.glassfish.jersey.process.internal.Stages.process(Stages.java:197)
	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:318)
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
	at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service(GrizzlyHttpContainer.java:384)
	at org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:224)
	at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:593)
	at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:573)
	at java.lang.Thread.run(Thread.java:745)
Dec 17, 2016 11:56:40 AM org.glassfish.grizzly.http.server.NetworkListener shutdownNow
INFO: Stopped listener bound to [localhost:9998]

org.junit.ComparisonFailure: 
Expected :OK
Actual   :Internal Server Error

Maybe it has to do with the change from GatewayResourceConfig (in 0.3.0) to use the GatewayFeature? Please let me know if I can try out anything else, as I'm not too knowledgeable about Jersey's internals.

add a filter to set the application path dynamically
"/api/{proxy+}" => application = "/api"
see #21 (comment)
(optional feature)

Currently the following combination :

• API Gateway resource path = "/api/{+proxy}"
• JAX-RS Resource class @path("/helloworld")

Does not resolve/work. It is expecting the root resource classes to have the same path prefix as the AG resource path (so @path("/api/..") in this example). This is unexpected. The combination above should result in :

https://mysite.com/{stage}/api/helloworld

Since the configuration implies the jersey application route is served by the {+proxy} section. It would be good if the Application instance root path is configurable (e.g. through @ApplicationPath which does not seem to be respected) or if the default is changed.

Hi, I'm having an issue when I've deployed my Lambda to AWS and hooked it up to API Gateway.

I use the API Gateway Test functionality to test the Lambda. It makes the call, the code executes, but when I do the Response.ok()... I get the following messages in my CloudWatch log:

org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor aroundWriteTo
SEVERE: MessageBodyWriter not found for media type=application/json, type=class com...

From what I've read, there's a problem with the glassfish jersey media implementation. So I'd like to just switch over to Jackson's implementation. Is this something you've run into or done in the past?

Thanks,
David

Firstly, thanks for authoring this project! It's greatly helped me get up to speed with Serverless!

I'm having some trouble with logging. I've tried following your example. However, after deploying such code and curling an endpoint, serverless logs -f $function_name doesn't indicate any logging is being done.

Here's my handler. I added a log to beforeHandleRequest, as well as to each method in my resource. None of these logs are showing up in serverless logs -f all (my function is named all).

Any idea why? Perhaps I should use a different command to obtain logs? Thanks.

Jrestless look be a interesthing project and is very use full for me.
I I would like to contribute with jrestless.

Exist a roadmap ?
What is your pretension for the future of the project ?

integrate OpenWhisk

With 0.4.0 I have more of a question than an actual issue using my own authentication filter. Maybe just a little confused about the new factory setup. Here's what I had before for 0.3.0 to retrieve a gatewayIdentity in a filter:

public class AuthFilter implements ContainerRequestFilter {

    @Override
    public void filter(ContainerRequestContext requestContext) throws IOException {
        GatewayIdentity gatewayIdentity = (GatewayIdentity) requestContext
               .getProperty(GatewayIdentityContextFactory.PROPERTY_NAME);

               
        ...
    }
}

How might I do this with 0.4.0? I am using IAM authentication for the API Gateway -- not custom or cognito userpool.

Pull the Gateway/Service/SnsFeature registration into the handlers itself and don't leave it to the user anymore. That should make things more clear and less fragile.
see #18 and #17

introduce commone injectable request object (body, headers, requestUri)

Hi,

I am trying to use jrestless with Weld integration (to use autodiscover feature) and I'm having the following exception:

WELD-001408: Unsatisfied dependencies for type GatewayRequest with qualifiers @default
at injection point [BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject public com.jrestless.aws.gateway.security.CognitoUserPoolAuthorizerFilter(GatewayRequest) ...

It seems that the class com.jrestless.aws.gateway.io.DefaultGatewayRequest is final so it cannot be used with Weld. The specification states that final classes are not eligible for injection because of the way Proxy works.

Thanks!

Hi
I want to invoke some of the mvc apis through and some through sns invocation. Is there any way to do it in present framework ?

add support for Azure
https://azure.microsoft.com/en-us/blog/announcing-the-preview-of-java-support-for-azure-functions/

(wildcard route: {*catchall}; raw: Azure/azure-functions-host#965 (comment))

I was looking to have some existing dropwizard applications run on aws lambda with minimal changes to them. Could I use jrestless for that ? Dropwizard uses Jersey & Jetty internally.

Add IAM Security Filter and Principal

Make the execution stage injectable.

• add a new class ExecutionStage with a name property
• derive the exection stage from com.amazonaws.services.lambda.runtime.Context#getInvokedFunctionArn()
  • invokedFunctionArn.split(":").length == 8 => invokedFunctionArn.length.split(":")[7] => alias
  • invokedFunctionArn.split(":").length == 7 => invokedFunctionArn.length.split(":")[6] => lambda function name => search for well known names like "dev", "development", "prod", "production" (serverless appends -- to the lambda function name)

the invokedFunctionArn looks like this arn:aws:lambda:<REGION>:<ID>:function:<LAMBDA FUNCTION NAME>:<ALIAS, optional>

centralize common dependencies

My function is throwing an exception when its Jackson decoder tries to deserialize input JSON:

2017-05-15 22:47:56 <874465cf-39c0-11e7-8842-ab61849afd56> ERROR com.jrestless.core.container.JRestlessHandlerContainer:356 - container failure
Invalid date    at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:62)
        at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:834)
        at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:1093)

This specific exception is not the source of this issue. The issue is that the first line of the stacktrace is not being shown.

The relevant line seems to be here. Note that the first line of the stacktrace is written if we

LOG.error("first line: {}", error.getMessage());