If the configuration is not processed concurrently (is it even possible?), the easiest way to implement this feature could be using ThreadLocal.
I don't see how that might help though - the binding occurs with JAXB so by the time a deployer gets ahold of the data, it's already in an object model, so any location info would have already been lost.
Ah, we are using JAXB. I thought we are something like SAX. Sorry about the noise.
Then, what about improving JBoss JAXB itself to maintain a complete map that maps an object property to the location of the XML file? For example:
Location l = map.getLocation(object, "bindAddress");
String path = l.getPath();
int lineno = l.getLineNumber();
int column = l.getColumn();
This map and location information could be written generic enough so that it can be used with different configuration file formats, as long as the configuration parser (JAXB implementation in the case above) puts the appropriate information when it processes the configuration file.
I hope my idea makes sense this time. :)