compiling collab rule without egate collab editor

[n3ur0manc3r]

Hi,

I just wanted to know if it's possible to modify, compile and redeploy a java collaboration rule without using egate collab editor?

Our egate repository resides in a Unix environment so I think it would be great to do eway modifications and redeployment in Unix without going through the hassle of opening egate collab editor in Windows.

Is this possible?

Thanks!

 

[DevIntProd]

While it is definatley possibly to set up a complile statement with all the right classpaths, etc... to end up with a compiled class file, I do not advise doing this, and here is why:

a) The other 4 files associated with that rule would not change, and these are essential files the editor uses when it builds the GUI, the generated code, etc... So you may end up with code that doesn't match what is seen in the editor.

b) You also run the risk of the editor re-generating the code from the .xts, .ctl, and .xpr files.

I have never tested this out, but I believe it to be a bad idea.