uniconlabs / orville Goto Github PK

And include this script in the distribution archive in bin directory for example. This way it will free users from having to execute long java -jar ... command, will enable the script to be installed as a Linux init.d service or OS X launchd script, etc. This will provide a more production ready operational aspect of the application. Take inspiration from Spring XD starter shell script for example, as at its heart, XD is a Spring Boot app:

https://github.com/spring-projects/spring-xd/blob/master/scripts/xd/xd-singlenode

So it would be easy for adopters to plug in their own processors into the pipeline or completly construct their own pipeline. Should utilize the features of Spring @Configuration style Java config as well as Spring Boot's @EnableAutoConfiguration framework as well as Spring 4 @Conditional framework. Look into contributing external jars to Orvile's final executable jar by means of Spring Boot's PropertiesLauncher

References:

• Auto configuration framework
• PropertiesLauncher

For querying people

Currently it relies on the GORM/Hibernate automagic schema update/create logic and hardcoded reference data bootstrap code in the Application class. Need to come up with a more flexible approach to provide generated database DDL/DML scripts or use the Flyaway database migration tool which is supported natively by Spring Boot: http://docs.spring.io/spring-boot/docs/1.0.1.RELEASE/reference/htmlsingle/#howto-use-a-higher-level-database-migration-tool

Initially we should implement HTTP basic auth

This needs to be implemented in its own processor and inserted into the pipeline before the persistence processor so the correct HTTP 400 could be signaled to REST resource implementation if any of the GORM validations fail

and make sure the real outcome is set by the idmatch processor

Need requirements for validation use cases in order to create implementation

Need requirements and use cases in order to implement

Need requirements and use cases in order to implement

For both new records and existing records (even if incoming JSON data [represented as Map] only holds partial amount of values for the object). If we could use existing GORM's model.properties = jsonMap somehow, etc.

http://stackoverflow.com/questions/5806478/binding-only-some-properties-onto-a-grails-domain-object