tracker issue : CF-4195914

select a category, or use search below
(searches all categories and all time range)
Title:

GetComponentMetadata incorrectly displaying parent components full name when using relative names

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Geoffrey Demoulin / Geoffrey Demoulin (Geoffrey Demoulin)

Created: 10/11/2016

Components: Core Runtime

Versions: 2016,11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final / 302196

Priority/Frequency: Major / All users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 0

Listed in the version 2016.0.04.302561 Issues Fixed doc
Problem Description:

When calling GetComponentMetadata on a component extending a parent component located in an other directory by referencing it relatively, the parent fullname property will contain a "/" char instead of a "." (ie. FULLNAME = "my.base/Component2").

Steps to Reproduce:

1/ Create a project using the attached zip "testmetadatafail.zip". Components are extending relatively to their location.
2/ Run the index.cfm file. A dump will be displayed.

Actual Result:

The dump will show: "my.Component3" -> extends -> "my.base/Component2" -> extends "my.folder/Component0"
The components names are malformed (usage of the "/" char) and, worse, incorrect (Component0).

Expected Result:

The dump should show: "my.Component3" -> extends -> "my.base.Component2" -> extends "my.base.folder.Component0"

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4195914

External Customer Info:
External Company:  
External Customer Name: Geoffrey Demoulin
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

  1. October 11, 2016 00:00:00: 1_testmetadatafail.zip
  2. October 11, 2016 00:00:00: 2_testmetadataok.zip

Comments:

I've attached a project to compare the issue with the expected output: "testmetadataok.zip"
Comment by External U.
1640 | October 11, 2016 12:34:49 AM GMT
Hi, Any news about this bug report? This should be quite easy to verify using the provided tests. Thanks
Comment by External U.
1641 | October 30, 2016 04:50:36 PM GMT
Hi, This bug report has been opened for weeks, any feedback on this? Thank you!
Comment by External U.
1642 | November 07, 2016 07:55:28 PM GMT