We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the project: http://github.com/caelum/dynamicRepositoryBuilder that creates the implementation of the queries based on an interface. So you just create an interface like:
@Component // or other annotation, perhaps public interface ProductRepository extends Repository { List findByName(String name); }
and receive this interface on your components constructor and VRaptor will provide an implementation using the project above.
The text was updated successfully, but these errors were encountered:
The core of vraptor is to be a controller framework? I think that use a mixture of "many other things" shifts the vraptor proposal.
In a few times, the vraptor will be an elephant.
But... this is only a opinion of a "Vraptor Lover".
Sorry, something went wrong.
This feature should not be in vraptor-core... It should be a plugin...
VRaptor core will always be a controller... but we can add some helpers for view and model as plugins or addons...
No branches or pull requests
Use the project: http://github.com/caelum/dynamicRepositoryBuilder that creates the implementation of the queries based on an interface. So you just create an interface like:
and receive this interface on your components constructor and VRaptor will provide an implementation using the project above.
The text was updated successfully, but these errors were encountered: