(RDMLX) Resource Folder

Please do not use to report errors- use your regional help desk.
Please mark posts as being for RPG or RDMLX (LANSA) developer.
To subscribe by email, display this forum, scroll to the end and select ‘Subscribe Forum’.
Post Reply
edwardtn
Posts: 33
Joined: Fri Aug 28, 2015 11:53 pm

(RDMLX) Resource Folder

Post by edwardtn »

Is it possible to have a schema's resources located in a folder other than '/webserver/images/LongRange/resource'?

For clarification, here is my use case: I would like to distribute a beta version of the application in our development partition using 'frozen' versions of the schema, local objects generator, and resources (HTML, CSS, JavaScript). I can create a copy of the working schema - but would like that schema to download resources from a different resource folder where I can place frozen versions of the required files.

Thanks in advance!

Edward
tsupartono
Posts: 289
Joined: Wed Apr 18, 2012 10:21 am

Re: (RDMLX) Resource Folder

Post by tsupartono »

Hi Edward,
Unfortunately it's not presently possible to designate a different resource folder.

Right now, the only (possibly cumbersome) way to achieve what you want is to put the beta resources in a subfolder (e.g. beta) and change all the resource references to have the "beta/" prefix. Depending upon how many references you have in the schema, this may not be feasible.
However, if most of your resource references are from your RDMLX, this method could work as you can create a function that resolves the resource based on a criteria, either to the actual resource, or to the /beta/resource (you do still need to replace all your resource references in your RDMLX to use this function instead).
edwardtn
Posts: 33
Joined: Fri Aug 28, 2015 11:53 pm

Re: (RDMLX) Resource Folder

Post by edwardtn »

Thanks Tony,

That is what I was afraid of. It is definitely too cumbersome for me to change all references to the resources...the number of references to the resources is just too high.

We are just going to give the beta testers a version of the development code without the ability to to do a schema refresh, and control when they get new versions by configuring a new schema via URL.

Once we are done with beta testing, our releases will be from our production partition, so this will no longer be an issue.

Regards,

Edward
Post Reply