> Hi, > I'm in your same boat (like many I guess). In an effort to learn best > pratice and avoiding to reinvent the wheel, I thought, it may be wise to > stick with one of the several java web application frameworks. > I'm trying with Spring, which seems quite good, but at least for me, it is > not that easy to learn too. I just come across another one called Wicket, > which between the other premises, says having focused on easier lerning > curve. > Hope it helps. > > Giorgio
Giorgio, I appreciate your reply. I don't have a choice in the framework - that's already set. I'm just learning a lot of stuff - a Java refresh, JDBC, Tomcat, numerous Apache-related project acronyms, and places to go for information. I'll have to look at the two you mentioned, simply to fill in the blanks on what they are. I've put together something that's working for me for now. I (sadly) don't have a clue whether I'm totally misunderstanding something, or whether I've coded a potential show-stopping kludge into my program, but it currently _is_ running enough to let me get at the next thing on my task list for the project. Ah, well, it's for things like this that we schedule a long test/fix cycle, right? Thanks again.....Warrick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
