[JBoss JIRA] Created: (SOAG-63) Extend WhileAction to cater for external decision using lookahead based on message type
by Gary Brown (JIRA)
Extend WhileAction to cater for external decision using lookahead based on message type
---------------------------------------------------------------------------------------
Key: SOAG-63
URL: https://jira.jboss.org/jira/browse/SOAG-63
Project: SOA Governance
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Conversation Runtime
Affects Versions: 1.0 CR1
Reporter: Gary Brown
Assignee: Mark Little
Currently, the WhileAction is only used to control repetition, and therefore the action provides the expression to be evaluated. This is sufficient for the examples that have been provided.
However, if the while loop needs to be represented within a service, that needs to "observe" the decision as to whether it should loop or exit, then it will be necessary to specify the relevant message types - similar to the way the SwitchAction works, using message types to determine which path to take.
--
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
16 years, 2 months
[JBoss JIRA] Resolved: (SOAG-39) Changes to error highlighting when displaying jboss-esb.xml error in XML editor
by Gary Brown (JIRA)
[ https://jira.jboss.org/jira/browse/SOAG-39?page=com.atlassian.jira.plugin... ]
Gary Brown resolved SOAG-39.
----------------------------
Fix Version/s: 1.0 CR1
Resolution: Done
Implemented single line highlighting in the XML editor.
> Changes to error highlighting when displaying jboss-esb.xml error in XML editor
> -------------------------------------------------------------------------------
>
> Key: SOAG-39
> URL: https://jira.jboss.org/jira/browse/SOAG-39
> Project: SOA Governance
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Tooling
> Affects Versions: 1.0 CR1
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0 CR1
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Currently an error on an action or property in the action results in the complete Action being highlighted as an error.
> Suggestion is to just highlight the first line of the Action, if the error is related to the complete action, or highlight the property within the action if property related.
> However, if a graphical editor is being used to show the ESB config, then focusing on the complete action (i.e. graphical component) may be all that is possible, as Eclipse does not provide default behaviour for focusing on individual properties.
--
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
16 years, 2 months
[JBoss JIRA] Resolved: (SOAG-40) Project import validation and conformance errors not being resolved once all files imported
by Gary Brown (JIRA)
[ 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
16 years, 2 months