Adding support for system property reference replacement

[starksm64]

We have so many places that depend on being able to replace system property references, this is going to be a roadblock to migrating configuration files over to parsing using the jbxb framework unless it also supports this.

It seems the best place to to this is the org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler (Alexey is still killing me with the naming).

We would need configuration to suppress the replacement. This could be done globally as well as on each attribute/element/text. Its not clear where to do this for the individual elements because other than text, we don't have a binding element.

I'm going to add the global configuration control to the schemaBindings and add this replacement support so I can finish integration of jbxb into the sar deployer.

[adrian.brock]

We need to decide who is responsible for doing this replacement and that there
is a well understood protocol/api, so it is not done twice. e.g. see
http://jira.jboss.com/jira/browse/JBAS-2039

The problem with the Properties PropertyEditor is still outstanding.

[starksm64]

If its to be consistent, I think only the first layer that does the processing of the deployment layer should be doing any transformation of the values. As such, the current parsing of property references by the jboss PropertiesEditor is also incorrect and is a source of another double parse issue.

http://jira.jboss.com/jira/browse/JBAS-1888

[dimitris]

Do you remember what was the original need for PropertiesEditor doing the replacement? From cvs I see this is done since 3.2.4

[starksm64]

It was simply to add support to Properties type of attributes before there was consistent processing of any xml text at the SARDeployer level. It should have been added to the SARDeployer at that point.

Now, as the SARDeployer gets migrated to using jbossxb, it should be delegated to the jbossxb layer.