Verifying WAD windows before generating them

Although developing automatic windows in Openbravo ERP is quite straight forward and saves a lot of coding time, in case something goes wrong it can be difficult to find out where the problem is. Of course you have the compilation log, but this is not always as user friendly as it should be. In many occasions, it is quite hard to figure out the root cause for the error. It must be inferred from a ton of lines of log and some times it fails in a place that it is not expected, for example a missing identifier for a table can cause a SQL error.

Currently we are working on improving the build process, and one of the improvements we are putting in place (it is already pushed to pi) is a verifier that is run before generating WAD windows, this verifier will check a number of common mistakes that make the tabs not to be properly generated and will display a clear message about this stopping the process.

The idea is to gradually include new checks to this verifier, now we just look for tables without identifier and for tables without primary key. Any feedback on which checks would be useful is welcome.

I hope this makes life a little bit easier to Openbravo ERP developers.


7 thoughts on “Verifying WAD windows before generating them

  1. Francesco Finamore says:

    Good idea :
    for example one common error is when you create a tab on a window and give it a name with the first lowercase letter.
    When compile it gives an error but you can’t understand the problem.
    For example you write “book” and the wad search “Book” and can’t find it and gives an error not clear.


  2. Francesco says:

    Thank you for info .
    Other feedback for you :

    1) When you create on the db a table with type date in some field , when you create the field on the A.D. table the type is “String” so if you dont check it , the compiling operation goes fine but when you try to save , the system raise an error of type.

    2) Sometime forgetting the right type, i put the fields dedicated to a button with type “characher varying (1)” and it seems all ok , but when i go to export.database the ant task fails because it says the field must be “characher(1)” :))


  3. ma7moud says:

    eclipse.refreshLocal] Warning: project OpenbravoWAD does not exist and cannot be refreshed.

    E:\Openbravo-3.0MP17.1\build.xml:699: The following error occurred while executing this line:
    Target “eclipse.trl.lib” does not exist in the project “openbravo”.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s