A couple of thoughts on that. - You don't want user interface developers modifying the production version of the app any more than you want app developers doing so.
- You could use a framework such a Tapestry that provides clear separation between user interface and application code. The user interface developers could then develope the user interface separately from the full application and would need only an http server to test their changes. - Considering that JBoss is not difficult to install or maintain, I don't see why the user interface developers could not have JBoss on their PC. (You could also provide a centralized machine running a development version of the app, but then you will need to do remote deployment of code changes and other "fun" things, so it probably is not worth it in the end.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946147#3946147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946147 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
