[
https://jira.jboss.org/jira/browse/SOAG-40?page=com.atlassian.jira.plugin...
]
Gary Brown resolved SOAG-40.
----------------------------
Fix Version/s: 1.0 CR1
Resolution: Done
Issue was that validation related to Java classes needed to be performed after the Java
builder had completed the compilation of the required Java code. This was achieved by
re-issuing the validation after the creation of new class files had been detected - being
scheduled as a Job, so that it would only be performed after the builder had finished.
Project import validation and conformance errors not being resolved
once all files imported
-------------------------------------------------------------------------------------------
Key: SOAG-40
URL:
https://jira.jboss.org/jira/browse/SOAG-40
Project: SOA Governance
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 CR1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira