tracker issue : CF-4100649

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

Using component FQDN as returnType is case-sensitive but using component name as returnType not

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): Jork Zijlstra / Jork Zijlstra (Jork Zijlstra)

Created: 12/16/2015

Components: Language

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / All users will encounter

Locale/System: English / Linux All

Vote Count: 1

Problem Description:
There is a difference in how the returnType of a method is handled when using a component name or a component FQDN.

The component return is new v1.TestCase()
case 1) private testcase function x(){} is case insensitive
case 2) private v1.testcase function x(){} is case sensitive and this example fails
case 3) private v1.TestCase function x(){} is case sensitive

Steps to Reproduce:
see attached zip file for testcode

Actual Result:
Actual Result:
1) returns object
2) causes EventHandlerException The value returned from the x function is not of type v1.testCase
3) returns object

Epected Result:
Make it uniform, all case sensitive or all case insensitive

Any Workarounds:
Use correct casing for FQDN as returnType

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

Watson Bug ID:	4100649

External Customer Info:
External Company:  
External Customer Name: Jork Zijlstra
External Customer Email:  
External Test Config: My Hardware and Environment details:

Ubuntu 14.04, CF10,0,18,29633

Attachments:

  1. December 16, 2015 00:00:00: 1_returnTypeCaseSensitive.zip

Comments:

+1. Makes no sense for this to not be treated uniformly.
Vote by External U.
5079 | December 16, 2015 08:16:04 AM GMT
Jork, Can you please confirm if the test code attached is correct? I see case 1 and case 2 are effectively the same.
Comment by Immanuel N.
5075 | January 12, 2016 01:47:31 AM GMT
Jork, We are unable to reproduce this issue Can you please provide a repro case?
Comment by Immanuel N.
5076 | February 24, 2016 05:19:07 AM GMT
Nope. I also no longer have access to the environments to further test this behavior. The only thing I can think of is that our codebase is accessed over an NFS mount which causes the case sensitivity, but then again I can't test it anymore,
Comment by External U.
5077 | February 25, 2016 04:47:56 AM GMT
Closing the bug as Cannot Reproduce. Please revert back if you see this issue again. The bug can then be reopened.
Comment by Immanuel N.
5078 | July 22, 2016 12:29:47 AM GMT