[jira] [Updated] (CAMEL-8555) on using Guice modules - give user control on when context starts
[ https://issues.apache.org/jira/browse/CAMEL-8555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] moritz löser updated CAMEL-8555: Summary: on using Guice modules - give user control on when context starts (was: Give user control on when context starts) on using Guice modules - give user control on when context starts - Key: CAMEL-8555 URL: https://issues.apache.org/jira/browse/CAMEL-8555 Project: Camel Issue Type: Improvement Components: camel-guice Reporter: moritz löser In my application i need to do some stuff before i want camel to start. in a normal camel app you would just call main.run(). The problem on using the camel modules is that they all start the context on @PostConstruct so as soon as the injector is constructed the context starts. I would suggest a CamelModule or an option (constructor parameter) to disable this auto start behavior. So with disabled autostart one must call org.apache.camel.guice.Main.run(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8547) Usage of camel-xmlbeans depends on TCCL
[ https://issues.apache.org/jira/browse/CAMEL-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381580#comment-14381580 ] ASF GitHub Bot commented on CAMEL-8547: --- Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/445 Usage of camel-xmlbeans depends on TCCL --- Key: CAMEL-8547 URL: https://issues.apache.org/jira/browse/CAMEL-8547 Project: Camel Issue Type: Bug Affects Versions: 2.15.0 Reporter: James Netherton Assignee: Willem Jiang xmlbeans marshalling and unmarshalling does not respect the ApplicationContextClassLoader CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/457 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8555) Give user control on when context starts
moritz löser created CAMEL-8555: --- Summary: Give user control on when context starts Key: CAMEL-8555 URL: https://issues.apache.org/jira/browse/CAMEL-8555 Project: Camel Issue Type: Improvement Components: camel-guice Reporter: moritz löser In my application i need to do some stuff before i want camel to start. in a normal camel app you would just call main.run(). The problem on using the camel modules is that they all start the context on @PostConstruct so as soon as the injector is constructed the context starts. I would suggest a CamelModule or an option (constructor parameter) to disable this auto start behavior. So with disabled autostart one must call org.apache.camel.guice.Main.run(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8537) CamelHazelcast component should create its own HZ instance only if it's not provided
[
https://issues.apache.org/jira/browse/CAMEL-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381689#comment-14381689
]
Claus Ibsen commented on CAMEL-8537:
Yeah sure that is valid forever. So you are very welcome to edit any time you
want
CamelHazelcast component should create its own HZ instance only if it's not
provided
Key: CAMEL-8537
URL: https://issues.apache.org/jira/browse/CAMEL-8537
Project: Camel
Issue Type: Improvement
Components: camel-hazelcast
Affects Versions: 2.15.0
Reporter: ayache khettar
Labels: patch
Fix For: 2.16.0
Hi
Currently Hazelcast component creates its own HZ instance regardless if a
reference to a HZ instance is provided or not. So in the case of a reference
of HZ instance is provided, the one created by the component does not get
shutdown - see below code snippet, doesn't get shutdown. So one end up with
multipole instances.
I believe the component should not create its own instance at the doStart()
method. It should first check if a reference to HZ instance is provided, if
yes then use it and if not create its own.
I have made the changes to reflect the correct behaviour described above. The
changes will make sure only one instance of HZ is created. Also, added the
ability to reference HZ instance by its name.
{panel:title=What
remains?|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
* Update the wiki to show how to reference HZ by its name
* Update the wiki to show the newly introduced parameter
(hazelcastInstanceName)
* Update the wiki to ideally show an example of how to publish HZ instance as
an OSGI service for reuse by multiple bundles.
{panel}
{panel:title=Changes
made|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
* No longer the component creates its own HZ instance in doStart() method.
* When the component is initialised, only one instance is either been created
or use the referenced on in the endpoint.
* Ability to reference HZ instance by its name. This will serve the use case
whereby the hazelcast cluster is running remotely or not part of the camel
context.
{panel}
{code:title=HazelcastComponent.java|borderStyle=solid}
@Override
public void doStart() throws Exception {
super.doStart();
if (hazelcastInstance == null) {
createOwnInstance = true;
hazelcastInstance = createOwnInstance();
}
}
{code}
I have created a pull request for this, details can be seen here:
https://github.com/apache/camel/pull/443
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-8547) Usage of camel-xmlbeans depends on TCCL
[ https://issues.apache.org/jira/browse/CAMEL-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381767#comment-14381767 ] Willem Jiang edited comment on CAMEL-8547 at 3/26/15 11:58 AM: --- Applied the patch into camel-2.15.x and camel-2.14.x branch with thanks to James, I also rewrite the patch in camel master branch. was (Author: njiang): Applied the patch into camel-2.15.x and camel-2.14.x branch, I already rewrite the patch in camel master branch. Usage of camel-xmlbeans depends on TCCL --- Key: CAMEL-8547 URL: https://issues.apache.org/jira/browse/CAMEL-8547 Project: Camel Issue Type: Bug Affects Versions: 2.15.0 Reporter: James Netherton Assignee: Willem Jiang Fix For: 2.14.3, 2.15.1, 2.16.0 xmlbeans marshalling and unmarshalling does not respect the ApplicationContextClassLoader CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/457 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8547) Usage of camel-xmlbeans depends on TCCL
[ https://issues.apache.org/jira/browse/CAMEL-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-8547. - Resolution: Fixed Fix Version/s: 2.16.0 2.15.1 2.14.3 Applied the patch into camel-2.15.x and camel-2.14.x branch, I already rewrite the patch in camel master branch. Usage of camel-xmlbeans depends on TCCL --- Key: CAMEL-8547 URL: https://issues.apache.org/jira/browse/CAMEL-8547 Project: Camel Issue Type: Bug Affects Versions: 2.15.0 Reporter: James Netherton Assignee: Willem Jiang Fix For: 2.14.3, 2.15.1, 2.16.0 xmlbeans marshalling and unmarshalling does not respect the ApplicationContextClassLoader CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/457 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8546) No LanguageResolver found for language=js
[
https://issues.apache.org/jira/browse/CAMEL-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-8546.
-
Resolution: Fixed
Fix Version/s: 2.15.1
2.14.3
Applied the patch into camel master, camel-2.15.x and camel-2.14.x branches
with thanks to Bart. I also polish the code to avoid the NPE.
No LanguageResolver found for language=js
-
Key: CAMEL-8546
URL: https://issues.apache.org/jira/browse/CAMEL-8546
Project: Camel
Issue Type: Bug
Components: camel-script
Affects Versions: 2.14.1
Reporter: Bart Horré
Assignee: Willem Jiang
Fix For: 2.14.3, 2.15.1, 2.16.0
{noformat}Unable to start blueprint container for bundle test.xml due to
unresolved dependencies
[((language=js)(objectClass=org.apache.camel.spi.LanguageResolver))]
java.util.concurrent.TimeoutException
at
org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:293)[10:org.apache.aries.blueprint:0.3.2]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_17]
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.7.0_17]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.7.0_17]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_17]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_17]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_17]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_17]
at java.lang.Thread.run(Thread.java:722)[:1.7.0_17] {noformat}
This happens when we try to use script with blueprint because blueprint tries
to resolve the LanguageResolver with filter language=js. However camel.osgi
registered a default LanguageResolver under resolver=default which causes
blueprint to wait for ever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8537) CamelHazelcast component should create its own HZ instance only if it's not provided
[
https://issues.apache.org/jira/browse/CAMEL-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381685#comment-14381685
]
ayache khettar commented on CAMEL-8537:
---
Hi Claus
I have signed the ICLA few months back when i introduced the Schematron
Component so it should still be valid right? I will update the wiki sometime
today.
Ayache
CamelHazelcast component should create its own HZ instance only if it's not
provided
Key: CAMEL-8537
URL: https://issues.apache.org/jira/browse/CAMEL-8537
Project: Camel
Issue Type: Improvement
Components: camel-hazelcast
Affects Versions: 2.15.0
Reporter: ayache khettar
Labels: patch
Fix For: 2.16.0
Hi
Currently Hazelcast component creates its own HZ instance regardless if a
reference to a HZ instance is provided or not. So in the case of a reference
of HZ instance is provided, the one created by the component does not get
shutdown - see below code snippet, doesn't get shutdown. So one end up with
multipole instances.
I believe the component should not create its own instance at the doStart()
method. It should first check if a reference to HZ instance is provided, if
yes then use it and if not create its own.
I have made the changes to reflect the correct behaviour described above. The
changes will make sure only one instance of HZ is created. Also, added the
ability to reference HZ instance by its name.
{panel:title=What
remains?|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
* Update the wiki to show how to reference HZ by its name
* Update the wiki to show the newly introduced parameter
(hazelcastInstanceName)
* Update the wiki to ideally show an example of how to publish HZ instance as
an OSGI service for reuse by multiple bundles.
{panel}
{panel:title=Changes
made|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#CE}
* No longer the component creates its own HZ instance in doStart() method.
* When the component is initialised, only one instance is either been created
or use the referenced on in the endpoint.
* Ability to reference HZ instance by its name. This will serve the use case
whereby the hazelcast cluster is running remotely or not part of the camel
context.
{panel}
{code:title=HazelcastComponent.java|borderStyle=solid}
@Override
public void doStart() throws Exception {
super.doStart();
if (hazelcastInstance == null) {
createOwnInstance = true;
hazelcastInstance = createOwnInstance();
}
}
{code}
I have created a pull request for this, details can be seen here:
https://github.com/apache/camel/pull/443
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-5884) camel-cxf - Allow to define which operationNames a given consumer services
[ https://issues.apache.org/jira/browse/CAMEL-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-5884: --- Assignee: Willem Jiang camel-cxf - Allow to define which operationNames a given consumer services -- Key: CAMEL-5884 URL: https://issues.apache.org/jira/browse/CAMEL-5884 Project: Camel Issue Type: New Feature Components: camel-cxf Reporter: Claus Ibsen Assignee: Willem Jiang Fix For: Future Currently when using a cxf consumer in a route, then all the operations is serviced by this route. This may confuse some people. As well some may want one route per operation. We should look into how we can support this. Today people would need to use the recipient list and direct endpoints to suport this. But many people dont know about this. See this example: http://camel.apache.org/cxf-tomcat-example.html I guess this is not so easy, as you would then have mutliple routes with the same CXF webservice. But we would like to have this level of indirection. And then I guess if a operation name is not bound to any route, then a soap fault should be thrown. Or we should allow to let Camel fail on startup saying that operation XXX is not bound to any consumer/route. Or something like that. Or allow people to turn this on|off. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
Thomas Diesler created CAMEL-8556:
-
Summary: AnnotationTypeConverterLoader treats package as class
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Reporter: Thomas Diesler
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-8556:
--
Fix Version/s: 2.15.1
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Fix For: 2.15.1
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-8556:
--
Component/s: camel-core
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Fix For: 2.15.1
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Diesler updated CAMEL-8556:
--
Affects Version/s: 2.15.0
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Fix For: 2.15.1
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8558) Camel Catalog - Add humanize component name
[ https://issues.apache.org/jira/browse/CAMEL-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8558: --- Fix Version/s: 2.15.1 Camel Catalog - Add humanize component name --- Key: CAMEL-8558 URL: https://issues.apache.org/jira/browse/CAMEL-8558 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.1, 2.16.0 Each component has a name such as ejb, ftp, jms, mqtt, file etc. But presenting these names to humans,we may want to let the component provide a humainzed text of its name, so we can do 100% correct names. - ejb = EJB - mqtt = MQTT - sap-netweaver = SAP NetWeaver and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8557) The entire LRU Cache is cleared on eviction of a single entry
Padmanaban created CAMEL-8557: - Summary: The entire LRU Cache is cleared on eviction of a single entry Key: CAMEL-8557 URL: https://issues.apache.org/jira/browse/CAMEL-8557 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.12.2 Environment: Camel 2.12.2, concurrentlinkedhashmap - 1.2 Reporter: Padmanaban Priority: Minor Use Case: Using Sftp End point to poll remote directory Set the following attributes in uri noop=true idempotent=true idempotentRepository=#idemRep where #idemRep is defined in context xml as below bean id=idemRep class=org.apache.camel.processor.idempotent.MemoryIdempotentRepository property name=cacheSize value=10 / /bean The number of files in the remote directory is more than 10. In the above scenario, while trying to add 11th entry in to map, the eldest entry is evicted as expected but soon after the eviction the LRUCache.onEviction clears cache, which i am wondering is not the expected behavior of LRU Cache. This happens because LRUCache.stopOnEviction is always set to true during the LRUCache instantiation which triggers ServiceHelper.stopService on eviction. I am trying to understand why we need to reset the cache on eviction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8557) The entire LRU Cache is cleared on eviction of a single entry
[ https://issues.apache.org/jira/browse/CAMEL-8557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Padmanaban updated CAMEL-8557: -- Description: Use Case: Using Sftp End point to poll remote directory Set the following attributes in uri noop=true idempotent=true idempotentRepository=#idemRep where #idemRep is defined in context xml as below bean id=idemRep class=org.apache.camel.processor.idempotent.MemoryIdempotentRepository property name=cacheSize value=10 / /bean The number of files in the remote directory is more than 10. In the above scenario, while trying to add 11th entry into the map, the eldest entry is evicted as expected but soon after the eviction the LRUCache.onEviction clears cache, which i am wondering is not the expected behavior of LRU Cache. This happens because LRUCache.stopOnEviction is always set to true during the LRUCache instantiation which triggers ServiceHelper.stopService on eviction. I am trying to understand why we need to reset the cache on eviction. was: Use Case: Using Sftp End point to poll remote directory Set the following attributes in uri noop=true idempotent=true idempotentRepository=#idemRep where #idemRep is defined in context xml as below bean id=idemRep class=org.apache.camel.processor.idempotent.MemoryIdempotentRepository property name=cacheSize value=10 / /bean The number of files in the remote directory is more than 10. In the above scenario, while trying to add 11th entry in to map, the eldest entry is evicted as expected but soon after the eviction the LRUCache.onEviction clears cache, which i am wondering is not the expected behavior of LRU Cache. This happens because LRUCache.stopOnEviction is always set to true during the LRUCache instantiation which triggers ServiceHelper.stopService on eviction. I am trying to understand why we need to reset the cache on eviction. The entire LRU Cache is cleared on eviction of a single entry - Key: CAMEL-8557 URL: https://issues.apache.org/jira/browse/CAMEL-8557 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.12.2 Environment: Camel 2.12.2, concurrentlinkedhashmap - 1.2 Reporter: Padmanaban Priority: Minor Use Case: Using Sftp End point to poll remote directory Set the following attributes in uri noop=true idempotent=true idempotentRepository=#idemRep where #idemRep is defined in context xml as below bean id=idemRep class=org.apache.camel.processor.idempotent.MemoryIdempotentRepository property name=cacheSize value=10 / /bean The number of files in the remote directory is more than 10. In the above scenario, while trying to add 11th entry into the map, the eldest entry is evicted as expected but soon after the eviction the LRUCache.onEviction clears cache, which i am wondering is not the expected behavior of LRU Cache. This happens because LRUCache.stopOnEviction is always set to true during the LRUCache instantiation which triggers ServiceHelper.stopService on eviction. I am trying to understand why we need to reset the cache on eviction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381886#comment-14381886
]
ASF GitHub Bot commented on CAMEL-8556:
---
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/446
[CAMEL-8556] AnnotationTypeConverterLoader treats package as class
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-8556
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/446.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 #446
commit f2f46faa82e3491ef86888ef29e2890132a6bb49
Author: Thomas Diesler thomas.dies...@jboss.com
Date: 2015-03-26T13:41:47Z
[CAMEL-8556] AnnotationTypeConverterLoader treats package as class
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Fix For: 2.15.1
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8558) Camel Catalog - Add humanize component name
Claus Ibsen created CAMEL-8558: -- Summary: Camel Catalog - Add humanize component name Key: CAMEL-8558 URL: https://issues.apache.org/jira/browse/CAMEL-8558 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Fix For: 2.16.0 Each component has a name such as ejb, ftp, jms, mqtt, file etc. But presenting these names to humans,we may want to let the component provide a humainzed text of its name, so we can do 100% correct names. - ejb = EJB - mqtt = MQTT - sap-netweaver = SAP NetWeaver and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8558) Camel Catalog - Add humanize component name
[
https://issues.apache.org/jira/browse/CAMEL-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8558.
Resolution: Fixed
A sample output from Karaf
{code}
karaf@root camel-catalog:component-list --verbose
Title Scheme Label
Maven Coordinate
- -- -
AHC ahchttp
org.apache.camel/camel-ahc/2.16-SNAPSHOT
AHC Websocket ahc-ws http,websocket
org.apache.camel/camel-ahc-ws/2.16-SNAPSHOT
AHC Secure Websocketahc-wsshttp,websocket
org.apache.camel/camel-ahc-ws/2.16-SNAPSHOT
AMQPamqp messaging
org.apache.camel/camel-amqp/2.16-SNAPSHOT
APNSapns eventbus,mobile
org.apache.camel/camel-apns/2.16-SNAPSHOT
Atmos atmos file,cloud
org.apache.camel/camel-atmos/2.16-SNAPSHOT
Atmosphere Websocketatmosphere-websocket http,websocket
org.apache.camel/camel-atmosphere-websocket/2.16-SNAPSHOT
Atomatom feeds
org.apache.camel/camel-atom/2.16-SNAPSHOT
Avroavro
messaging,transformationorg.apache.camel/camel-avro/2.16-SNAPSHOT
AWS CloudWatch aws-cw
cloud,monitoringorg.apache.camel/camel-aws/2.16-SNAPSHOT
AWS DynamoDBaws-ddb
cloud,database,nosqlorg.apache.camel/camel-aws/2.16-SNAPSHOT
AWS S3 Storage Service aws-s3 cloud,file
org.apache.camel/camel-aws/2.16-SNAPSHOT
AWS SimpleDBaws-sdb
cloud,database,nosqlorg.apache.camel/camel-aws/2.16-SNAPSHOT
AWS Simple Email Serviceaws-sescloud,mail
org.apache.camel/camel-aws/2.16-SNAPSHOT
AWS Simple Notification System aws-sns
cloud,mobile,messaging org.apache.camel/camel-aws/2.16-SNAPSHOT
AWS Simple Queue Serviceaws-sqscloud,messaging
org.apache.camel/camel-aws/2.16-SNAPSHOT
AWS Simple Workflow aws-swfcloud,workflow
org.apache.camel/camel-aws/2.16-SNAPSHOT
Beanbean core,java
org.apache.camel/camel-core/2.16-SNAPSHOT
Bean Validator bean-validator validation
org.apache.camel/camel-bean-validator/2.16-SNAPSHOT
{code}
.. and the variation with description
{code}
araf@root camel-catalog:component-list
Title Description
AHC Defines the Async HTTP Client Component
AHC Websocket Defines the WebSocket Client Component
AHC Secure WebsocketDefines the WebSocket Client Component
AMQPThis component supports the AMQP
protocol using the Client API of the Apache Qpid project.
APNSA Camel Apple Push Notification Server
Component
Atmos Camel Atmos support
Atmosphere WebsocketCamel Atmosphere WebSocket Servlet
AtomAn Atom Component.
AvroCamel Avro data format
AWS CloudWatch Defines the AWS CloudWatch Component
AWS DynamoDBDefines the AWS DynamoDB component
AWS S3 Storage Service Defines the AWS S3 Component
AWS SimpleDBDefines the AWS SDB component
AWS Simple Email ServiceDefines the AWS SES component
AWS Simple Notification System Defines the AWS SNS Component
AWS Simple Queue ServiceDefines the AWS Component
AWS Simple Workflow Defines the Amazon Simple Workflow
Component
BeanThe Bean Component is for invoking
Java beans from Camel.
Bean Validator Bean Validator Component for
validating Java beans against reference implementation of JSR 303 Validator
(Hibernate Vali
Beanstalk Beanstalk Camel component.
{code}
Camel Catalog - Add humanize
[jira] [Assigned] (CAMEL-8558) Camel Catalog - Add humanize component name
[ https://issues.apache.org/jira/browse/CAMEL-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8558: -- Assignee: Claus Ibsen Camel Catalog - Add humanize component name --- Key: CAMEL-8558 URL: https://issues.apache.org/jira/browse/CAMEL-8558 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.16.0 Each component has a name such as ejb, ftp, jms, mqtt, file etc. But presenting these names to humans,we may want to let the component provide a humainzed text of its name, so we can do 100% correct names. - ejb = EJB - mqtt = MQTT - sap-netweaver = SAP NetWeaver and so on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8559) Upgrade to jsonpath 2
Claus Ibsen created CAMEL-8559: -- Summary: Upgrade to jsonpath 2 Key: CAMEL-8559 URL: https://issues.apache.org/jira/browse/CAMEL-8559 Project: Camel Issue Type: Improvement Components: camel-jsonpath Reporter: Claus Ibsen Fix For: 2.16.0 They have released 2.0. We should upgrade to this https://github.com/jayway/JsonPath -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8549) camel-jackson should provide Map = Object converter
Henryk Konsek created CAMEL-8549:
Summary: camel-jackson should provide Map = Object converter
Key: CAMEL-8549
URL: https://issues.apache.org/jira/browse/CAMEL-8549
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be
nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8550) camel-jackson should provide Map = Object converter
Henryk Konsek created CAMEL-8550:
Summary: camel-jackson should provide Map = Object converter
Key: CAMEL-8550
URL: https://issues.apache.org/jira/browse/CAMEL-8550
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be
nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8553) camel-jackson should provide Map = Object converter
Henryk Konsek created CAMEL-8553:
Summary: camel-jackson should provide Map = Object converter
Key: CAMEL-8553
URL: https://issues.apache.org/jira/browse/CAMEL-8553
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be
nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8552) camel-jackson should provide Map = Object converter
Henryk Konsek created CAMEL-8552:
Summary: camel-jackson should provide Map = Object converter
Key: CAMEL-8552
URL: https://issues.apache.org/jira/browse/CAMEL-8552
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be
nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8554) camel-jackson should provide Map = Object converter
Henryk Konsek created CAMEL-8554:
Summary: camel-jackson should provide Map = Object converter
Key: CAMEL-8554
URL: https://issues.apache.org/jira/browse/CAMEL-8554
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be
nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8554) camel-jackson should provide Map = Object converter
[
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henryk Konsek resolved CAMEL-8554.
--
Resolution: Fixed
Resolved in 2fa60111add917affc161570892efda4a763f56a.
camel-jackson should provide Map = Object converter
Key: CAMEL-8554
URL: https://issues.apache.org/jira/browse/CAMEL-8554
Project: Camel
Issue Type: Improvement
Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
Fix For: 2.16.0
Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would
be nice if Jackson component provide this kind of fallback converter then.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14381943#comment-14381943
]
ASF GitHub Bot commented on CAMEL-8556:
---
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/446
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Fix For: 2.15.1, 2.16.0
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8556:
---
Priority: Minor (was: Major)
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Priority: Minor
Fix For: 2.15.1, 2.16.0
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8556) AnnotationTypeConverterLoader treats package as class
[
https://issues.apache.org/jira/browse/CAMEL-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-8556.
Resolution: Fixed
Fix Version/s: 2.16.0
Assignee: Claus Ibsen
AnnotationTypeConverterLoader treats package as class
-
Key: CAMEL-8556
URL: https://issues.apache.org/jira/browse/CAMEL-8556
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.0
Reporter: Thomas Diesler
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.15.1, 2.16.0
A package with an uppercase letter like
{code}
org.wildfly.camel.test.core.subA
{code}
would be treated as class leading to
{code}
Caused by: java.lang.NullPointerException
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.loadConverterMethods(AnnotationTypeConverterLoader.java:262)
at
org.apache.camel.impl.converter.AnnotationTypeConverterLoader.load(AnnotationTypeConverterLoader.java:130)
at
org.apache.camel.impl.converter.BaseTypeConverterRegistry.loadTypeConverters(BaseTypeConverterRegistry.java:544)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
