Project import validation errors not being revalidated
Status: Pre-Alpha
Brought to you by:
objectiser
Menu
▾
▴
#5 Project import validation errors not being revalidated
When a project is being imported, validation and conformance checking is being performed on the files as they are imported - however not all of the dependent files are present at the point the validation is performed, resulting in some temporary errors.
However, once the full project has been imported, the temporary should have been resolved by triggering re-validation of the ESB configuration files. This does not appear to be happening.
The most common problem appears to be unable to find the class associated with the 'session' property. This may be due to the fact that , although the Java file is imported, the actual build of the Java class does not occur until after the import, when the Java builder kicks in.
Might need to establish dependency on class file being added/modified, and treat as being the same as the Java type it represents.
Logged In: YES
user_id=1091755
Originator: YES
Partially resolved, as resources were being validated multiple times (due to multiple dependencies) concurrently - this has now been resolved.
However the main problem occurs because the imported project already has existing 'compiled' classes/jboss-esb.xml - but they are not marked as 'derived' resources until the Java builder processes them. The validation ignores derived resources, so this is usually not a problem - but during import, and prior to the Java builder being invoked, these files temporarily are not 'derived' and therefore get validated.
Longer term solution required for this - but currently should not be a problem in situations where projects are imported without the compiled classes/resources.