<< Back to previous view

[GLASSFISH-19352] An empty string ("") can be set for clientID Created: 16/Nov/12  Updated: 01/Jul/13  Resolved: 01/Jul/13

Status: Resolved
Project: glassfish
Component/s: jms
Affects Version/s: 4.0_b45
Fix Version/s: 4.0_b89_RC5

Type: Bug Priority: Trivial
Reporter: tak09 Assignee: David Zhao
Resolution: Invalid Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Glassfish v4.0 b45
Windows 7


File Attachments: PNG File clientid.png     Zip Archive setClientID.zip    
Tags:
Participants: David Zhao and tak09

 Description   

An empty string ("") can be used when setting a clientID using GUI or setClientID() method.

1. Set ("") in the Resources > JMS Resources > Connection Factories > Connection Factory Name Additional Properties. If you click Save, it is saved successfully. (Bug) Please see the attachment file.

2. When "" is used for setting clientID, it is compiled and executed without an error. (Bug) See the attachment file for the use of setClientID("\"\"").

3. When asadmin is used for setting an empty string ("") in clientID, this operation fails. (Working as expected. Not a bug)

C:\GFFeedback\3043ClientID\TP\setClientID\run>C:\glassfish\glassfish-4.0-b45\glassfish3\glassfish\bi
n\asadmin create-jms-resource --restype javax.jms.ConnectionFactory --property ClientID=^"^\^"^\^"^"
 jms/ConnectionFactory001
remote failure: Unable to create connection pool.
Invalid property syntax, missing property value: ClientID=
Command create-jms-resource failed.

^ is an escape sequence character in MS-DOS.



 Comments   
Comment by David Zhao [ 01/Jul/13 02:31 AM ]

In the admin gui, the value is escaped by default. So if you input "" for ClientID property, then the value stored in domain.xml will be "" with no change. If you want to test empty string for the property, you should leave the value field blank and then click Save button, thus the property will not be saved, which is expected.

Generated at Mon Apr 21 02:42:43 UTC 2014 using JIRA 4.0.2#472.