Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1023597 - Connection properties are not persisted with non-XA datasource creation
Connection properties are not persisted with non-XA datasource creation
Status: CLOSED CURRENTRELEASE
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6 (Show other bugs)
JON 3.1.2
Unspecified Unspecified
unspecified Severity high
: DR01
: JON 3.2.1
Assigned To: Thomas Segismont
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-25 17:30 EDT by David
Modified: 2014-05-08 13:43 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-08 13:43:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 526273 None None None Never

  None (edit)
Description David 2013-10-25 17:30:54 EDT
Description of problem:
When Creating a non-XA datasource via JON GUI, custom property-name:value pairs entered in Connection Property interface are not reflected in datastore, requiring a second pass after creation

Version-Release number of selected component (if applicable):
JON 3.1.2.GA
Build Number :	
323587d:38819b7
Agent Plugin: JBoss Application Server 7.x Version : 4.4.0.JON312GA

How reproducible:
Every time.  Create a non-XA datasource, fill values for fields, add a custom value pair in the bottom section,

Click finish.



Steps to Reproduce:
1.Create a non-XA datasource, fill values for fields, add a custom value pair in the bottom section 
2.Click finish.


Actual results:
Datastore is created but custom parameter/value is not in standalone...xml file or shown in configuration tab in JON.

If you then go back and add the value pair again, and save, it will be reflected in JON and XML

Expected results:
Both pre-defined fields and the custom Connection Properties fields would be reflected in created datastore OR error saying can't do that.  Basically anything but a silent discard of a configured value - with a strong preference towards being able to do complete configuration in one pass.

Additional info:
Comment 1 Thomas Segismont 2014-02-11 15:36:50 EST
Fixed in master

commit 54a47ee6a3a92cfeaa65d059edf17b44f79b047b
Author: Thomas Segismont <tsegismo@redhat.com>
Date:   Tue Feb 11 10:17:52 2014 +0100
Comment 2 Libor Zoubek 2014-02-12 06:36:09 EST
Tested (including domain mode) and cherry-picked over to release/jon3.2.x

commit e4421804222d739a58c68c716907fcc85ec6c319
Author: Thomas Segismont <tsegismo@redhat.com>
Date:   Tue Feb 11 10:17:52 2014 +0100
Comment 3 Simeon Pinder 2014-02-18 10:08:16 EST
Moving to ON_QA as available for testing in the following brew build:
https://brewweb.devel.redhat.com//buildinfo?buildID=336752

Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA.  How this will be delivered to customers is still being discussed.
Comment 4 Mike Foley 2014-02-18 15:38:32 EST
Verified JON 3.2.1 DR1
Comment 5 Mike Foley 2014-05-08 13:43:44 EDT
JON 3.2.1 released week of 5/5/2014

Note You need to log in before you can comment on or make changes to this bug.