"PeterJ" wrote :
| - You could use a framework such a Tapestry that provides clear separation
between user interface and application code.
Or even better, Wicket ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946226#3946226
Reply to the post :
http://
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
Hi Peter,
Thanks for the suggestion. However you have stated that :
5) Developers can deploy the code that they are developing to their own copy of
JBoss for their own testing. Note that this is not the production version of
JBoss. No developer is ever allowed to update the production ve
A couple of suggestions:
1) All source code must be stored in a source control system (CVS, Subversion,
etc.)
2) Everyone checks out the code from the source control system, makes changes,
and checks the code back in.
3) Official builds are done directly from the source control system on a
mach
