Soriento
Soriento copied to clipboard
dimparf
Package scan for classes
If you have very many classes to be marshalled into ODB it would be useful to automatically detect them with a package scanner and to automate calling OCreate and typereaderregistry.
Should mark classes to be imported as @Entity, or @Table in order to identify which should be imported?
I have a local implementation that uses the Reflection package scanner to find classes: http://reflections.googlecode.com/svn/trunk/reflections/javadoc/apidocs/index.html?org/reflections/Reflections.html
Hi, stuz5000. I do not want to add new dependencies for the project. It should be simple. If you will create a simple package scanner without dependencies, it will be good.
It turns out package scanning doesn't look so simple that it makes sense duplicate one (there are several gitub projects just on package scanning). But I agree that having external dependencies is not good (especially since there's a high likelihood that an individual project already users a different package scanner.)
How about this:
- define a standard set of annotations (e.g. @Entity), and set of utility functions
- pick a package scanner for the sbt test config to build tests.
On Sun, Jun 5, 2016 at 5:02 PM, Dmitry Parenskiy [email protected] wrote:
Hi, stuz5000. I do not want to add new dependencies for the project. It should be simple. If you will create a simple package scanner without dependencies, it will be good.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dimparf/Soriento/issues/18#issuecomment-223846096, or mute the thread https://github.com/notifications/unsubscribe/AHcErPyRSF3rOX8gjm8BWJKYQAjX1INeks5qI2OmgaJpZM4ISF0j .