| Summary: | Uploading spreadsheet in creating a new rule, or creating new assets such as RulesFlow can generate ugly but non-fatal error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||
| Component: | User Interface | Assignee: | Mark Little <mark.little> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.0.0 CR1 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.1.0 GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/BRMS-100 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
April 17 CR1
|
|||||
| Last Closed: | 2010-11-22 19:12:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Len DiMaggio
2009-05-01 01:32:06 UTC
Link: Added: This issue depends GUVNOR-282 The problem is more wide-spread - creating files, RulesFlows, Functions, Models, Enumerations - all these tasks - and I can recreate this on a clean/empty repo after an install - raise a dialog with this error: "Unable to validate package configuration (eg, DSLs, models) for [packagename]. Suggestion completions may not operate correctly for graphical editors for this package." The user can safely close the dialog and ignore the error, but it is very awkward. Multiple screen shots. Attachment: Added: screenshots.zip Does this happen *after* you delete a DSL? If yes, then it's strictly related to BRMS-115 - you have a rule (thirdRule) that relies on this DSL. Link: Added: This issue related BRMS-124 Draft text for release note states: https://jira.jboss.org/browse/GUVNOR-282 An error message would appear if the user selected a spreadsheet to upload into a rule. This was because the system was attempting to build the package each time so that it could obtain a classloader for suggestion completion. The software has been changed so that it no longer builds the package each time. It now obtains the requisite classloader from a JAR. As a result, the error message no longer appears. Writer: Added: dlesage Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: test Release Notes Text: Removed: test Steps to Reproduce: Added: Draft text for release note states: https://jira.jboss.org/browse/GUVNOR-282 An error message would appear if the user selected a spreadsheet to upload into a rule. This was because the system was attempting to build the package each time so that it could obtain a classloader for suggestion completion. The software has been changed so that it no longer builds the package each time. It now obtains the requisite classloader from a JAR. As a result, the error message no longer appears. Release Notes Text: Added: Draft text for release note states: https://jira.jboss.org/browse/GUVNOR-282 An error message would appear if the user selected a spreadsheet to upload into a rule. This was because the system was attempting to build the package each time so that it could obtain a classloader for suggestion completion. The software has been changed so that it no longer builds the package each time. It now obtains the requisite classloader from a JAR. As a result, the error message no longer appears. Steps to Reproduce: Removed: Draft text for release note states: https://jira.jboss.org/browse/GUVNOR-282 An error message would appear if the user selected a spreadsheet to upload into a rule. This was because the system was attempting to build the package each time so that it could obtain a classloader for suggestion completion. The software has been changed so that it no longer builds the package each time. It now obtains the requisite classloader from a JAR. As a result, the error message no longer appears. Cannot reproduce the error with BRMS 5.1 ER4 build - closing. |