Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168309

Summary: The publish areas defined by the sequencer is not being created, which requires tooling user to know what it is
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Van Halbert <vhalbert>
Component: ModeShapeAssignee: Thomas Hauser <thauser>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, felias, fnguyen, hchiorea, vhalbert
Target Milestone: ER5Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:48:30 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:
Embargoed:

Description Van Halbert 2014-11-26 16:15:52 UTC
In the standalone.xml configuration, the modeshape sequencers are defining the publish area to be used, and where the user should be publishing artifacts in order for them to be sequenced.  Example:

 <sequencer name="teiid-vdb-sequencer" classname="vdb" module="org.modeshape.sequencer.teiid" path-expression="/files(//*.vdb[*])/jcr:content[@jcr:data] => /derived/teiid/vdbs/$1"/>
                   

The above indicates the user should publish artifacts to the "/files" publish area.  

However, when using the ModeShape tooling in JBDS, there are no default publish areas being presented to the user.  They must create that publish ares.  

Unfortunately, the user doesn't necessarily know what that publish area they need to create unless they know to goto the server and look here.   So what happens is, the user creates anything they want, but doesn't realize that if they don't use "files", that their artifacts will not be sequenced.

Can Modeshape server component automatically create the available publish area's based on how the sequencer is configured?

Comment 2 JBoss JIRA Server 2014-11-27 07:51:50 UTC
Horia Chiorean <hchiorea> updated the status of jira MODE-2378 to Resolved

Comment 3 Horia Chiorean 2014-11-27 07:53:21 UTC
The section of the CLI scripts which installs the ModeShape DV repository should be changed to:

/subsystem=modeshape/repository=dv:add(cache-container="modeshape",cache-name="dv",security-domain="modeshape-security",use-anonymous-upon-failed-authentication="false",anonymous-roles=["readonly"], default-initial-content="initial-content-default.xml")

This will ensure that when the server is started, ModeShape will create by default the "files" publish area.

Comment 4 Thomas Hauser 2014-12-01 21:22:34 UTC
I've applied the required changes to the cli-script used to install ModeShape.

Comment 5 JBoss JIRA Server 2014-12-15 07:15:21 UTC
Horia Chiorean <hchiorea> updated the status of jira MODE-2378 to Reopened

Comment 6 JBoss JIRA Server 2014-12-30 08:38:58 UTC
Horia Chiorean <hchiorea> updated the status of jira MODE-2378 to Closed