I'm sure this has been asked at some point, in some form or another, but since I couldn't find a clear answer to my questions... I figured I'd ask rather than lurk.
My question's one of ease of use and migration. At the moment, I hand-code my apps to follow MVC patterns, though I have to admit the idea of using a tool to assist in this appeals to me. What's stopped me thus far is having a rather vague idea of the amount of effort needed to migrate to a framework tool. Obviously, some of the code would have to be redone (or so I figure), but the question that lingers in my mind is - how much of my effort am I going to have to duplicate to utilize a tool? Is it fairly painless - be it Spring, or Struts, or another tool - and quick to get rolling (as it was when I taught myself Hibernate), or is it better for me to wait for a lull between projects to take the time to get rolling?
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
Originally posted by Ali Pope: I am not quite sure what are you calling a tool :-(. But the points to analyse before migrating are quite easy to imagine:
I suppose 'tool' is probably the wrong word. But still.
Budget's not a concern - the project I'd consider starting out on this with is something I'm working on in my free time, so it's more for 'fun' than anything professional.
I'm more than willing to learn something new, but the question in my mind really is a matter of how much of my existing code I'm going to have to throw out and redo. Since I don't have any real way to evaluate that based on just looking at the documentation, I'm curious as to any practical advice from others out here.
Hope that clarifies.
Joined: Jul 12, 2004
But from my position I am not able to see how is your application at this moment .
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com