Camel PropertiesComponent ignores custom parser in Blueprint

Solution Verified - Updated -

Issue

  • We have implemented a custom PropertiesParser which allows us to use system property placeholders in propertyPrefix and propertySuffix.
  • In the use case the propertyPrefix is defined as ${container.stage}, where container.stage is a jvm option defined at container creation. The value is one of a, b and c.

  • This works fine in Java DSL world (SCR bundle), but custom parser is ignored in Blueprint.

Environment

  • Red hat JBoss Fuse
    • 6.1.0
  • Apache Aries Blueprint

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.