Menu
▾
▴
#97 Flexible application version in GridBeans
The application version in GridBeans should be more
flexible.
Example:
A povray job that would run fine on any version >3.0
of POVRay. Probably the user should even have the
option to specify the required version in the POVRay
GUI.
The corresponding code in the
TargetSystemDatabaseImpl would also have to be
modified. I think currently the app version is
ignored anyway.
Logged In: YES
user_id=1038690
Originator: YES
Currently version 3.5 is hard-coded in the POVRay GridBean and has to be configured on the server side as well, even though a different version may actually be used. A more flexible way of specifying the version would be desirable (e.g. >=3.5). However, we don't want to introduce this change now, but maybe we could find a simple solution and demonstrate it in the POVRay GridBean:
I tried simply not to specify the version in the POVRay GridBean and ran into two problems:
1. The job appeared as "POVRay - null" in the job list. The "- null" should not be displayed here.
2. The job actually failed, even though it appeared as SUCCESSFUL in the client. Is this is a server-side problem?
As an alternative we could query the available version from the TS and put it into the JSDL.
Logged In: YES
user_id=1038690
Originator: YES
postponed until 1.5: requires change of GB API