It is really not needed as it does not add much value other then allows user to cast POJO function to its actual type. The reality is that the actual goald of POJO function is to make sure they can be looked at as plain Functions.
Resolves#514
rename fuction-sample-gcp to function-sample-gcp-http
refdoc polish
background sample polish
Resolves#525
Update pub/sub bg function to use base64 encoding
enable test output temporarily for Travis
Revert "enable test output temporarily for Travis"
This reverts commit a797ca75e8c7a48e57f988360e5d57dbb497a6fb.
Resolves#527
pr comments, mv package, make work locally.
revert pom change to parent
Rm provided scope - this is problematic for spring-boot-maven plugin to build jar
Detach sample from spring-cloud-function-parent
Update readmes
cleanup
Add comment
fix javadoc
Resolves#518
implement HttpFunction
add headers processing
Some refactoring [WIP]
Add invoker integration test
Make test classes nested within test.
Add sample and refdoc
Resolves#468
- Added generic FunctionInvoker capable of handling the request generically without requiring user to implemen specific AWS request handler
Resolves#434
Cleaned up pom to use java.version instead of the compiler.source and
compiler.target
Added version properties for azure-functions-java-library and
azure-functions-maven-plugin
Updated the properties to be the latest recommended from Azure Functions
Used stagingDirectory in maven-resources-plugin
Updated README.adoc to say port 7071 instead of 8080
- Ensured that FunctionClassUtils performs additional check to ensure that located star class is SpringBootApplication
- Added additional lookup to look for Main-Class if nothing was found in Start-Class primarily to support Azure
- Updated Azure samples
- Updated documentation
Resolves#431
