Bug 751326 - ResourceChangeScanner fails to scan CSV resource
Summary: ResourceChangeScanner fails to scan CSV resource
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRE (Expert, Fusion)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: BRMS 5.3.0.GA
Assignee: Nobody
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 10:47 UTC by Jiri Svitak
Modified: 2023-05-01 08:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The KnowledgeAgent's ResourceChangeScanner failed to scan CSV, XLS, and BPMN2 resources and threw an illegalStateException. This has been resolved and error no longer occurs.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
test case (3.07 KB, application/x-zip-compressed)
2011-11-04 10:47 UTC, Jiri Svitak 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 733008 0 unspecified VERIFIED ResourceChangeScanner fails when trying to scan package from Guvnor 2023-05-15 19:53:53 UTC
Red Hat Bugzilla 741219 0 unspecified VERIFIED ResourceChangeScanner fails to scan XLS resource 2023-05-15 19:53:50 UTC
Red Hat Bugzilla 741287 0 unspecified VERIFIED ResourceChangeScanner fails to scan DRF resource 2023-05-01 08:28:14 UTC
Red Hat Bugzilla 751319 0 unspecified VERIFIED ResourceChangeScanner fails to scan BPMN resource 2023-05-01 08:28:21 UTC
Red Hat Issue Tracker JBRULES-3358 0 Major Closed Fix reload of KnowledgeAgent resources: CSV, XLS, BPMN, DRF, PKG 2014-07-04 05:49:42 UTC

Internal Links: 733008 741219 741287 751319

Description Jiri Svitak 2011-11-04 10:47:50 UTC 
Created attachment 531744 [details]
test case

Description of problem:
IllegalStateException is thrown when trying to scan a BPMN2 file resource using
ResourceChangeScanner of the KnowledgeAgent. So BPMN process is not hotdeployable
as a result. The same exception occurs in ResourceChangeScanner with XLS, CSV,
DRF, BPMN and PKG of Guvnor.

Version-Release number of selected component (if applicable):
BRMS 5.3.0 DEV4

How reproducible:
Run attached test case.

Steps to Reproduce:
1. Unzip test case.
2. Run as Java app.
  
Actual results:
CSV resource is not hotdeployable.

Expected results:
All resources in changeset specification should be hotdeployable.
Comment 1 Edson Tirelli 2012-01-23 20:35:12 UTC 
This is fixed for XLS, CSV and BPMN. Working on the PKG under the other open ticket for this.
Comment 2 JBoss JIRA Server 2012-01-23 21:50:34 UTC 
Edson Tirelli <ed.tirelli> updated the status of jira JBRULES-3358 to Resolved
Comment 3 JBoss JIRA Server 2012-01-23 21:50:38 UTC 
Edson Tirelli <ed.tirelli> updated the status of jira JBRULES-3358 to Closed
Comment 4 Ryan Zhang 2012-02-15 09:12:05 UTC 
Please verify the issue on 5.3 ER4.
Comment 5 Jiri Svitak 2012-02-21 09:55:59 UTC 
Verified in 5.3 ER4.
Comment 7 lcarlon 2012-06-06 01:52:31 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The KnowledgeAgent's ResourceChangeScanner failed to scan CSV, XLS, and BPMN2 resources and threw a illegalStateException. This has been resolved and error no longer occurs.
Comment 8 lcarlon 2012-06-06 02:21:26 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-The KnowledgeAgent's ResourceChangeScanner failed to scan CSV, XLS, and BPMN2 resources and threw a illegalStateException. This has been resolved and error no longer occurs.+The KnowledgeAgent's ResourceChangeScanner failed to scan CSV, XLS, and BPMN2 resources and threw an illegalStateException. This has been resolved and error no longer occurs.
Note You need to log in before you can comment on or make changes to this bug.