[jira] [Comment Edited] (CAMEL-17668) camel-core - WireTap - Remove function to tap as new body/header
[
https://issues.apache.org/jira/browse/CAMEL-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852455#comment-17852455
]
Henrik edited comment on CAMEL-17668 at 6/24/24 11:45 AM:
--
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
was (Author: monti):
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
> camel-core - WireTap - Remove function to tap as new body/header
>
>
> Key: CAMEL-17668
> URL: https://issues.apache.org/jira/browse/CAMEL-17668
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> The wiretap should be for tapping the message as-is, and not to create new
> messages.
> Otherwise the onPrepare processor can be used to customize a new message with
> copy option enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17668) camel-core - WireTap - Remove function to tap as new body/header
[
https://issues.apache.org/jira/browse/CAMEL-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852455#comment-17852455
]
Henrik edited comment on CAMEL-17668 at 6/24/24 11:45 AM:
--
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
was (Author: monti):
[~davsclaus] I'm sorry to comment on a very old issue, but I finally in the
process of upgrading our old Camel 2.x stack. I haven't found any examples of
this, so: what should I replace `newExchange()` with in this instance?
{code:java}
exceptionErrorHandlers.forEach {
onException(it.exceptionToHandle)
.process(ErrorHandlerProcessor(provider(), it))
.wireTap(Endpoint.solrizeUri)
.newExchange(StatusMessage(STATUS_FAILED_KEY))
.end()
.handled(true)
.bean(providerFailedCounter, "inc()")
} {code}
> camel-core - WireTap - Remove function to tap as new body/header
>
>
> Key: CAMEL-17668
> URL: https://issues.apache.org/jira/browse/CAMEL-17668
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> The wiretap should be for tapping the message as-is, and not to create new
> messages.
> Otherwise the onPrepare processor can be used to customize a new message with
> copy option enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18320) camel-core - Move xtokenize language into camel-stax
[ https://issues.apache.org/jira/browse/CAMEL-18320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859648#comment-17859648 ] Henrik commented on CAMEL-18320: For anyone else encountering "NoSuchLanguageException: No language could be found for: xtokenize": I needed to include the "camel-stax" dependency to fix this when upgrading to 3.19.0. > camel-core - Move xtokenize language into camel-stax > > > Key: CAMEL-18320 > URL: https://issues.apache.org/jira/browse/CAMEL-18320 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > This language needs a StAX parser that is not out of the box in the JDK that > works, instead you need to use woostock which we provide via camel-stax. > So lets move the language there so it will work OOTB for everyone. > CEQ has a special note about this at: > https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/xml-jaxp.html#_usage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17668) camel-core - WireTap - Remove function to tap as new body/header
[
https://issues.apache.org/jira/browse/CAMEL-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852455#comment-17852455
]
Henrik commented on CAMEL-17668:
[~davsclaus] I'm sorry to comment on a very old issue, but I finally in the
process of upgrading our old Camel 2.x stack. I haven't found any examples of
this, so: what should I replace `newExchange()` with in this instance?
{code:java}
exceptionErrorHandlers.forEach {
onException(it.exceptionToHandle)
.process(ErrorHandlerProcessor(provider(), it))
.wireTap(Endpoint.solrizeUri)
.newExchange(StatusMessage(STATUS_FAILED_KEY))
.end()
.handled(true)
.bean(providerFailedCounter, "inc()")
} {code}
> camel-core - WireTap - Remove function to tap as new body/header
>
>
> Key: CAMEL-17668
> URL: https://issues.apache.org/jira/browse/CAMEL-17668
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> The wiretap should be for tapping the message as-is, and not to create new
> messages.
> Otherwise the onPrepare processor can be used to customize a new message with
> copy option enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Component/s: camel-spring-boot camel-spring > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx, camel-spring, camel-spring-boot >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > Attachments: camel-2-17-7.txt, camel-2-18-0.txt > > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > The offending commit is > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > , but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Attachment: camel-2-18-0.txt camel-2-17-7.txt In the log from 2.17.7 ([^camel-2-17-7.txt]) we can see that the camel context starts up early, and the managementName and managementCamelContext is available. In the log from 2.18.0 ([^camel-2-18-0.txt]) Camel & JMX starts much later, and both the Bean and afterPropertiesSet() gets null when reading managementName and managementCamelContext. > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > Attachments: camel-2-17-7.txt, camel-2-18-0.txt > > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > The offending commit is > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > , but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Description: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. The offending commit is https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f , but I can't see why it creates trouble. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html was: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. A git bisect shows https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f as the offending commit, but I can't see why it creates trouble. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > The offending commit is > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > , but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Regression: Regression > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > A git bisect shows > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > as the offending commit, but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Description: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. A git bisect shows https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f as the offending commit, but I can't see why it creates trouble. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html was: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > A git bisect shows > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > as the offending commit, but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
[ https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-11536: --- Description: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. A git bisect shows https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f as the offending commit, but I can't see why it creates trouble. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html was: I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. A git bisect shows https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f as the offending commit, but I can't see why it creates trouble. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html > camelContext.getManagedCamelContext returns null in 2.18+ > - > > Key: CAMEL-11536 > URL: https://issues.apache.org/jira/browse/CAMEL-11536 > Project: Camel > Issue Type: Bug > Components: camel-jmx >Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1 >Reporter: Henrik > > I have created an example project at https://github.com/henrik242/camel218jmx > that shows the problem: > SomeTest shows how camelContext.getManagementName() is null in 2.18.x when > fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a > Bean. 2.17.7 does not have this problem. > If I have an Autowired camelContext in the test, then getManagementName() > returns the proper name. > A git bisect shows > https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f > as the offending commit, but I can't see why it creates trouble. > Mailing list thread: > http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11536) camelContext.getManagedCamelContext returns null in 2.18+
Henrik created CAMEL-11536: -- Summary: camelContext.getManagedCamelContext returns null in 2.18+ Key: CAMEL-11536 URL: https://issues.apache.org/jira/browse/CAMEL-11536 Project: Camel Issue Type: Bug Components: camel-jmx Affects Versions: 2.19.1, 2.19.0, 2.18.4, 2.18.3, 2.18.2, 2.18.1, 2.18.0 Reporter: Henrik I have created an example project at https://github.com/henrik242/camel218jmx that shows the problem: SomeTest shows how camelContext.getManagementName() is null in 2.18.x when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. 2.17.7 does not have this problem. If I have an Autowired camelContext in the test, then getManagementName() returns the proper name. Mailing list thread: http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-9485) camel-servlet is no-longer working in 2.16.1 (works in 2.15.3 and 2.16.0)
[
https://issues.apache.org/jira/browse/CAMEL-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15087044#comment-15087044
]
Henrik commented on CAMEL-9485:
---
So, the url has changed since 2.16.0 and 2.15.4?
> camel-servlet is no-longer working in 2.16.1 (works in 2.15.3 and 2.16.0)
> -
>
> Key: CAMEL-9485
> URL: https://issues.apache.org/jira/browse/CAMEL-9485
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Affects Versions: 2.16.1
>Reporter: Henrik
>
> As reported by Mel in
> http://camel.465427.n5.nabble.com/camel-servlet-is-no-longer-working-in-2-16-1-works-in-2-15-3-and-2-16-0-td5774558.html
> on Nov 30, 2015 (reporting here since it affects me too):
> I am using the camel-servlet component, in an app hosted in tomcat, to
> trigger a route via a URL such as this
> http://localhost:9090/appcontext/triggerimport/
> When upgrading to 2.16.1 the URL fails to trigger the route; the URL works
> if I downgrade to 2.15.3 or 2.16.0 (looks like CAMEL-9263 may have introduced
> the issue)
> web.xml:
> {code}
>
> MyTriggerImportServlet
> Trigger import of JArchive content
>
>
> org.apache.camel.component.servlet.CamelHttpTransportServlet
> 2
>
> ignoreDuplicateServletName
> true
>
>
>
>
> MyTriggerImportServlet
> /triggerimport/*
>
> {code}
>
> camel-config.xml:
> {code}
>
>uri="servlet://jarchive?servletName=MyTriggerImportServletmatchOnUriPrefix=true"
> />
>
>
> {code}
> The endpoint is actually starting up:
> {code}[INFO ] [2016-01-06T15:30:37,050] [RMI TCP Connection(3)-127.0.0.1]
> Initialized CamelHttpTransportServlet[name= MyTriggerImportServlet,
> contextPath=/my-integration] [CamelHttpTransportServlet] {code}
> 2.16.2-SNAPSHOT does not fix the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-9485) camel-servlet is no-longer working in 2.16.1 (works in 2.15.3 and 2.16.0)
Henrik created CAMEL-9485:
-
Summary: camel-servlet is no-longer working in 2.16.1 (works in
2.15.3 and 2.16.0)
Key: CAMEL-9485
URL: https://issues.apache.org/jira/browse/CAMEL-9485
Project: Camel
Issue Type: Bug
Components: camel-servlet
Affects Versions: 2.16.1
Reporter: Henrik
As reported my "MEL" in
http://mail-archives.apache.org/mod_mbox/camel-users/201511.mbox/%3c1448892863338-5774558.p...@n5.nabble.com%3E
on Nov 30, 2015 (reporting here since it affects me too):
I am using the camel-servlet component, in an app hosted in tomcat, to
trigger a route via a URL such as this
http://localhost:9090/appcontext/triggerimport/
When upgrading to 2.16.1 the URL fails to trigger the route; the URL works
if I downgrade to 2.15.3 or 2.16.0 (looks like CAMEL-9263 may have
introduced the issue)
web.xml:
{code}
MyTriggerImportServlet
Trigger import of JArchive content
org.apache.camel.component.servlet.CamelHttpTransportServlet
2
ignoreDuplicateServletName
true
MyTriggerImportServlet
/triggerimport/*
{code}
camel-config.xml
{code}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-9485) camel-servlet is no-longer working in 2.16.1 (works in 2.15.3 and 2.16.0)
[
https://issues.apache.org/jira/browse/CAMEL-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik updated CAMEL-9485:
--
Description:
As reported by "MEL" in
http://mail-archives.apache.org/mod_mbox/camel-users/201511.mbox/%3c1448892863338-5774558.p...@n5.nabble.com%3E
on Nov 30, 2015 (reporting here since it affects me too):
I am using the camel-servlet component, in an app hosted in tomcat, to trigger
a route via a URL such as this
http://localhost:9090/appcontext/triggerimport/
When upgrading to 2.16.1 the URL fails to trigger the route; the URL works if
I downgrade to 2.15.3 or 2.16.0 (looks like CAMEL-9263 may have introduced the
issue)
web.xml:
{code}
MyTriggerImportServlet
Trigger import of JArchive content
org.apache.camel.component.servlet.CamelHttpTransportServlet
2
ignoreDuplicateServletName
true
MyTriggerImportServlet
/triggerimport/*
{code}
camel-config.xml:
{code}
{code}
was:
As reported my "MEL" in
http://mail-archives.apache.org/mod_mbox/camel-users/201511.mbox/%3c1448892863338-5774558.p...@n5.nabble.com%3E
on Nov 30, 2015 (reporting here since it affects me too):
I am using the camel-servlet component, in an app hosted in tomcat, to
trigger a route via a URL such as this
http://localhost:9090/appcontext/triggerimport/
When upgrading to 2.16.1 the URL fails to trigger the route; the URL works
if I downgrade to 2.15.3 or 2.16.0 (looks like CAMEL-9263 may have
introduced the issue)
web.xml:
{code}
MyTriggerImportServlet
Trigger import of JArchive content
org.apache.camel.component.servlet.CamelHttpTransportServlet
2
ignoreDuplicateServletName
true
MyTriggerImportServlet
/triggerimport/*
{code}
camel-config.xml
{code}
{code}
> camel-servlet is no-longer working in 2.16.1 (works in 2.15.3 and 2.16.0)
> -
>
> Key: CAMEL-9485
> URL: https://issues.apache.org/jira/browse/CAMEL-9485
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Affects Versions: 2.16.1
>Reporter: Henrik
>
> As reported by "MEL" in
> http://mail-archives.apache.org/mod_mbox/camel-users/201511.mbox/%3c1448892863338-5774558.p...@n5.nabble.com%3E
> on Nov 30, 2015 (reporting here since it affects me too):
> I am using the camel-servlet component, in an app hosted in tomcat, to
> trigger a route via a URL such as this
> http://localhost:9090/appcontext/triggerimport/
> When upgrading to 2.16.1 the URL fails to trigger the route; the URL works
> if I downgrade to 2.15.3 or 2.16.0 (looks like CAMEL-9263 may have introduced
> the issue)
> web.xml:
> {code}
>
> MyTriggerImportServlet
> Trigger import of JArchive content
>
>
> org.apache.camel.component.servlet.CamelHttpTransportServlet
> 2
>
> ignoreDuplicateServletName
> true
>
>
>
>
> MyTriggerImportServlet
> /triggerimport/*
>
> {code}
>
> camel-config.xml:
> {code}
>
>uri="servlet://jarchive?servletName=MyTriggerImportServletmatchOnUriPrefix=true"
> />
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237752#comment-14237752 ] Henrik commented on CAMEL-7835: --- [~davsclaus] Any chance this can go into 2.14.1? camel-test-spring doesn't support Spring 4.1.0.RELEASE -- Key: CAMEL-7835 URL: https://issues.apache.org/jira/browse/CAMEL-7835 Project: Camel Issue Type: Task Components: camel-test Affects Versions: 2.14.0 Reporter: Henrik Assignee: Claus Ibsen Labels: deprecation, junit, spring, test Fix For: 2.15.0 CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and the TestContextManager.getDefaultTestExecutionListenerClasses() method. Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237752#comment-14237752 ] Henrik edited comment on CAMEL-7835 at 12/8/14 11:02 AM: - [~davsclaus] [~wuwen] Any chance this can go into 2.14.1? was (Author: monti): [~davsclaus] Any chance this can go into 2.14.1? camel-test-spring doesn't support Spring 4.1.0.RELEASE -- Key: CAMEL-7835 URL: https://issues.apache.org/jira/browse/CAMEL-7835 Project: Camel Issue Type: Task Components: camel-test Affects Versions: 2.14.0 Reporter: Henrik Assignee: Claus Ibsen Labels: deprecation, junit, spring, test Fix For: 2.15.0 CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and the TestContextManager.getDefaultTestExecutionListenerClasses() method. Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
Henrik created CAMEL-7835: - Summary: camel-test-spring doesn't support Spring 4.1.0.RELEASE Key: CAMEL-7835 URL: https://issues.apache.org/jira/browse/CAMEL-7835 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.14.0 Reporter: Henrik CamelSpringJUnit4ClassRunner calls TestContextManager(Class, String) constructor, and TestContextManager.getDefaultTestExecutionListenerClasses(). Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-7835: -- Description: CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and TestContextManager.getDefaultTestExecutionListenerClasses(). Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. was: CamelSpringJUnit4ClassRunner calls TestContextManager(Class, String) constructor, and TestContextManager.getDefaultTestExecutionListenerClasses(). Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. camel-test-spring doesn't support Spring 4.1.0.RELEASE -- Key: CAMEL-7835 URL: https://issues.apache.org/jira/browse/CAMEL-7835 Project: Camel Issue Type: Bug Components: camel-spring Affects Versions: 2.14.0 Reporter: Henrik Labels: deprecation, junit, spring, test CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and TestContextManager.getDefaultTestExecutionListenerClasses(). Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7835) camel-test-spring doesn't support Spring 4.1.0.RELEASE
[ https://issues.apache.org/jira/browse/CAMEL-7835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henrik updated CAMEL-7835: -- Description: CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and the TestContextManager.getDefaultTestExecutionListenerClasses() method. Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. was: CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and TestContextManager.getDefaultTestExecutionListenerClasses(). Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. camel-test-spring doesn't support Spring 4.1.0.RELEASE -- Key: CAMEL-7835 URL: https://issues.apache.org/jira/browse/CAMEL-7835 Project: Camel Issue Type: Task Components: camel-test Affects Versions: 2.14.0 Reporter: Henrik Labels: deprecation, junit, spring, test Fix For: 2.15.0 CamelSpringJUnit4ClassRunner calls the TestContextManager(Class, String) constructor, and the TestContextManager.getDefaultTestExecutionListenerClasses() method. Both of these are deprecated in spring-test-4.0.x, and are gone in 4.1.x. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7074) Upgrade to spring 4.x
[
https://issues.apache.org/jira/browse/CAMEL-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13976524#comment-13976524
]
Henrik commented on CAMEL-7074:
---
Morten: That pull request has been merged into the 3.2.x branch and will be
present in 3.2.9:
https://github.com/spring-projects/spring-framework/commit/9ac46a965f3314f09ec5a75eded97589ab13fbdb
Upgrade to spring 4.x
-
Key: CAMEL-7074
URL: https://issues.apache.org/jira/browse/CAMEL-7074
Project: Camel
Issue Type: Task
Components: camel-spring
Reporter: David J. M. Karlsen
Assignee: Willem Jiang
Fix For: 2.14.0
Upgrade to spring4.
There is a non-backwards compatible change in spring 4.x which will cause:
{noformat}
java.lang.IncompatibleClassChangeError: Found interface
org.springframework.test.context.TestContext, but class was expected
at
org.apache.camel.test.spring.CamelSpringTestContextLoaderTestExecutionListener.prepareTestInstance(CamelSpringTestContextLoaderTestExecutionListener.java:35)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:326)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:212)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:232)
at
org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner.runChild(CamelSpringJUnit4ClassRunner.java:37)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:175)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
{noformat}
due to https://jira.springsource.org/browse/SPR-7692
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7074) Upgrade to spring 4.x
[
https://issues.apache.org/jira/browse/CAMEL-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903871#comment-13903871
]
Henrik commented on CAMEL-7074:
---
Thanks!
Upgrade to spring 4.x
-
Key: CAMEL-7074
URL: https://issues.apache.org/jira/browse/CAMEL-7074
Project: Camel
Issue Type: Task
Components: camel-spring
Reporter: David J. M. Karlsen
Assignee: Willem Jiang
Fix For: Future
Upgrade to spring4.
There is a non-backwards compatible change in spring 4.x which will cause:
{noformat}
java.lang.IncompatibleClassChangeError: Found interface
org.springframework.test.context.TestContext, but class was expected
at
org.apache.camel.test.spring.CamelSpringTestContextLoaderTestExecutionListener.prepareTestInstance(CamelSpringTestContextLoaderTestExecutionListener.java:35)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:326)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:212)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:232)
at
org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner.runChild(CamelSpringJUnit4ClassRunner.java:37)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:175)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
{noformat}
due to https://jira.springsource.org/browse/SPR-7692
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CAMEL-7074) Upgrade to spring 4.x
[
https://issues.apache.org/jira/browse/CAMEL-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903219#comment-13903219
]
Henrik commented on CAMEL-7074:
---
Is there any ETA on this issue?
Upgrade to spring 4.x
-
Key: CAMEL-7074
URL: https://issues.apache.org/jira/browse/CAMEL-7074
Project: Camel
Issue Type: Task
Components: camel-spring
Reporter: David J. M. Karlsen
Assignee: Willem Jiang
Fix For: Future
Upgrade to spring4.
There is a non-backwards compatible change in spring 4.x which will cause:
{noformat}
java.lang.IncompatibleClassChangeError: Found interface
org.springframework.test.context.TestContext, but class was expected
at
org.apache.camel.test.spring.CamelSpringTestContextLoaderTestExecutionListener.prepareTestInstance(CamelSpringTestContextLoaderTestExecutionListener.java:35)
at
org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:326)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:212)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:289)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.methodBlock(SpringJUnit4ClassRunner.java:291)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:232)
at
org.apache.camel.test.junit4.CamelSpringJUnit4ClassRunner.runChild(CamelSpringJUnit4ClassRunner.java:37)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:175)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
{noformat}
due to https://jira.springsource.org/browse/SPR-7692
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
