Hi
please, can you make a small example for the rodl2code to write the name of the file with the name of the service?
I’ve tried a few things here following your suggestion but it’s not working.
Regards.
Hi
please, can you make a small example for the rodl2code to write the name of the file with the name of the service?
I’ve tried a few things here following your suggestion but it’s not working.
Regards.
Unfortunately rodl2code doesn’t allow to customize output file name. This file name always matches either RODL library name (when RODL is downloaded from a remote server by rodl2code itself) or RODL file name (when RODL is loaded from a local file).
Actually you can create a .cmd file that will call rodl2code with desired options and then immediately rename resulting file(s) as you need.
I can add an option to override the output folder.
OnCustomResponseEvent works only for unhandled requests so try to pass something unusual like http://localhost:8099/zzzzz?servicegroup=BINDER or similar
rodl2code will support this parameter in next build:
--outfilename:<name> (optional base filename for generated files, w/o extension)
Hi,
when will this improvement be available? could you release a beta test for me?
Regards,
We’re actually doing a new official build right now that will be our later today, Build .1449.
okay I’ll be waiting.
Thanks
.1449 is out now. Enjoy!
Hello,
I’m trying to install this build (.1449) and I giving installation errors.
Also treid to compile the packages but many errors ocorrs too.
Regards.
can you sent log.html/log.xml to support@, pls?
what errors were shown?
according to log file:
uHYLocalService.pas(39) Fatal: E2225 Never-build package ‘RemObjects_Server_D25’ must be recompiled
you should recompile RO packages in IDE manually before installing Hydra
It worked!! rodl2code generated output file is with service name!
I will continue with the my update.
Thank you very much
Smokoveck
It seems that this thread has seen a good many different/unrelated issues being discussed. If the codeine works now, would it be ok if we close this and start a new thread for nay future issues? It makes it easier to keep track of than having everyone in one long threat…
That’s right! Combined.
bugs://D18313 was closed as fixed.