Bug 1408846

Summary:	[GSS](6.4.z) Class names with $ generates a warning
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	Server	Assignee:	jboss-set
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	medium	Docs Contact:	eap-docs <eap-docs>
Priority:	unspecified
Version:	6.4.12	CC:	harshada, ihradek, jason.greene, msochure, pjurak, pmackay
Target Milestone:	CR1
Target Release:	EAP 6.4.14
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-23 08:25:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1401452

Description Brad Maxwell 2016-12-27 17:06:50 UTC

When a class name with $ is loaded, a warning was logged

WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015893:
Encountered invalid class name
'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for service
type 'javax.ws.rs.ext.MessageBodyReader'

But as http://docs.oracle.com/javase/specs/jls/se7/html/jls-3.html#jls-3.8, the $ is a valid character:

The "Java letters" include uppercase and lowercase ASCII Latin letters A-Z (\u0041-\u005a), and a-z (\u0061-\u007a), and, for historical reasons, the ASCII underscore (_, or \u005f) and dollar sign ($, or \u0024).
The $ character should be used only in mechanically generated source code or, rarely, to access pre-existing names on legacy systems.

More info about this warning: https://access.redhat.com/solutions/263373

Comment 3 Peter Mackay 2017-02-28 09:36:56 UTC

Verified with EAP 6.4.14.CP.CR1

Comment 4 Petr Penicka 2017-03-23 08:25:19 UTC

Released with EAP 6.4.14 on March 14 (ZIPs) and March 22 (RPMs).