Bug 605767 - QMF mangles class names
Summary: QMF mangles class names
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf   
(Show other bugs)
Version: Development
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-18 18:17 UTC by Justin Ross
Modified: 2011-08-12 16:05 UTC (History)
0 users

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: ---


Attachments (Terms of Use)

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.


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