v0.0.6

In this release, in addition to some internal changes,

• Request body in POST request is injected to controller classes. This injection can occur as String format or alternatively Lambada can try to serialize the JSON to given object type. See: #19
• Lambada framework can be used as Lambda deployment tool without JAX-RS capabilities. See lambdaHandler configuration option for that.

v0.0.5

This update

• Addresses the issue reported in #17
• Deprecates LambdaLogger in favor of log4j. Now framework's internal logging works only if the user's project has log4j configured. (See boilerplate project for example)

v0.0.4

This release

• Addresses the issue reported in #9
• Removes some unnecessary dependencies in order to reduce the deployment package
• Renames maven plugin to suppress a warning at deployment stage

This is a breaking change

You should edit your project's pom.xml file and replace

            <groupId>org.lambadaframework</groupId>
            <artifactId>maven-plugin</artifactId>

with

            <groupId>org.lambadaframework</groupId>
            <artifactId>lambada-maven-plugin</artifactId>

v0.0.3

This release has important bugfixes as well as some Cloudformation changes for better support.

First release

This is the first release of Lambada Framework.