Conversation
This ended up a more aggressive refactoring than I started, but it is on its way to being a more Ruby-like framework. * Library will be named "boing", like the sound a spring makes. * All modules and classes are namespaced under the Boing module. * Examples have been split off from the library. * Library has been restructured based on functionality area and organized like a standard Ruby project with a toplevel "boing" dir and subdirs for submodules. * The new Boing::Boot module applies SpringBootApplication anno and adds the include class to a list of original sources. This avoids having to manually register as well as include. * Java imports have been localized to their use site in most cases. There's more coming, since I can't get the employees example working, but the hello example works fine.
|
@prabhavpandey19 This is a start at reorganizing. I could not get the employees example to work... was it working for you? Best I could do is get it to complain that it can't find "root entity Employee" even though I thought I was registering it correctly. Readme is updated with how to run examples. |
This is a possible example of a way to do single-line or single- body REST apps.
@headius I think the issue is related to the H2 in-memory database setup. We should verify that the in-memory database is being created correctly and that the Flyway migrations are running successfully. I will do further testing after this reorg get back to you with solution Here’s the PR where I’ve addressed the issue: #3 The core problem lies with the JPA entity mapping failing in JRuby. We’ll need to explore a new approach to properly handle this, or alternatively, revert to using the native query approach if that proves more stable. |
This ended up a more aggressive refactoring than I started, but it is on its way to being a more Ruby-like framework.
There's more coming, since I can't get the employees example working, but the hello example works fine.