[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Unexpected canonicalization of string

[alesj]

"alesj" wrote : 
  | But I guess you'll have to add similar behavior to ServiceMetaDataParser.
  | 
Or not. :-)

I think StringValueMetaData should not modify its input.
I've modified AbstractValueMetaData to check at setValue invocation
if it should use the JMXObjectNameFix:

  |    public void setValue(Object value)
  |    {
  |       if (isUseJMXObjectNameFix())
  |       {
  |          Object jmxHack = JMXObjectNameFix.needsAnAlias(value);
  |          if (jmxHack != null)
  |          {
  |             this.value = jmxHack;
  |             flushJBossObjectCache();
  |             return;
  |          }
  |       }
  |       this.value = value;
  |       flushJBossObjectCache();
  |    }
  | 
Where StringValueMetaData now returns false on isUseJMXObjectNameFix call.

Non canonicalized string. ;-)
  assertEquals("jboss.remoting:service=JMXConnectorServer,protocol=rmi", binding.getServiceName());
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169764#4169764

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169764