Bug 1048717 - Opening audit log from BRMS5 throws internal error
Summary: Opening audit log from BRMS5 throws internal error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: ---
Assignee: Kris Verlaenen
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-06 08:44 UTC by Tomas Schlosser
Modified: 2014-08-06 19:57 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:57:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Error report from JBDS (10.58 KB, text/plain)
2014-01-06 08:44 UTC, Tomas Schlosser 		no flags Details
View All

Description Tomas Schlosser 2014-01-06 08:44:27 UTC 
Created attachment 845962 [details]
Error report from JBDS

Description of problem:
If you open log generated by BRMS 5.x runtime, you get an Internal error in Drools Plugin.

Version-Release number of selected component (if applicable):
JBDS 7.1.0.GA
Drools plugin 6.0.0.Final

How reproducible:


Steps to Reproduce:
1. run Drools 5 example (with Drools 5 runtime)
2. open audit view
3. open the "test.log" file

Actual results:
Internal Error

Expected results:
opened audit log

Additional info:
This is yet another problem with using internal binaries. The problem is that classes have a different package in Drools 6.
Comment 1 Kris Verlaenen 2014-02-05 02:04:35 UTC 
6.0.x: http://github.com/droolsjbpm/droolsjbpm-tools/commit/6919002d1
master: http://github.com/droolsjbpm/droolsjbpm-tools/commit/03d69efbe
Comment 2 Tomas Schlosser 2014-06-06 11:43:40 UTC 
Verified with JBTIS 7.0.2.CR1.
Note You need to log in before you can comment on or make changes to this bug.