Frequently Asked Questions - Use Cases
Can MyEclipse for Spring leverage a legacy Spring app?
The general answer is yes, but it really depends on how you want to leverage the legacy Spring application. Do you want to use existing application artifacts (i.e. POJOs, JPA entities, database tables) as an input into scaffolding? Do you want to generate into an existing application? Do you want integrate with a legacy application via database or web services? For all these questions, the answer would be yes.
How would a Spring application integrate with SOA (or previously created web services)?
There are a variety of technologies available for integrating a Spring application with web services, and they can all be used with the applications that are scaffolded or generated with MyEclipse for Spring. MyEclipse for Spring also provides tooling for generating Java-based web service clients from existing WSDLs.
What if you are the only member of dev team using the tool?
There are no caveats to using MyEclipse for Spring. You can layer this tool right into existing projects to leverage what you have and generate new artifacts as you add new functionality to the existing project. The tool works great whether you are a lone developer or part of a very large team. It is all about the code, and MyEclipse for Spring generates standard Spring code and configurations.
For testing, is it possible to have the Junit tests generated into separate directory?
Yes, the destination directory and names of all generated artifacts can be easily customized.
Are there any runtime royalties for commercial use?
Absolutely not. The generated code is straight, best practice-based, Spring code. There are no proprietary libraries or anything else included in any way. The generated applications are all yours to do with as you please, unrestricted.