[Opaltoolkit-users] Automatic Interface Generation Bugs

[Sriram K. <sr...@sd...>]

Hi,

I think I found a bug in the automatic interface generation. I have  
an application that has only untagged params - and no flags or tagged  
parameters. If I try to generate an interface from it, the generator  
throws an exception - Can not get application configuration file from  
remote server. On digging deep, it appears as if it requires the  
metadata to contain flags. This is the Tomcat error -

2008-02-26 14:21:27,580 ERROR  
edu.sdsc.nbcr.opal.gui.actions.CreateSubmissionFormAction.parseAppMetada 
ta(CreateSubmissionFormAction.java:214) - PARSER: Impossible to get  
the appMetadata from the Opal server. Error: null
java.lang.NullPointerException
         at edu.sdsc.nbcr.opal.gui.common.AppMetadata.getArgFlagId 
(AppMetadata.java:196)
         at  
edu.sdsc.nbcr.opal.gui.actions.CreateSubmissionFormAction.parseGroup 
(CreateSubmissionFormAction.java:299)
         at  
edu.sdsc.nbcr.opal.gui.actions.CreateSubmissionFormAction.parseAppMetada 
ta(CreateSubmissionFormAction.java:199)

Sure enough, if I add a dummy flag, it works ok (except of course, if  
I click on the flag the application fails because it doesn't expect  
the flag). I am attaching the config file for my app  - along with  
the extra flag. Check it out - you can then get rid of the flags, and  
see that it fails.

Also, the generator doesn't do BOOL correctly. It basically creates a  
text box, while it should create a drop down list or radio buttons  
with true/false. I had to change the BOOL to STRING, and give it a  
list of values (true, false) for it to look acceptable.

Sriram