Hi Matthew, can you provide a quick rationale and use case of this change ?
Thanks, Regards JB On 07/07/2019 01:13, Matthew Zipay wrote: > Hi, > > I am interested in submitting a patch to add support for augmented > properties with fallback to Blueprint property placeholders (analogous to > Camel's propertyPlaceholder and its @propertyPrefix, @propertySuffix and > @fallbackToUnaugmentedProperty attributes). I've implemented this as a > customization on a couple projects, but I think there would be value in > having this behavior built in to Blueprint. > > Firstly, is there any interest in having this behavior in Blueprint? > > If so, I have a couple questions before I open a JIRA ticket and submit the > PR: > > 1) My changes touch the blueprint-cm, blueprint-core and blueprint-noosgi > submodules. One of the changes I've had to apply is to bump the dependency > version of blueprint-core in the blueprint-cm and blueprint-noosgi POMs > (from 1.10.0 to 1.10.3-SNAPSHOT). Is this acceptable, or is there a > preferred alternative way to handle this? > 2) My changes require modifications to the blueprint-cm and blueprint-ext > schemas. Looking at the history of these schemas, I see that their minor > versions have been incremented in the past when new attributes are added to > the property-placeholder element (which is exactly what I need to do). So > I have gone ahead and introduced blueprint-cm-1.5.0.xsd and > blueprint-ext-1.7.0.xsd > (with appropriate corresponding changes in the namespace handlers). Is > this the preferred way to handle this case? > > Thanks! > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
