This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I would like to know if that i have in mind is a good practice for working with Web Services. I explain this:
I have a very complex Java Project, and i need to implement a WS for interact with data. I try to transform this Java Project into a Java Dinamyc Web Project, but there are a lot of dependences and its difficult.
My question is, is a good practice if i create a new Dinamyc Web Project with only the WebService? At the end, i will have two projects, Java and Dinamyc. Is this a good solution?
What do you mean by "Java Dinamyc Web Project" - a web app? Or just a collection of web services? Is the "Java Project" a desktop app or web app? You can run web services as part of a web app, or you can run them as a separate web app. What makes more sense depends on the circumstances about which we know nothing.
Yes i think its a good Solution for handling dependancies
Joined: Nov 22, 2007
The "Java Dinamyc Web Project" is a web app, and my Java project is an web app too, but in eclipse, for example, the "Java project" don't appear as a Dinamyc Web Project and i would like to make separate projects, the "Java Project" for magnament and the "Dinamyc Web Project" as a collection of web services.