hi *,
since we have done now 5+ years of repository based programming we are very used to having a very fixed deployment mechanism. generally we were really happy with the version control of the repository. but TIMES ARE CHANGEING. since we want to do a lot of webservices within CAPS we are currently forced to adopt JCA programming. one thing that is really different when dealing with JCA is that there will be hundreds of projects in netbeans.
can anyone give me some hints to do effective JCA programming with a large environment? best practices. etc.
what do you do for:
1) Version control ? checking in hundreds of netbeans projects? is this doable?
2) Build Management? is it porrible to do an automatic build management with ejb modules?
3) deployment process? how does it look like in DEV/PROD/TEST/ACCEPTANCE?
and so much more...
any hints appreciated. sorry i am really a little disoriented having done now a long time in repo based development. it feels really a bit clumsy doing JCA like hitting with a 5 kilo hammer on a tiny nail. repo based development from my point of view was very suiteable for small teams. now i have to care for so much more....
regards chris

Yup, that's going to be a lot of work. Little best practises out there, so best to involve someone to figure out the easiest/lightweight approach which is also future compliant considering the JBI/Fuji direction of the toolset.
Take care
Paul

Hello Chris,
1) I'm an happy Subversion user, but CVS and other tools work nicely with Netbeans
2) As the Netbeans build system is Ant, you can use any build / continuous integration Ant-compliant tool, there are hundreds out there
3) This blog entry might help: http://blogs.sun.com/tronds/entry/creating_a_simpl e_headless_buildCiao
Maurizio