Bug 605767

Summary: QMF mangles class names
Product: Red Hat Enterprise MRG Reporter: Justin Ross <jross>
Component: qpid-qmfAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: Development   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Justin Ross 2010-06-18 18:17:07 UTC 
A class called "JobServer" in the schema is sent as "jobserver" over the wire.  Ken says this is due to the behavior of the qmf code generator.

I think this is a bad practice, though it's not a terrible state of affairs, and it's apparently difficult to fix now.

As to why it's bad: it recently served as the background for a bug in mint.  In an effort to recapture the original class names, mint had logic in place to take the value of ClassKey.getClassName() and capitalize its initial letter so it would match the metadata, which contains classes by their as-written (capitalized) form.

This worked until JobServer came along.  It has a cap in the middle.  (I've now introduced a lowercased index of classes to use instead, so the problem is addressed in a general fashion.)

Nonetheless, mangling class names causes unnecessary confusion for implementors.