Sequencers currently write their sequenced data through the SequencerOutputMap object. SequencerOutputMap exposes two methods to set properties, both of which take the relative path to the node, the name of the property, and the values to set. The first version of the setProperty method takes a Path, a Name, and set of Objects. This version doesn't depend on namespace mappings. The second version takes a String for the path, a String for the property name, and a set of Objects for the values. This version requires the first two arguments to be converted into a Path and Name. The conversion process is dependent on the current namespace mappings, of course.

The first problem with setProperty(String, String, Object...) is that it requires extra effort to do the conversion from Strings to a Path and Name. The second (bigger) problem is that this conversion is dependent on the current namespace mappings at the engine level, which cannot be manipulated from the JCR repositories. This leads to issues like the one in the forum post at http://community.jboss.org/message/544783#544783. The third problem is that all of our sequencers in trunk use the second method.

If we deprecate the setProperty method and convert all of our sequencers in trunk, we could avoid the problem in the attached post. This would also likely forestall the need to provide configuration support for engine-level namespace mappings.