I am new to grails I give it a detour from implementing a new feature or two in an existing Java EE application Want to The current Java EE application is the standard standard MVC / Hibernate app running on Tomcat. By looking at the documentation, it seems that I should be able to take advantage of all the existing business logic written in Java.
I'm only able to find tutorials on creating new grails applications. Is there a tutorial address to integrate with an existing Java EE app? If there are no tutorials, where do any suggestions or suggestions?
Whether or not these features go live, will depend on my experience with Grails and if I think it is appropriate to use it to move forward. The goal will either be:
- For me, Grails is not deconstructed.
- This decision is for me, and all future developments on this app will be in Grails with a complete final port.
I'm afraid that I do not know about any such tutorials, But my immediate idea would be that even with the closure of an application, it can be difficult to learn together with Grail.
I have not done anything like that before, so it is not similar to GSP and the controllers in Java are typed steady, while Grails is wired on the magic methods of controllers, maybe I would like to They write again in Grails by scratches because their transfers are not clear - the logic should be moved, but the old code boilerplate is not absolutely necessary for the most part. .
Perhaps taking a simple story / taking feature, he uses the existing services and he gets wired through Grails in the spring, after which you try to make a copy with the one you have Java has related controller / GSP and domain. What you need to do to get rid of the land for the port?
Your biggest struggle, those people who have heard me do this, may be that they are in Grails Trying to reuse current hibernate stuff.
Just my tweepens, so do not respond completely ...
Comments
Post a Comment