Bug 1015531 - KieExpander adds all artifacts as 'Document'
Summary: KieExpander adds all artifacts as 'Document'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: DT Governance
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER7
: 6.0.0
Assignee: Kurt T Stam
QA Contact: Stefan Bunciak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 13:01 UTC by Kurt T Stam
Modified: 2014-02-06 15:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SRAMP-243 0 Major Closed Fix KieExpander 2014-01-23 06:34:46 UTC

Description Kurt T Stam 2013-10-04 13:01:16 UTC 
Description of problem:

The KieIntegration is not setting the correct Extended Models causing all artifact to show as 'Document' rather then for example BpmnDocument for bpmn files.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 JBoss JIRA Server 2013-10-10 15:41:44 UTC 
Kurt Stam <kurt.stam> updated the status of jira SRAMP-243 to Resolved
Comment 3 JBoss JIRA Server 2013-10-10 15:41:50 UTC 
Kurt Stam <kurt.stam> updated the status of jira SRAMP-243 to Closed
Comment 4 Stefan Bunciak 2014-01-07 10:20:47 UTC 
As I mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1015251#c4, the KieExpander is not working properly and even it's not classifying derived artifacts as 'Document', the types are still not completely correct. E.g. kmodule.xml is not classified as 'KieXmlDocument' but 'XmlDocument'.
Comment 5 kconner 2014-01-22 20:43:14 UTC 
Kurt added the following comment on 1015251

"Hi Stefan, are you setting the type to KieJarArchive? If you are not it will default to 'Document'."

Could you please double check?
Comment 6 Jiri Pechanec 2014-01-23 06:34:40 UTC 
CR1 - when the import type is explicitly set to KieJarArchive then the import is executed properly
When import is not set it guesses it as JarArchive and the behaviour is the same is described above
Note You need to log in before you can comment on or make changes to this bug.