[jira] [Created] (CAMEL-8332) Add component implementation to camel-dozer module
Keith Babo created CAMEL-8332:
-
Summary: Add component implementation to camel-dozer module
Key: CAMEL-8332
URL: https://issues.apache.org/jira/browse/CAMEL-8332
Project: Camel
Issue Type: New Feature
Components: camel-dozer
Reporter: Keith Babo
The camel-dozer component does not actually provide a Camel component
implementation today. Rather, it provides a converter loader which can be used
in combination with a set of Dozer mapping files to register a global set of
converters within a CamelContext. This issue proposes the addition of a
full-blown component implementation within camel-dozer. Advantages of this
approach include:
* The ability to manage Dozer mapping configuration on a per-endpoint basis vs.
global configuration via the converter registry.
* Dozer handles direct field assignment quite well, but does not provide other
common mapping functions OOTB. Camel can enrich Dozer via standard Dozer
extensions, e.g.
** Mapping constant values to target fields
** Support for lookup tables, using the source value as the key
** Convenience transformations for mappings (e.g. trim spaces,
convertToLowerCase, regular expression evaluation)
** Allow Camel message/exchange headers to be mapped to target fields
* The ability to surround dozer mappings with data formats to support a single,
any-to-any transformation endpoint
Here's an example of what the endpoint configuration would look like.
{noformat}
dozer:mytransform?mappingFile=dozerBeanMapping.xmlmarshalId=jsonunmarshalId=jaxbtargetModel=example.MyObject
{noformat}
An initial implementation of this component is available as a PR against the
Camel GitHub repository. Unit tests in the PR provide examples of various
transformation use cases. Many, but not all, of the features listed above are
implemented already. I can file follow-up JIRAs for additional features I have
in mind. I will also post a link to the PR and the topic branch in the issue
comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8174) Added TimeoutInflightRepository to track the long processing exchange
[ https://issues.apache.org/jira/browse/CAMEL-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313775#comment-14313775 ] Claus Ibsen commented on CAMEL-8174: Willem, we have a better solution out of the box with the default inflight repoistory. It has a browse API now, that returns details about how long time the exchange has been inflight. And its also available from JMX so end users can use that to track long processing exchanges. And for Karaf we have a Camel command also. So I would like to remove the TimeoutInflightRepository as its no longer needed, and also its code is not complete. Any thoughts? Added TimeoutInflightRepository to track the long processing exchange - Key: CAMEL-8174 URL: https://issues.apache.org/jira/browse/CAMEL-8174 Project: Camel Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 It could be helpful is we can track the long processing exchange, user can log or send alarm when getting these exchange by extending the TimeoutInflightRepository. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8329) camel-sql - May not propagate headers for operations with no resultset
Claus Ibsen created CAMEL-8329: -- Summary: camel-sql - May not propagate headers for operations with no resultset Key: CAMEL-8329 URL: https://issues.apache.org/jira/browse/CAMEL-8329 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.2, 2.15.0 See nabble http://camel.465427.n5.nabble.com/Camel-SQL-CamelSqlRetrieveGeneratedKeys-attribute-delete-all-headers-tp5762512.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313847#comment-14313847
]
Claus Ibsen commented on CAMEL-8197:
Yay that is great work.
I am working on merging your chances to the code.
You are welcome to log that separate ticket.
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard updated CAMEL-8326:
-
Attachment: test.zip
Project tested
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle:
org.apache.felix.configadmin [25],
[jira] [Resolved] (CAMEL-8329) camel-sql - May not propagate headers for operations with no resultset
[ https://issues.apache.org/jira/browse/CAMEL-8329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8329. Resolution: Fixed Fix Version/s: 2.13.4 camel-sql - May not propagate headers for operations with no resultset -- Key: CAMEL-8329 URL: https://issues.apache.org/jira/browse/CAMEL-8329 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.13.4, 2.14.2, 2.15.0 See nabble http://camel.465427.n5.nabble.com/Camel-SQL-CamelSqlRetrieveGeneratedKeys-attribute-delete-all-headers-tp5762512.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313880#comment-14313880
]
Charles Moulliard commented on CAMEL-8326:
--
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T22:58:10+02:00)
Java version: 1.7.0_51, vendor: Oracle Corporation
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313810#comment-14313810
]
Claus Ibsen commented on CAMEL-8326:
What version of Maven and JDK are you using?
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin],
[jira] [Resolved] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[ https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8226. Resolution: Fixed Thanks for the PR Deprecated feature dataSourceRef not working correctly -- Key: CAMEL-8226 URL: https://issues.apache.org/jira/browse/CAMEL-8226 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Benjamin Graf Assignee: Claus Ibsen Fix For: 2.13.4, 2.14.2, 2.15.0 If several sql endpoints are defined using dataSourceRef attribute the latest one will not get dataSourceRef removed in createEndpoint causing validation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[ https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8226: --- Fix Version/s: 2.15.0 2.14.2 Deprecated feature dataSourceRef not working correctly -- Key: CAMEL-8226 URL: https://issues.apache.org/jira/browse/CAMEL-8226 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Benjamin Graf Fix For: 2.14.2, 2.15.0 If several sql endpoints are defined using dataSourceRef attribute the latest one will not get dataSourceRef removed in createEndpoint causing validation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[ https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8226: -- Assignee: Claus Ibsen Deprecated feature dataSourceRef not working correctly -- Key: CAMEL-8226 URL: https://issues.apache.org/jira/browse/CAMEL-8226 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Benjamin Graf Assignee: Claus Ibsen Fix For: 2.14.2, 2.15.0 If several sql endpoints are defined using dataSourceRef attribute the latest one will not get dataSourceRef removed in createEndpoint causing validation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[ https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8226: --- Fix Version/s: 2.13.4 Deprecated feature dataSourceRef not working correctly -- Key: CAMEL-8226 URL: https://issues.apache.org/jira/browse/CAMEL-8226 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Benjamin Graf Assignee: Claus Ibsen Fix For: 2.13.4, 2.14.2, 2.15.0 If several sql endpoints are defined using dataSourceRef attribute the latest one will not get dataSourceRef removed in createEndpoint causing validation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[
https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313783#comment-14313783
]
Claus Ibsen commented on CAMEL-8226:
Well spotted, in fact the code is a bit wrong as the endpoint options should
overrule the component configured, the correct code would be
{code}
// endpoint options overrule component configured datasource
DataSource ds = resolveAndRemoveReferenceParameter(parameters,
dataSource, DataSource.class);
String dataSourceRef = getAndRemoveParameter(parameters,
dataSourceRef, String.class);
if (ds == null dataSourceRef != null) {
ds = CamelContextHelper.mandatoryLookup(getCamelContext(),
dataSourceRef, DataSource.class);
}
if (ds == null) {
// fallback and use component
ds = dataSource;
}
if (ds == null) {
throw new IllegalArgumentException(DataSource must be configured);
}
{code}
Deprecated feature dataSourceRef not working correctly
--
Key: CAMEL-8226
URL: https://issues.apache.org/jira/browse/CAMEL-8226
Project: Camel
Issue Type: Bug
Components: camel-sql
Affects Versions: 2.14.1
Reporter: Benjamin Graf
Assignee: Claus Ibsen
Fix For: 2.14.2, 2.15.0
If several sql endpoints are defined using dataSourceRef attribute the latest
one will not get dataSourceRef removed in createEndpoint causing validation
exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313826#comment-14313826
]
Nazarii Kukhar commented on CAMEL-8197:
---
Hi Claus,
I would mark it as finished. Here is a result xsd by this plugin
https://github.com/nkukhar/misk/blob/master/camel-blueprint.xsd.
There is one (which I can think of) corner case that it doesn't populate
documentation for base types. But I would create a separate bug/feature ticket
for this.
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8226) Deprecated feature dataSourceRef not working correctly
[ https://issues.apache.org/jira/browse/CAMEL-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313855#comment-14313855 ] ASF GitHub Bot commented on CAMEL-8226: --- Github user igarashitm closed the pull request at: https://github.com/apache/camel/pull/388 Deprecated feature dataSourceRef not working correctly -- Key: CAMEL-8226 URL: https://issues.apache.org/jira/browse/CAMEL-8226 Project: Camel Issue Type: Bug Components: camel-sql Affects Versions: 2.14.1 Reporter: Benjamin Graf Assignee: Claus Ibsen Fix For: 2.13.4, 2.14.2, 2.15.0 If several sql endpoints are defined using dataSourceRef attribute the latest one will not get dataSourceRef removed in createEndpoint causing validation exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313935#comment-14313935
]
Claus Ibsen commented on CAMEL-8197:
There are two things left to do
- include doc for abstract/base types (such as SendDefinition) which are used
by to
- the schema file in the JAR is the old schema, we should include the schema
with the documentation
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7861) Camel-Spring depends on Spring 4
[ https://issues.apache.org/jira/browse/CAMEL-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314007#comment-14314007 ] Magnus Jungsbluth commented on CAMEL-7861: -- IMHO this is a bug despite spring dm not working with spring 4 yet. I am using Gemini Blueprint with Spring 4.1 and the OSGi header of Camel's camel-spring jar is too restrictive. Camel 2.14 is officially supporting Spring 4 so it should at the very least support a version range of [3.2,4.1) ideally [3.2,5). Camel-Spring depends on Spring 4 - Key: CAMEL-7861 URL: https://issues.apache.org/jira/browse/CAMEL-7861 Project: Camel Issue Type: Bug Components: camel-spring, karaf, osgi Affects Versions: 2.14.0 Environment: Karaf 2.4.0 Spring 4.0.5 Reporter: Ray Rishty When I attempt to start camel-spring in Karaf 2.4.0, I see the below error stating that I need a version of spring between 3.2 and 4: karaf@root osgi:start camel-spring You are about to access system bundle 81. Do you wish to continue (yes/no): yes Error executing command: Error starting bundles: Unable to start bundle 81: Unresolved constraint in bundle org.apache.camel.camel-spring [81]: Unable to resolve 81.0: missing requirement [81.0] osgi.wiring.package; ((osgi.wiring.package=org.springframework.beans)(version=3.2.0)(!(version=4.0.0))) Checking out the import-package statement via osgi:headers, I see that the Spring dependency is explicitly less than 4. org.springframework.beans;version=[3.2,4), org.springframework.beans.factory;version=[3.2,4), org.springframework.beans.factory.config;version=[3.2,4), org.springframework.beans.factory.parsing;version=[3.2,4), org.springframework.beans.factory.support;version=[3.2,4), org.springframework.beans.factory.xml;version=[3.2,4), org.springframework.context;version=[3.2,4), org.springframework.context.event;version=[3.2,4), org.springframework.context.expression;version=[3.2,4), org.springframework.context.support;version=[3.2,4), org.springframework.core;version=[3.2,4), org.springframework.core.io;version=[3.2,4), org.springframework.expression;version=[3.2,4), org.springframework.expression.common;version=[3.2,4), org.springframework.expression.spel.standard;version=[3.2,4), org.springframework.expression.spel.support;version=[3.2,4), org.springframework.jmx.export.annotation;version=[3.2,4), org.springframework.jmx.export.assembler;version=[3.2,4), org.springframework.jmx.export.metadata;version=[3.2,4), org.springframework.osgi.context;resolution:=optional;version=[1.2,2), org.springframework.remoting.support;version=[3.2,4), org.springframework.scheduling;version=[3.2,4), org.springframework.scheduling.concurrent;version=[3.2,4), org.springframework.scheduling.support;version=[3.2,4), org.springframework.transaction;version=[3.2,4), org.springframework.transaction.support;version=[3.2,4), org.springframework.util;version=[3.2,4), -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-6720) SoapJaxbDataFormat not handling correctly SOAP action with request wrapper element
[
https://issues.apache.org/jira/browse/CAMEL-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314014#comment-14314014
]
Paul G commented on CAMEL-6720:
---
This bug is still happening to me in Camel 2.14.1. Is there or will there be
any fix?
SoapJaxbDataFormat not handling correctly SOAP action with request wrapper
element
--
Key: CAMEL-6720
URL: https://issues.apache.org/jira/browse/CAMEL-6720
Project: Camel
Issue Type: Bug
Components: camel-soap
Affects Versions: 2.12.0
Reporter: Ondrej Fischer
Priority: Minor
Fix For: Future
Attachments: ServiceInterfaceStrategy.java
If an interface to be used as SOAP service interface is configured to have
parameters wrapped in a request wrapper element (eg. using @RequestWrapper),
then an attempt to invoke a its method will throw NPE:
{code}
java.lang.NullPointerException
at
org.apache.camel.dataformat.soap.name.ServiceInterfaceStrategy.findQNameForSoapActionOrType(ServiceInterfaceStrategy.java:207)
at
org.apache.camel.dataformat.soap.SoapJaxbDataFormat.createContentFromObject(SoapJaxbDataFormat.java:208)
at
org.apache.camel.dataformat.soap.Soap11DataFormatAdapter.doMarshal(Soap11DataFormatAdapter.java:77)
at
org.apache.camel.dataformat.soap.SoapJaxbDataFormat.marshal(SoapJaxbDataFormat.java:141)
at
org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:59)
{code}
The reason for this is sequence of following:
# The ServiceInterfaceStrategy is creating a mapping of methods to MethodInfo.
# In case of RequestWrapper, the wrapper class is used as a single input
TypeInfo, and no TypeInfo is being held for the real parameters.
# At method invocation, it tries to lookup the TypeInfo in the MethodInfo,
but for the real parameter class, and it only contains mapping for the
request wrapper. So it fails with NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8331) OSGi bundle upgrades
Claus Ibsen created CAMEL-8331: -- Summary: OSGi bundle upgrades Key: CAMEL-8331 URL: https://issues.apache.org/jira/browse/CAMEL-8331 Project: Camel Issue Type: Task Components: karaf, osgi Reporter: Claus Ibsen Fix For: 2.15.0 There is new osgi bundles. We should upgrade if possible. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311208version=12329297 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314184#comment-14314184
]
Charles Moulliard commented on CAMEL-8326:
--
I can't yet explain what is the issue but if we first, install the project
before to launch camel:run, then it will work
1) Does not work
mvn clean compile camel:run
2) Work
mvn clean package camel:run
I suspect that the reason is that the MANIFEST.MF created by the felix maven
bundle was not generated during compile phase !
{code}
dabouhost:~/Temp/test$ mvn install
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building A Camel Blueprint Route 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ test ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ test ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
test ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ test
---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.13-SONATYPE:test (default-test) @ test ---
[INFO] Surefire report directory:
/Users/chmoulli/Temp/test/target/surefire-reports
---
T E S T S
---
Running org.apache.camel.RouteTest
[ main] CamelBlueprintHelper INFO Using
Blueprint XML file:
/Users/chmoulli/Temp/test/target/classes/OSGI-INF/blueprint/blueprint.xml
[ Thread-0] RawBuilder INFO Copy
thread finished.
[ main] Activator INFO Camel
activator starting
[ main] Activator INFO Camel
activator started
[ main] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[ main] RouteTest INFO
[ main] RouteTest INFO Testing:
testRoute(org.apache.camel.RouteTest)
[ main] RouteTest INFO
[ Blueprint Extender: 3] BlueprintContainerImpl INFO Bundle
RouteTest is waiting for namespace handlers
[http://camel.apache.org/schema/blueprint]
[ main] RouteTest INFO Skipping
starting CamelContext as system property skipStartingCamelContext is set to be
true.
[ main] BlueprintCamelContext INFO Apache
Camel 2.14.1 (CamelContext: blueprintContext) is starting
[ main] DefaultManagementStrategy INFO JMX is
disabled
[ main] BlueprintCamelContext INFO
AllowUseOriginalMessage is enabled. If access to the original message is not
needed, then its recommended to turn this option off as it may improve
performance.
[ main] BlueprintCamelContext INFO
StreamCaching is not in use. If using streams then its recommended to enable
stream caching. See more details at http://camel.apache.org/stream-caching.html
[ main] BlueprintCamelContext INFO Route:
timerToLog started and consuming from: Endpoint[timer://foo?period=5000]
[ main] BlueprintCamelContext INFO Total 1
routes, of which 1 is started.
[ main] BlueprintCamelContext INFO Apache
Camel 2.14.1 (CamelContext: blueprintContext) started in 0.075 seconds
[ main] MockEndpoint INFO
Asserting: Endpoint[mock://result] is satisfied
[ntext) thread #0 - timer://foo] timerToLog INFO The
message contains Hi from Camel at 2015-02-10 14:37:32
[ main] RouteTest INFO
[ main] RouteTest INFO Testing
done: testRoute(org.apache.camel.RouteTest)
[ main] RouteTest INFO Took:
1.090 seconds (1090 millis)
[ main]
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314190#comment-14314190
]
Claus Ibsen commented on CAMEL-8326:
Oh yeah I have a habbit of running mvn clean install a lot ;)
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference:
[jira] [Resolved] (CAMEL-8330) camel-jms - Use 1000 as default receiveTimeout
[ https://issues.apache.org/jira/browse/CAMEL-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8330. Resolution: Fixed camel-jms - Use 1000 as default receiveTimeout -- Key: CAMEL-8330 URL: https://issues.apache.org/jira/browse/CAMEL-8330 Project: Camel Issue Type: Improvement Components: camel-jms Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.15.0 The receiveTimeout documentation is a bit confusing as it says None. But we use the spring-jms default value of 1000. We should set it to explicit 1000 like the others. And we should not set receiveTimeout in the JmsTemplate that we are using for sending messages, as we do not us its receive method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314191#comment-14314191
]
Charles Moulliard commented on CAMEL-8326:
--
That works without issue if add an execution tag to the
maven-bundle-plugin. I will update the archetype into the project to avoid
such stupid behavior and problem.
{code}
executions
execution
idbundle-manifest/id
phaseprocess-classes/phase
goals
goalmanifest/goal
/goals
/execution
/executions
{code}
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()]
[jira] [Commented] (CAMEL-8332) Add component implementation to camel-dozer module
[
https://issues.apache.org/jira/browse/CAMEL-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314349#comment-14314349
]
ASF GitHub Bot commented on CAMEL-8332:
---
GitHub user kcbabo opened a pull request:
https://github.com/apache/camel/pull/389
CAMEL-8332: Add component implementation to camel-dozer module
Proposed implementation of CAMEL-8332.
https://issues.apache.org/jira/browse/CAMEL-8332
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kcbabo/camel CAMEL-8332
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/389.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #389
commit 655f845a6a70f7c22ec86a95d265dd64b1220300
Author: Keith Babo kb...@redhat.com
Date: 2015-02-04T15:31:14Z
CAMEL-8332: Add component implementation to camel-dozer module
Add component implementation to camel-dozer module
--
Key: CAMEL-8332
URL: https://issues.apache.org/jira/browse/CAMEL-8332
Project: Camel
Issue Type: New Feature
Components: camel-dozer
Reporter: Keith Babo
The camel-dozer component does not actually provide a Camel component
implementation today. Rather, it provides a converter loader which can be
used in combination with a set of Dozer mapping files to register a global
set of converters within a CamelContext. This issue proposes the addition of
a full-blown component implementation within camel-dozer. Advantages of this
approach include:
* The ability to manage Dozer mapping configuration on a per-endpoint basis
vs. global configuration via the converter registry.
* Dozer handles direct field assignment quite well, but does not provide
other common mapping functions OOTB. Camel can enrich Dozer via standard
Dozer extensions, e.g.
** Mapping constant values to target fields
** Support for lookup tables, using the source value as the key
** Convenience transformations for mappings (e.g. trim spaces,
convertToLowerCase, regular expression evaluation)
** Allow Camel message/exchange headers to be mapped to target fields
* The ability to surround dozer mappings with data formats to support a
single, any-to-any transformation endpoint
Here's an example of what the endpoint configuration would look like.
{noformat}
dozer:mytransform?mappingFile=dozerBeanMapping.xmlmarshalId=jsonunmarshalId=jaxbtargetModel=example.MyObject
{noformat}
An initial implementation of this component is available as a PR against the
Camel GitHub repository. Unit tests in the PR provide examples of various
transformation use cases. Many, but not all, of the features listed above
are implemented already. I can file follow-up JIRAs for additional features
I have in mind. I will also post a link to the PR and the topic branch in
the issue comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
[
https://issues.apache.org/jira/browse/CAMEL-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315712#comment-14315712
]
Nazarii Kukhar edited comment on CAMEL-8334 at 2/11/15 7:24 AM:
I'll work on it next week provided nobody fix it till then.
was (Author: nkukhar):
I'll work on it next week provided nobody fixes it till then.
EIP documentation mave plugin should aslo inject documentation to
abstract/base types
-
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Reporter: Nazarii Kukhar
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_
injects ducumentation to attributest of top level elements. It would be nice
if it could also inject documentation to attributes of base/abstract
elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
[
https://issues.apache.org/jira/browse/CAMEL-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315712#comment-14315712
]
Nazarii Kukhar commented on CAMEL-8334:
---
I'll work on it next week provided nobody fixes it till then.
EIP documentation mave plugin should aslo inject documentation to
abstract/base types
-
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Reporter: Nazarii Kukhar
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_
injects ducumentation to attributest of top level elements. It would be nice
if it could also inject documentation to attributes of base/abstract
elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315663#comment-14315663
]
ASF GitHub Bot commented on CAMEL-8197:
---
Github user nkukhar closed the pull request at:
https://github.com/apache/camel/pull/387
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315716#comment-14315716
]
Nazarii Kukhar commented on CAMEL-8197:
---
I've logged followup ticket https://issues.apache.org/jira/browse/CAMEL-8334.
Also I just realized that I used different tab size, sorry for that, I will
adjust my settings next time.
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8332) Add component implementation to camel-dozer module
[
https://issues.apache.org/jira/browse/CAMEL-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8332:
---
Fix Version/s: 2.15.0
Add component implementation to camel-dozer module
--
Key: CAMEL-8332
URL: https://issues.apache.org/jira/browse/CAMEL-8332
Project: Camel
Issue Type: New Feature
Components: camel-dozer
Reporter: Keith Babo
Fix For: 2.15.0
The camel-dozer component does not actually provide a Camel component
implementation today. Rather, it provides a converter loader which can be
used in combination with a set of Dozer mapping files to register a global
set of converters within a CamelContext. This issue proposes the addition of
a full-blown component implementation within camel-dozer. Advantages of this
approach include:
* The ability to manage Dozer mapping configuration on a per-endpoint basis
vs. global configuration via the converter registry.
* Dozer handles direct field assignment quite well, but does not provide
other common mapping functions OOTB. Camel can enrich Dozer via standard
Dozer extensions, e.g.
** Mapping constant values to target fields
** Support for lookup tables, using the source value as the key
** Convenience transformations for mappings (e.g. trim spaces,
convertToLowerCase, regular expression evaluation)
** Allow Camel message/exchange headers to be mapped to target fields
* The ability to surround dozer mappings with data formats to support a
single, any-to-any transformation endpoint
Here's an example of what the endpoint configuration would look like.
{noformat}
dozer:mytransform?mappingFile=dozerBeanMapping.xmlmarshalId=jsonunmarshalId=jaxbtargetModel=example.MyObject
{noformat}
An initial implementation of this component is available as a PR against the
Camel GitHub repository. Unit tests in the PR provide examples of various
transformation use cases. Many, but not all, of the features listed above
are implemented already. I can file follow-up JIRAs for additional features
I have in mind. I will also post a link to the PR and the topic branch in
the issue comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8332) Add component implementation to camel-dozer module
[
https://issues.apache.org/jira/browse/CAMEL-8332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-8332:
--
Assignee: Claus Ibsen
Add component implementation to camel-dozer module
--
Key: CAMEL-8332
URL: https://issues.apache.org/jira/browse/CAMEL-8332
Project: Camel
Issue Type: New Feature
Components: camel-dozer
Reporter: Keith Babo
Assignee: Claus Ibsen
Fix For: 2.15.0
The camel-dozer component does not actually provide a Camel component
implementation today. Rather, it provides a converter loader which can be
used in combination with a set of Dozer mapping files to register a global
set of converters within a CamelContext. This issue proposes the addition of
a full-blown component implementation within camel-dozer. Advantages of this
approach include:
* The ability to manage Dozer mapping configuration on a per-endpoint basis
vs. global configuration via the converter registry.
* Dozer handles direct field assignment quite well, but does not provide
other common mapping functions OOTB. Camel can enrich Dozer via standard
Dozer extensions, e.g.
** Mapping constant values to target fields
** Support for lookup tables, using the source value as the key
** Convenience transformations for mappings (e.g. trim spaces,
convertToLowerCase, regular expression evaluation)
** Allow Camel message/exchange headers to be mapped to target fields
* The ability to surround dozer mappings with data formats to support a
single, any-to-any transformation endpoint
Here's an example of what the endpoint configuration would look like.
{noformat}
dozer:mytransform?mappingFile=dozerBeanMapping.xmlmarshalId=jsonunmarshalId=jaxbtargetModel=example.MyObject
{noformat}
An initial implementation of this component is available as a PR against the
Camel GitHub repository. Unit tests in the PR provide examples of various
transformation use cases. Many, but not all, of the features listed above
are implemented already. I can file follow-up JIRAs for additional features
I have in mind. I will also post a link to the PR and the topic branch in
the issue comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8333) Upgrade async-http-client to 1.9.0
Freeman Fang created CAMEL-8333: --- Summary: Upgrade async-http-client to 1.9.0 Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-8333 started by Freeman Fang. --- Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-8333: --- Assignee: Freeman Fang Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reopened CAMEL-8333: - Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315709#comment-14315709 ] Claus Ibsen commented on CAMEL-8333: Freeman do you mind taking a look as camel-ahc-ws component can no longer compile Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
Nazarii Kukhar created CAMEL-8334:
-
Summary: EIP documentation mave plugin should aslo inject
documentation to abstract/base types
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Reporter: Nazarii Kukhar
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_ injects
ducumentation to attributest of top level elements. It would be nice if it
could also inject documentation to attributes of base/abstract elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315713#comment-14315713 ] Stephan Siano commented on CAMEL-8333: -- Just one question: Why are you using ahc 1.9.0, not 1.9.8? Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
[
https://issues.apache.org/jira/browse/CAMEL-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315712#comment-14315712
]
Nazarii Kukhar edited comment on CAMEL-8334 at 2/11/15 7:24 AM:
I'll work on it next week if nobody fix it till then.
was (Author: nkukhar):
I'll work on it next week provided nobody fix it till then.
EIP documentation mave plugin should aslo inject documentation to
abstract/base types
-
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Reporter: Nazarii Kukhar
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_
injects ducumentation to attributest of top level elements. It would be nice
if it could also inject documentation to attributes of base/abstract
elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315714#comment-14315714 ] Freeman Fang commented on CAMEL-8333: - Hi Claus, Sure, I'm on it. The commit it is on the way. And sorry for it. Freeman Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8333) Upgrade async-http-client to 1.9.8
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315723#comment-14315723 ] Freeman Fang commented on CAMEL-8333: - Hi Stephan, Good question, as we upgrade, use the latest version should be good. Freeman Upgrade async-http-client to 1.9.8 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8197.
Resolution: Fixed
Thanks
Great you want to help with the last pieces.
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8333) Upgrade async-http-client to 1.9.0
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-8333. - Resolution: Fixed Fix Version/s: 2.15.0 2.14.2 commit fix http://git-wip-us.apache.org/repos/asf/camel/commit/5b4ac788 for master http://git-wip-us.apache.org/repos/asf/camel/commit/4a2b4963 for camel-2.14.x branch Upgrade async-http-client to 1.9.0 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315716#comment-14315716
]
Nazarii Kukhar edited comment on CAMEL-8197 at 2/11/15 7:36 AM:
I've logged followup ticket CAMEL-8334.
Also I just realized that I used different tab size, sorry for that, I will
adjust my settings next time.
was (Author: nkukhar):
I've logged followup ticket https://issues.apache.org/jira/browse/CAMEL-8334.
Also I just realized that I used different tab size, sorry for that, I will
adjust my settings next time.
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8333) Upgrade async-http-client to 1.9.8
[ https://issues.apache.org/jira/browse/CAMEL-8333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-8333: Summary: Upgrade async-http-client to 1.9.8 (was: Upgrade async-http-client to 1.9.0) Upgrade async-http-client to 1.9.8 --- Key: CAMEL-8333 URL: https://issues.apache.org/jira/browse/CAMEL-8333 Project: Camel Issue Type: Task Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.14.2, 2.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7999) Camel Toolbox - Easy information about all Camel components and the release for tooling
[ https://issues.apache.org/jira/browse/CAMEL-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14315734#comment-14315734 ] Claus Ibsen commented on CAMEL-7999: We have ticket CAMEL-8334 where the last pieces for the EIP in the XSD is missing. Camel Toolbox - Easy information about all Camel components and the release for tooling --- Key: CAMEL-7999 URL: https://issues.apache.org/jira/browse/CAMEL-7999 Project: Camel Issue Type: New Feature Components: camel-core, jmx, tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.0 A Camel release contains many components, and we have the ability to let components document which options they offer. Though there is currently a few shortcomings that can be improved - the component json schema is currently runtime generated, which requires to load the component and create an instance of it. Instead we should build-time generate it, which we do today with the camel apt compiler plugin. *DONE* - we should include documentation about the option from the javadoc, that allows end users to fully document a component using plain java getter/settr with javadocs, and add those @UriParam annotations for the apt compiler to detect and leverage *DONE* - add a module that embeds all these json schema files in a single module, and also other information, such as the xml schemas, and what else can be handy. Then there is a single module as a one stop shop for tooling and whatnot to gather information about a Camel release. There is a new camel-catalog module that contains this now. *DONE* - allow at runtime to explain an endpoint uri what the options in use are, eg as we got the json schema, we can add mbeans that can explain those options, than we can use in tooling, JMX, karaf commands etc. And also IDE editors etc *DONE* - add JMX/Java API to explain a EIP and also get a tabular data with a list of all EIPs and their data. *DONE* - enrich the dsl xml to inject javadoc for the eips into the xml schema, so we have documented in the xsd directly that any tooling can use. We have a old ticket about this. But the apt compiler plugin can detect the @JAXB annotations in the model and extract the javadoc, and generate a json schema with, and then we can load those and enrich into the generated xsd, or enrich into the jaxb model generator, or something. - migrate more Camel components to include javadoc as documentation for their options *DONE* for all camel-core. Other components will be migrated over time. - figure out how to specify a default value in the json schema. Unfortunately the apt plugin cannot grab that from the source code. So the only solution I can think of now is to add an attribute to the @UriParam where you can specify that, eg this is also what I have seen others do. There is now a defaultValue attribute on UriParam to be used. *DONE* - add component summary to component json file so we have a description of what the component does *DONE* - add attribute to @UriEndpoint to link it to the component class, so we can include the class name of the component in the json schema, which allows Camel to link from component class - schema. eg the point is that if people define a component as activemq we do not know its the jms schema that has its documentation. Though we can infer this by the component class name. And alternative is for a component to have an api to return its original schema name etc. So activemq can say jms etc. We can resolve this by iterating the component data, and find the FQN of the components. *DONE* - add @UriComponent annotation to component class which allows end users to provide meta-data about the component. Currently we grab a summary of what the component does from the maven pom.xml. Though this annotation prepares us for being able to scan the component class as well for which option it provides, so we can have out of the box documentation for that also. We detect getter/setter pairs as component options, and the apt plugin generates those in the schema. Use @Metadata to configure the options. *DONE* - add JMX/Java API to explain a component and also get a tabular data with a list of all components and that data. *DONE* - improve karaf commands to use the component information to show that also *DONE* - add name of karaf feature of the component, eg its 99% came-xxx, but there may be some exceptions. We can likely add a property to the maven plugin that generates component.properties to include the karaf feature name as the artifactId by default. But allow to set a property in the pom.xml in case there is another name, or no karaf feature - add
[jira] [Updated] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
[
https://issues.apache.org/jira/browse/CAMEL-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8334:
---
Fix Version/s: 2.15.0
EIP documentation mave plugin should aslo inject documentation to
abstract/base types
-
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Components: build system, camel-blueprint, camel-spring, tooling
Reporter: Nazarii Kukhar
Fix For: 2.15.0
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_
injects ducumentation to attributest of top level elements. It would be nice
if it could also inject documentation to attributes of base/abstract
elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8334) EIP documentation mave plugin should aslo inject documentation to abstract/base types
[
https://issues.apache.org/jira/browse/CAMEL-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8334:
---
Component/s: tooling
camel-spring
camel-blueprint
build system
EIP documentation mave plugin should aslo inject documentation to
abstract/base types
-
Key: CAMEL-8334
URL: https://issues.apache.org/jira/browse/CAMEL-8334
Project: Camel
Issue Type: Improvement
Components: build system, camel-blueprint, camel-spring, tooling
Reporter: Nazarii Kukhar
Fix For: 2.15.0
Currently maven plugin _camel-eip-documentation-enricher-maven-plugin_
injects ducumentation to attributest of top level elements. It would be nice
if it could also inject documentation to attributes of base/abstract
elements.
Example:
It's a snippet on top level _logDefinition_ type with injected documentation.
{code:xml}
xs:complexType name=logDefinition
xs:complexContent
xs:extension base=tns:noOutputDefinition
xs:sequence/
xs:attribute name=message type=xs:string use=required
xs:annotation
xs:documentation xml:lang=enSets the log message (uses simple
language)/xs:documentation
/xs:annotation
/xs:attribute
...
/xs:complexType
{code}
But for it's abstract base type documentation does not injected:
{code:xml}
xs:complexType abstract=true name=processorDefinition
xs:complexContent
xs:extension base=tns:optionalIdentifiedDefinition
xs:sequence/
!-- Documentation should be injected for this attribute. --
xs:attribute name=inheritErrorHandler type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8330) camel-jms - Use 1000 as default receiveTimeout
Claus Ibsen created CAMEL-8330: -- Summary: camel-jms - Use 1000 as default receiveTimeout Key: CAMEL-8330 URL: https://issues.apache.org/jira/browse/CAMEL-8330 Project: Camel Issue Type: Improvement Components: camel-jms Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.15.0 The receiveTimeout documentation is a bit confusing as it says None. But we use the spring-jms default value of 1000. We should set it to explicit 1000 like the others. And we should not set receiveTimeout in the JmsTemplate that we are using for sending messages, as we do not us its receive method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314158#comment-14314158
]
Claus Ibsen commented on CAMEL-8326:
Works fine for me with almost the same
mvndavsclaus:~/$ mvn -version
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T22:58:10+02:00)
Maven home: /opt/apache-maven-3.2.3
Java version: 1.7.0_45, vendor: Oracle Corporation
I think you need to check the logs, or deploy the bundle to Karaf 2.4.x and see
if karaf reports some error.
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()]
[jira] [Comment Edited] (CAMEL-8197) Create Maven plugin to inject EIP documentation into the spring and blueprint XML DSL
[
https://issues.apache.org/jira/browse/CAMEL-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14313935#comment-14313935
]
Claus Ibsen edited comment on CAMEL-8197 at 2/10/15 12:34 PM:
--
There are two things left to do
- include doc for abstract/base types (such as SendDefinition) which are used
by to
- the schema file in the JAR is the old schema, we should include the schema
with the documentation *DONE*
was (Author: davsclaus):
There are two things left to do
- include doc for abstract/base types (such as SendDefinition) which are used
by to
- the schema file in the JAR is the old schema, we should include the schema
with the documentation
Create Maven plugin to inject EIP documentation into the spring and blueprint
XML DSL
-
Key: CAMEL-8197
URL: https://issues.apache.org/jira/browse/CAMEL-8197
Project: Camel
Issue Type: Sub-task
Components: eip, tooling
Reporter: Claus Ibsen
Assignee: Willem Jiang
Fix For: 2.15.0
So we can include documentation out of the box in the XSD schema files, which
allows end users to better work with Camel, as their IDE editors can show the
documentation in the IDE.
To do this we need to
1)
Create a new Maven plugin at
https://github.com/apache/camel/tree/master/tooling/maven
which can be inspired by
https://github.com/apache/camel/tree/master/tooling/maven/camel-package-maven-plugin
2)
Run this plugin in camel-spring and camel-blueprint, so it can read the
camel-spring.xsd, camel-blueprint.xsd file, and inject documentation.
3)
Parse the XSD maybe using SAX, and inject the documentation.
For each xs:element in the top of the schema file
http://camel.apache.org/schema/spring/camel-spring.xsd
Then use the name, eg (name=split)
{code}
xs:element name=split type=tns:splitDefinition/
{code}
To find the split.json file in camel-core. Then the json file has the
documentation for that type (including inherited types).
So for the split definition
{code}
xs:complexType name=splitDefinition
xs:complexContent
xs:extension base=tns:expressionNode
xs:sequence/
xs:attribute name=parallelProcessing type=xs:boolean/
xs:attribute name=strategyRef type=xs:string/
xs:attribute name=strategyMethodName type=xs:string/
xs:attribute name=strategyMethodAllowNull type=xs:boolean/
xs:attribute name=executorServiceRef type=xs:string/
xs:attribute name=streaming type=xs:boolean/
xs:attribute name=stopOnException type=xs:boolean/
xs:attribute name=timeout type=xs:long/
xs:attribute name=onPrepareRef type=xs:string/
xs:attribute name=shareUnitOfWork type=xs:boolean/
xs:anyAttribute namespace=##other processContents=skip/
/xs:extension
/xs:complexContent
/xs:complexType
{code}
We can find the description of these attributes, and elements from the json
file.
For example for the streaming attribute we have
{code}
streaming: { kind: attribute: required: false, type: boolean,
javaType: java.lang.Boolean, description: The splitter should use
streaming -- exchanges are being sent as the data for them becomes available.
This improves throughput and memory usage but it has a drawback: - the sent
exchanges will no longer contain the link org.apache.camel.ExchangeSPLIT_SIZE
header property
{code}
Then add the needed xs:annotation to document it.
http://www.w3schools.com/schema/el_annotation.asp
Which should be
{code}
xs:annotation
xs:documentation xml:lang=en
The splitter should use streaming -- exchanges are being sent as the data for
them becomes available. This improves throughput and memory usage but it has
a drawback: - the sent exchanges will no longer contain the link
org.apache.camel.ExchangeSPLIT_SIZE header property
/xs:documentation
/xs:annotation
{code}
Notice that the xsd will become bigger due the verbosity of how to annotate
xsd fields.
Mind that sometimes there is not yet documentation, so check for not empty
value.
To parse the json file, then use this class from camel-core
{code}
ListMapString, String rows =
JsonSchemaHelper.parseJsonSchema(properties, json, true);
{code}
Then you have a map with key/value for all those values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8023) Add javadoc documentation to camel-core endpoints so we have documentation out of the box
[ https://issues.apache.org/jira/browse/CAMEL-8023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314141#comment-14314141 ] ASF GitHub Bot commented on CAMEL-8023: --- Github user kevinearls closed the pull request at: https://github.com/apache/camel/pull/386 Add javadoc documentation to camel-core endpoints so we have documentation out of the box - Key: CAMEL-8023 URL: https://issues.apache.org/jira/browse/CAMEL-8023 Project: Camel Issue Type: Sub-task Components: camel-core Reporter: Claus Ibsen Assignee: Willem Jiang Fix For: 2.15.0 See parent ticket. For each of the components in camel-core, we need to document each @UriParam option. This is done by adding javadoc to the setter method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard reassigned CAMEL-8326:
Assignee: Charles Moulliard
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ConfigurationAdmin], bundle:
[jira] [Closed] (CAMEL-8326) Project created from camel-blueprint-archetype does not work
[
https://issues.apache.org/jira/browse/CAMEL-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Moulliard closed CAMEL-8326.
Resolution: Fixed
code submitted : ed73023..c7cb9d3 master - master
Project created from camel-blueprint-archetype does not work
Key: CAMEL-8326
URL: https://issues.apache.org/jira/browse/CAMEL-8326
Project: Camel
Issue Type: Bug
Components: osgi, tooling
Affects Versions: 2.13.3, 2.14.1
Reporter: Charles Moulliard
Assignee: Charles Moulliard
Attachments: test.zip
When we launch the camel:run maven goal created from a project created using
the archetype :
org.apache.camel.archetypes:camel-archetype-blueprint (Creates a new Camel
project with OSGi blueprint support. Ready to be deployed in OSGi.)
then it fails
{code}
[mel.test.blueprint.Main.main()] MainSupportINFO Apache
Camel 2.14.1 starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator starting
[mel.test.blueprint.Main.main()] Activator INFO Camel
activator started
[mel.test.blueprint.Main.main()] BlueprintExtender INFO No
quiesce support is available, so blueprint components will not participate in
quiesce operations
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN Test
bundle headers: Bundle-ManifestVersion=2, Bundle-Name=System Bundle,
Bundle-SymbolicName=de.kalpatec.pojosr.framework, Bundle-Vendor=kalpatec,
Bundle-Version=0.2.1
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.packageadmin.PackageAdmin], bundle:
de.kalpatec.pojosr.framework [0], symbolicName: de.kalpatec.pojosr.framework
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.LanguageResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.cm.ManagedServiceFactory], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.felix.cm.PersistenceManager], bundle:
org.apache.felix.configadmin [25], symbolicName: org.apache.felix.configadmin
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.DataFormatResolver], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.blueprint.container.BlueprintContainer],
bundle: org.apache.aries.blueprint [13], symbolicName:
org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.camel.camel-blueprint [4], symbolicName:
org.apache.camel.camel-blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.aries.blueprint.NamespaceHandler], bundle:
org.apache.aries.blueprint [13], symbolicName: org.apache.aries.blueprint
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.apache.camel.spi.TypeConverterLoader], bundle:
org.apache.camel.camel-core [2], symbolicName: org.apache.camel.camel-core
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference: [org.osgi.service.url.URLStreamHandlerService], bundle:
org.apache.felix.fileinstall [26], symbolicName: org.apache.felix.fileinstall
[mel.test.blueprint.Main.main()] CamelBlueprintHelper WARN
ServiceReference:
