Bug 784970

Description of problem:

This issue was identified due to a TCK failure.
When the TCK was comparing the toString() of the original destination to the one it used in a QueueBrowser, the test failed. Upon closer inspection a subtle change was noted.

Original destination toString()
'MY_QUEUE'/None; {
  'create': 'always'
} 

The destination created by using the toString()
'MY_QUEUE'/'None'; {
  'create': 'always'
}

Notice the None is quoted in the second string. The code prints None in place of a Null subject to make an address string more readable. Therefore if a new destination is created from a toString() of a destination, the code needs to identify the 'None' in the subject field as null.

Version-Release number of selected component (if applicable):
All release java rpms which supports addressing

How reproducible:
Always

Steps to Reproduce:
Address addr = Address.parse("MY_QUEUE; {create : always}");
System.out.println("Addr1 : " + addr);
		
Address addr2 = Address.parse(addr.toString());
System.out.println("Addr2 : " + addr2);
  
Actual results:
'MY_QUEUE'/'None'; {
  'create': 'always'
}

Expected results:
'MY_QUEUE'/None; {
  'create': 'always'
}

Additional info:
Note the missing quotes around "None" in the expected results when comparing with actual results.