[jira] [Assigned] (CAMEL-13220) camel-jetty - Remove deprecated producer
[ https://issues.apache.org/jira/browse/CAMEL-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13220: --- Assignee: Claus Ibsen > camel-jetty - Remove deprecated producer > > > Key: CAMEL-13220 > URL: https://issues.apache.org/jira/browse/CAMEL-13220 > Project: Camel > Issue Type: Task > Components: camel-jetty >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The producer of camel-jetty has been deprecated in Camel 2.x, and should be > removed in 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13220) camel-jetty - Remove deprecated producer
[ https://issues.apache.org/jira/browse/CAMEL-13220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13220: Fix Version/s: (was: 3.0.0-M3) 3.0.0.M4 > camel-jetty - Remove deprecated producer > > > Key: CAMEL-13220 > URL: https://issues.apache.org/jira/browse/CAMEL-13220 > Project: Camel > Issue Type: Task > Components: camel-jetty >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The producer of camel-jetty has been deprecated in Camel 2.x, and should be > removed in 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13594) camel apt - Avoid generating TypeConverter META-INF file when we generate TypeConverterLoader
[ https://issues.apache.org/jira/browse/CAMEL-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13594. - Resolution: Fixed > camel apt - Avoid generating TypeConverter META-INF file when we generate > TypeConverterLoader > - > > Key: CAMEL-13594 > URL: https://issues.apache.org/jira/browse/CAMEL-13594 > Project: Camel > Issue Type: Improvement > Components: build system >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We can optimize this to only have the newer TypeConverterLoader file which > has all the type converters that are optimized. And then in tooling/apt avoid > generate both TypeConverter and TypeConverterLoaded meta files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12481) Camel-Mongodb3: Add support for Change Streams feature
[ https://issues.apache.org/jira/browse/CAMEL-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12481: Fix Version/s: 3.0.0.M4 3.0.0 > Camel-Mongodb3: Add support for Change Streams feature > -- > > Key: CAMEL-12481 > URL: https://issues.apache.org/jira/browse/CAMEL-12481 > Project: Camel > Issue Type: New Feature > Components: camel-mongodb3 >Reporter: Andrea Cosentino >Assignee: Denis Istomin >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > https://docs.mongodb.com/manual/changeStreams/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13606) Olingo Consumer filtering can cause NPE
[ https://issues.apache.org/jira/browse/CAMEL-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13606: Fix Version/s: 3.0.0.M4 2.25.0 2.24.1 2.23.3 3.0.0 > Olingo Consumer filtering can cause NPE > --- > > Key: CAMEL-13606 > URL: https://issues.apache.org/jira/browse/CAMEL-13606 > Project: Camel > Issue Type: Bug > Components: camel-olingo2, camel-olingo4 >Affects Versions: 2.21.5 >Reporter: Paul Richardson >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 2.25.0, 3.0.0.M4 > > > When polling with the Olingo*Consumer, the result is intercepted and filtered > (if filtering is switched on). If a key predicate is used as well then, on > subsequent polling iterations, the result is filtered to return null. When > the result is then intercepted and passed to the Olingo*Index for indexing, > the latter fails to handle the null value and causes an NullPointerException. > This exception is reported/logged and polling continues with subsequent > iterations (also blowing up with NPEs). Need to fix the Index classes so they > handle null values correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13611: - Fix Version/s: (was: 2.24.1) 2.25.0 3.0.0 > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 2.25.0 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13611: Assignee: Andrea Cosentino > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.24.1 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13611: Assignee: Andrea Cosentino > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.24.1 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13611: Assignee: (was: Andrea Cosentino) > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Priority: Major > Fix For: 2.24.1 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-9103) camel-cxf does not handle soapfaults with ws-addressing headers in async mode
[
https://issues.apache.org/jira/browse/CAMEL-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856111#comment-16856111
]
Freeman Fang commented on CAMEL-9103:
-
For the async mode, I believe the problem comes from the test soap response
itself
currently it's
{code}
http://www.w3.org/2005/08/addressing;
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/;>
http://www.w3.org/2005/08/addressing/soap/fault
env:Client
Rejected by policy.
urn:nav:ikt:plattform:samhandling:t5_pepgwsbs:OutboundPartnerSecurityGateway
{code}
and per MAPCodec.markPartialResponse method, this message lack of RelatesTo
ws-addressing header, so it's a partial response(empty message). And per the
spec, reply message must have RelatesTo header, we can see more details from
discussion CXF-3916.
If I add a
{code}
1234567
{code}
header into soapfault.xml, the sync/async behavior are identical. So IMO, this
is a testcase problem which uses invalid soap resp message.
Freeman
> camel-cxf does not handle soapfaults with ws-addressing headers in async mode
> -
>
> Key: CAMEL-9103
> URL: https://issues.apache.org/jira/browse/CAMEL-9103
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.15.3
>Reporter: Bjørn Hilstad
>Assignee: Freeman Fang
>Priority: Minor
> Attachments: camel-jboss-web.7z
>
>
> I am invoking a SOAP 1.1 webservice with WS-Addressing using camel-cxf. When
> the webservice returns a soapfault that includes a ws-addressing header
> (http://www.w3.org/2005/08/addressing/soap/fault)
> which I believe is allowed per spec (ws-addressing) I can see in logs that
> cxf processes the response but the response never reaches Camel (would be
> handled by the DefaultErrorHandler). The thread just hangs forever.
> I have been able to get the same test to work if I configure the camel
> endpoint for cxf to use synchronous=true.
> I am attaching a maven project that contains a test that reproduces the
> issue. The test uses wiremock as a stub to return the response.
> If the endpoint in the camelcontext is changed to use synchronous=true the
> test succeeds (it gets the soapfault that is expected).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
[ https://issues.apache.org/jira/browse/CAMEL-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13611: - Affects Version/s: (was: 2.21.1) > Camel Web3j - Upgrade to Web3j 4.3.1 > > > Key: CAMEL-13611 > URL: https://issues.apache.org/jira/browse/CAMEL-13611 > Project: Camel > Issue Type: New Feature >Reporter: Choucri Fahed >Priority: Major > Fix For: 2.24.1 > > > Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-12481) Camel-Mongodb3: Add support for Change Streams feature
[ https://issues.apache.org/jira/browse/CAMEL-12481?focusedWorklogId=253952=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-253952 ] ASF GitHub Bot logged work on CAMEL-12481: -- Author: ASF GitHub Bot Created on: 04/Jun/19 19:03 Start Date: 04/Jun/19 19:03 Worklog Time Spent: 10m Work Description: DenisIstomin commented on pull request #2960: CAMEL-12481: Add Change Streams support to MongoDB component URL: https://github.com/apache/camel/pull/2960 1. For Tailing consumer and StreamChange consumer common code moved to the abstract class. 1. New property `streamFilter` used as route property. Maybe this is wrong usage of route properties. I wanted to provide flexible and declarative way of configuration in XML DSL. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 253952) Time Spent: 10m Remaining Estimate: 0h > Camel-Mongodb3: Add support for Change Streams feature > -- > > Key: CAMEL-12481 > URL: https://issues.apache.org/jira/browse/CAMEL-12481 > Project: Camel > Issue Type: New Feature > Components: camel-mongodb3 >Reporter: Andrea Cosentino >Assignee: Denis Istomin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > https://docs.mongodb.com/manual/changeStreams/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13611) Camel Web3j - Upgrade to Web3j 4.3.1
Choucri Fahed created CAMEL-13611: - Summary: Camel Web3j - Upgrade to Web3j 4.3.1 Key: CAMEL-13611 URL: https://issues.apache.org/jira/browse/CAMEL-13611 Project: Camel Issue Type: New Feature Affects Versions: 2.21.1 Reporter: Choucri Fahed Fix For: 2.24.1 Support the latest version of Web3j. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-9103) camel-cxf does not handle soapfaults with ws-addressing headers in async mode
[ https://issues.apache.org/jira/browse/CAMEL-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855885#comment-16855885 ] Freeman Fang commented on CAMEL-9103: - I can still reproduce it with latest CXF 3.3.2, I'd like to take a close look > camel-cxf does not handle soapfaults with ws-addressing headers in async mode > - > > Key: CAMEL-9103 > URL: https://issues.apache.org/jira/browse/CAMEL-9103 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.15.3 >Reporter: Bjørn Hilstad >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-jboss-web.7z > > > I am invoking a SOAP 1.1 webservice with WS-Addressing using camel-cxf. When > the webservice returns a soapfault that includes a ws-addressing header > (http://www.w3.org/2005/08/addressing/soap/fault) > which I believe is allowed per spec (ws-addressing) I can see in logs that > cxf processes the response but the response never reaches Camel (would be > handled by the DefaultErrorHandler). The thread just hangs forever. > I have been able to get the same test to work if I configure the camel > endpoint for cxf to use synchronous=true. > I am attaching a maven project that contains a test that reproduces the > issue. The test uses wiremock as a stub to return the response. > If the endpoint in the camelcontext is changed to use synchronous=true the > test succeeds (it gets the soapfault that is expected). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
[
https://issues.apache.org/jira/browse/CAMEL-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-12290.
--
Resolution: Information Provided
> CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
> -
>
> Key: CAMEL-12290
> URL: https://issues.apache.org/jira/browse/CAMEL-12290
> Project: Camel
> Issue Type: Task
> Components: camel-cxf
>Affects Versions: 2.20.1
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
>
> When I tried to run tests on JDK9 I get:
> {code:java}
> java.lang.NoClassDefFoundError: javax/jws/WebService
> at
> org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
> at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
> at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
> at
> org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
> at
> org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
> at
> org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
> at
> org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:287)
> at
>
[jira] [Assigned] (CAMEL-9103) camel-cxf does not handle soapfaults with ws-addressing headers in async mode
[ https://issues.apache.org/jira/browse/CAMEL-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-9103: --- Assignee: Freeman Fang > camel-cxf does not handle soapfaults with ws-addressing headers in async mode > - > > Key: CAMEL-9103 > URL: https://issues.apache.org/jira/browse/CAMEL-9103 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.15.3 >Reporter: Bjørn Hilstad >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-jboss-web.7z > > > I am invoking a SOAP 1.1 webservice with WS-Addressing using camel-cxf. When > the webservice returns a soapfault that includes a ws-addressing header > (http://www.w3.org/2005/08/addressing/soap/fault) > which I believe is allowed per spec (ws-addressing) I can see in logs that > cxf processes the response but the response never reaches Camel (would be > handled by the DefaultErrorHandler). The thread just hangs forever. > I have been able to get the same test to work if I configure the camel > endpoint for cxf to use synchronous=true. > I am attaching a maven project that contains a test that reproduces the > issue. The test uses wiremock as a stub to return the response. > If the endpoint in the camelcontext is changed to use synchronous=true the > test succeeds (it gets the soapfault that is expected). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
[
https://issues.apache.org/jira/browse/CAMEL-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855884#comment-16855884
]
Freeman Fang commented on CAMEL-12290:
--
Thanks [~eximius]!
Since java9 isn't a LTS java version and CXF 3.3.x has JDK11 support, I'd like
to close this issue for now. We can reopen if we do need it in the future.
Freeman
> CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
> -
>
> Key: CAMEL-12290
> URL: https://issues.apache.org/jira/browse/CAMEL-12290
> Project: Camel
> Issue Type: Task
> Components: camel-cxf
>Affects Versions: 2.20.1
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
>
> When I tried to run tests on JDK9 I get:
> {code:java}
> java.lang.NoClassDefFoundError: javax/jws/WebService
> at
> org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
> at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
> at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
> at
> org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
> at
> org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
> at
> org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
> at
> org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230)
> at
>
[jira] [Assigned] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
[
https://issues.apache.org/jira/browse/CAMEL-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CAMEL-12290:
Assignee: Freeman Fang
> CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
> -
>
> Key: CAMEL-12290
> URL: https://issues.apache.org/jira/browse/CAMEL-12290
> Project: Camel
> Issue Type: Task
> Components: camel-cxf
>Affects Versions: 2.20.1
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
>
> When I tried to run tests on JDK9 I get:
> {code:java}
> java.lang.NoClassDefFoundError: javax/jws/WebService
> at
> org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
> at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
> at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
> at
> org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
> at
> org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
> at
> org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
> at
> org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner$1.runReflectiveCall(SpringJUnit4ClassRunner.java:287)
> at
>
[jira] [Commented] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
[
https://issues.apache.org/jira/browse/CAMEL-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855877#comment-16855877
]
Kamil commented on CAMEL-12290:
---
[~ffang] I believe CXF version was related to camel-cxf (which was in version
2.20.1)
Unfortunatelly I'm no longer in that project
> CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
> -
>
> Key: CAMEL-12290
> URL: https://issues.apache.org/jira/browse/CAMEL-12290
> Project: Camel
> Issue Type: Task
> Components: camel-cxf
>Affects Versions: 2.20.1
>Reporter: Kamil
>Priority: Minor
>
> When I tried to run tests on JDK9 I get:
> {code:java}
> java.lang.NoClassDefFoundError: javax/jws/WebService
> at
> org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
> at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
> at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
> at
> org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
> at
> org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
> at
> org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
> at
> org.springframework.test.context.TestContextManager.prepareTestInstance(TestContextManager.java:230)
> at
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.createTest(SpringJUnit4ClassRunner.java:228)
> at
>
[jira] [Resolved] (CAMEL-13610) Allow for expressions as arguments to RouteBuilder.{from,to}() to dynamically change endpoint URIs using the Java DSL
[
https://issues.apache.org/jira/browse/CAMEL-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13610.
-
Resolution: Won't Fix
Hi
This is not on our roadmap and Camel routes in the DSL are using endpoints via
string or as an existing endpoint instance. For the latter you can build your
own expression -> endpoint logic or whatever you do to refer to the endpoint to
use.
Also mind that a Camel Expression is bound to an Exchange, eg during routing
messages, and not for dynamic configuration during startup etc.
> Allow for expressions as arguments to RouteBuilder.{from,to}() to dynamically
> change endpoint URIs using the Java DSL
> -
>
> Key: CAMEL-13610
> URL: https://issues.apache.org/jira/browse/CAMEL-13610
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Affects Versions: 2.22.1
>Reporter: Philipp Bachmann
>Priority: Major
>
> We use Apache Camel, in particular its IMAP and SMTP endpoins. When, for
> whatever reason, the endpoints fail, e.g. the SMTP server is down, then it
> was nice if we were able to connect to an alternative endpoint. As I have
> researched so far, Apache Camel does not allow for a dynamic way of
> specifying the URIs e.g. in terms of a user supplied callback Strategy. The
> only way I have figured out are the load balancing features, but then you
> still have to know the URIs in advance.
> So may I suggest to add overloads of the from() and to() methods that accept
> expressions, which in my opinion would gain the flexibility desired?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-9421) CxfEndpoint Not using proper Service Factory when javax.jws.WebService is proxied
[
https://issues.apache.org/jira/browse/CAMEL-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855780#comment-16855780
]
Freeman Fang commented on CAMEL-9421:
-
Hi [~jkampf],
If you have a reproducer project I'd like to take a close look.
Thanks!
Freeman
> CxfEndpoint Not using proper Service Factory when javax.jws.WebService is
> proxied
> -
>
> Key: CAMEL-9421
> URL: https://issues.apache.org/jira/browse/CAMEL-9421
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.13.3
> Environment: karaf 3.0.2
>Reporter: Joseph Kampf
>Priority: Minor
>
> Clearing out the karaf/data/cache directory and then doing a fresh deploy of
> the Bundle works fine.
> However after restarting Karaf the
> org.apache.cxf.jaxws.JaxWsServerFactoryBean is not used by the CxfEndpoint.
> Instead the org.apache.cxf.frontend.ServerFactoryBean is used. This causes
> the mapping of WSDL Operations to SEI methods to not work.
> This results in error messages:
> {quote}
> 2015-12-15 09:51:18,729 | WARN | xtenderThread-42 |
> ReflectionServiceFactoryBean | 194 - org.apache.cxf.cxf-rt-core - 2.7.11
> | No method was found for the WSDL operation <%WSDL Operation%>{quote}
> It also causes the CXF page to not list the WSDL Operations under the SOAP
> Port.
> The reason this is happening is because the annotations that are on the SEI
> class are proxied. This causes the annotation check in
> org.apache.camel.component.cxf.CxfSpringEndpoint.createServerFactoryBean() to
> seem as if the SEI does not have the javax.jws.WebService annotation.
> The annotation is on the list of annotations for the SEI, but they are
> proxied by sun.reflect.annotation.AnnotationInvocationHandler.
> One solution I see would be to change the implementation of
> org.apache.camel.component.cxf.CxfEndpointUtils.hasAnnotation() method.
> Instead of relying on Class.getAnnoation(), instead loop through the
> annotations on the class and not only check the annotation class directly,
> but also try to reach into the annotation to determine if it is a proxy of
> the annotation in question.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12290) CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
[
https://issues.apache.org/jira/browse/CAMEL-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855774#comment-16855774
]
Freeman Fang commented on CAMEL-12290:
--
Hi [~eximius],
Do you still have this issue now?
I assume you should use JDK11 now, and please let me know if you still have
this issue with latest camel+cxf.
And if you still have issue, please clarify the CXF version(you should use CXF
3.3.x which has JDK 11 support) you are using and a reproducer project is more
helpful.
Thanks!
Freeman
> CxfEndpoint with JDK9: NoClassDefFoundError: javax/jws/WebService
> -
>
> Key: CAMEL-12290
> URL: https://issues.apache.org/jira/browse/CAMEL-12290
> Project: Camel
> Issue Type: Task
> Components: camel-cxf
>Affects Versions: 2.20.1
>Reporter: Kamil
>Priority: Minor
>
> When I tried to run tests on JDK9 I get:
> {code:java}
> java.lang.NoClassDefFoundError: javax/jws/WebService
> at
> org.apache.camel.component.cxf.CxfEndpointUtils.hasWebServiceAnnotation(CxfEndpointUtils.java:88)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClientFactoryBean(CxfEndpoint.java:394)
> at
> org.apache.camel.component.cxf.CxfEndpoint.createClient(CxfEndpoint.java:635)
> at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:84)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.SynchronousDelegateProducer.start(SynchronousDelegateProducer.java:66)
> at org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
> at
> org.apache.camel.impl.DeferServiceStartupListener.onCamelContextStarted(DeferServiceStartupListener.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:3859)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:3638)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3490)
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> at
> org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:133)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:174)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360)
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
> at
> org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:120)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:98)
> at
> org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:116)
> at
> org.springframework.test.context.support.DefaultTestContext.getApplicationContext(DefaultTestContext.java:83)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.setUpRequestContextIfNecessary(ServletTestExecutionListener.java:189)
> at
> org.springframework.test.context.web.ServletTestExecutionListener.prepareTestInstance(ServletTestExecutionListener.java:131)
> at
>
[jira] [Commented] (CAMEL-12957) camel-cxf - Swagger/OpenAPI feature should not involve the Camel route
[ https://issues.apache.org/jira/browse/CAMEL-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855767#comment-16855767 ] Freeman Fang commented on CAMEL-12957: -- Hi [~jen...@gmx.net], Any chance you can append a testcase project? (github project or a zipped one here both are OK) Thanks! Freeman > camel-cxf - Swagger/OpenAPI feature should not involve the Camel route > -- > > Key: CAMEL-12957 > URL: https://issues.apache.org/jira/browse/CAMEL-12957 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 2.22.2 >Reporter: Jens Kleine-Herzbruch >Priority: Minor > > Currently, when adding Swagger2Feature or OpenApiFeature to a CXFRS endpoint, > the calls to the API descriptions go through the Camel route, ie. one has to > implement an additional Camel route in order to make those features work. > Using runAsFilter=false a call to > http://localhost:8080/services/myCamelService/openapi.json > results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > results in call of the Camel route with an operation "getResource" > Using runAsFilter=true the situation improves marginally: > http://localhost:8080/services/myCamelService/openapi.json > still results in a call of the Camel route with an operation "getOpenApi" > http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json > at least now shows the Swagger UI page frame but still fails to load the > actual service description since it again calls the Camel route with the > "getOpenApi" operation. > Supposedly that means the filter correctly intercepts the getResource call > but not the getOpenApi call. It would be great if this worked out of the box. > A custom implementation would still be possible by not running as a filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-8853) CXF endpoint with a relative address cannot be invoked by a producer template
[
https://issues.apache.org/jira/browse/CAMEL-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-8853.
-
Resolution: Not A Problem
Fix Version/s: (was: Future)
> CXF endpoint with a relative address cannot be invoked by a producer template
> -
>
> Key: CAMEL-8853
> URL: https://issues.apache.org/jira/browse/CAMEL-8853
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.15.2
>Reporter: Tomas Rohovsky
>Priority: Minor
> Attachments: cxf-producer-template.zip
>
>
> If you invoke this Camel CXF endpoint by a producer template:
> {code}
> serviceClass="org.example.cxf_producer_template.GreetingService"/>
> {code}
> you will get:
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Tom]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1635)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:645)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:331)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.example.cxf_producer_template.ProducerProcessor.process(ProducerProcessor.java:12)[265:cxf-producer-template:0.0.1.SNAPSHOT]
> at
> org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:129)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:165)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:73)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_71]
> at java.util.TimerThread.run(Timer.java:505)[:1.7.0_71]
> Caused by: java.lang.IllegalArgumentException: URI is not absolute
> at java.net.URI.toURL(URI.java:1095)[:1.7.0_71]
> at
> org.apache.cxf.transport.http.Address.getURL(Address.java:45)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:93)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit.setupConnection(URLConnectionHTTPConduit.java:105)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
>
[jira] [Commented] (CAMEL-8853) CXF endpoint with a relative address cannot be invoked by a producer template
[
https://issues.apache.org/jira/browse/CAMEL-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855759#comment-16855759
]
Freeman Fang commented on CAMEL-8853:
-
The relative address of cxf endpoint means using serlvet transport, it assume
the endpoint is deployed into servlet container.
In the test code, which suppose to use the plain http transport, should use
absolute url instead.
> CXF endpoint with a relative address cannot be invoked by a producer template
> -
>
> Key: CAMEL-8853
> URL: https://issues.apache.org/jira/browse/CAMEL-8853
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.15.2
>Reporter: Tomas Rohovsky
>Priority: Minor
> Fix For: Future
>
> Attachments: cxf-producer-template.zip
>
>
> If you invoke this Camel CXF endpoint by a producer template:
> {code}
> serviceClass="org.example.cxf_producer_template.GreetingService"/>
> {code}
> you will get:
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Tom]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1635)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:645)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:301)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:331)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.example.cxf_producer_template.ProducerProcessor.process(ProducerProcessor.java:12)[265:cxf-producer-template:0.0.1.SNAPSHOT]
> at
> org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:129)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:448)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:118)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:165)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at
> org.apache.camel.component.timer.TimerConsumer$1.run(TimerConsumer.java:73)[198:org.apache.camel.camel-core:2.15.1.redhat-620123]
> at java.util.TimerThread.mainLoop(Timer.java:555)[:1.7.0_71]
> at java.util.TimerThread.run(Timer.java:505)[:1.7.0_71]
> Caused by: java.lang.IllegalArgumentException: URI is not absolute
> at java.net.URI.toURL(URI.java:1095)[:1.7.0_71]
> at
> org.apache.cxf.transport.http.Address.getURL(Address.java:45)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit.createConnection(URLConnectionHTTPConduit.java:93)[123:org.apache.cxf.cxf-rt-transports-http:3.0.4.redhat-620123]
> at
>
[jira] [Created] (CAMEL-13610) Allow for expressions as arguments to RouteBuilder.{from,to}() to dynamically change endpoint URIs using the Java DSL
Philipp Bachmann created CAMEL-13610:
Summary: Allow for expressions as arguments to
RouteBuilder.{from,to}() to dynamically change endpoint URIs using the Java DSL
Key: CAMEL-13610
URL: https://issues.apache.org/jira/browse/CAMEL-13610
Project: Camel
Issue Type: New Feature
Components: camel-core
Affects Versions: 2.22.1
Reporter: Philipp Bachmann
We use Apache Camel, in particular its IMAP and SMTP endpoins. When, for
whatever reason, the endpoints fail, e.g. the SMTP server is down, then it was
nice if we were able to connect to an alternative endpoint. As I have
researched so far, Apache Camel does not allow for a dynamic way of specifying
the URIs e.g. in terms of a user supplied callback Strategy. The only way I
have figured out are the load balancing features, but then you still have to
know the URIs in advance.
So may I suggest to add overloads of the from() and to() methods that accept
expressions, which in my opinion would gain the flexibility desired?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13594) camel apt - Avoid generating TypeConverter META-INF file when we generate TypeConverterLoader
[ https://issues.apache.org/jira/browse/CAMEL-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13594: --- Assignee: Claus Ibsen > camel apt - Avoid generating TypeConverter META-INF file when we generate > TypeConverterLoader > - > > Key: CAMEL-13594 > URL: https://issues.apache.org/jira/browse/CAMEL-13594 > Project: Camel > Issue Type: Improvement > Components: build system >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We can optimize this to only have the newer TypeConverterLoader file which > has all the type converters that are optimized. And then in tooling/apt avoid > generate both TypeConverter and TypeConverterLoaded meta files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13606) Olingo Consumer filtering can cause NPE
[ https://issues.apache.org/jira/browse/CAMEL-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855541#comment-16855541 ] Paul Richardson commented on CAMEL-13606: - PR for both olingo2 & 4 -> https://github.com/apache/camel/pull/2959 > Olingo Consumer filtering can cause NPE > --- > > Key: CAMEL-13606 > URL: https://issues.apache.org/jira/browse/CAMEL-13606 > Project: Camel > Issue Type: Bug > Components: camel-olingo2, camel-olingo4 >Affects Versions: 2.21.5 >Reporter: Paul Richardson >Priority: Major > > When polling with the Olingo*Consumer, the result is intercepted and filtered > (if filtering is switched on). If a key predicate is used as well then, on > subsequent polling iterations, the result is filtered to return null. When > the result is then intercepted and passed to the Olingo*Index for indexing, > the latter fails to handle the null value and causes an NullPointerException. > This exception is reported/logged and polling continues with subsequent > iterations (also blowing up with NPEs). Need to fix the Index classes so they > handle null values correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13608) camel-spring-boot - Add option to include/exclude routes based on their ids
[ https://issues.apache.org/jira/browse/CAMEL-13608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855450#comment-16855450 ] Claus Ibsen commented on CAMEL-13608: - You can also do this with camel-test > camel-spring-boot - Add option to include/exclude routes based on their ids > --- > > Key: CAMEL-13608 > URL: https://issues.apache.org/jira/browse/CAMEL-13608 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > So you can for example do an unit test where you want to only test a specific > route and then filter out everyone else. Currently you can filter on route > builder and xml files level, but not on route ids. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13608) camel-spring-boot - Add option to include/exclude routes based on their ids
[ https://issues.apache.org/jira/browse/CAMEL-13608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13608. - Resolution: Fixed Assignee: Claus Ibsen Fix Version/s: 3.0.0.M4 > camel-spring-boot - Add option to include/exclude routes based on their ids > --- > > Key: CAMEL-13608 > URL: https://issues.apache.org/jira/browse/CAMEL-13608 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > So you can for example do an unit test where you want to only test a specific > route and then filter out everyone else. Currently you can filter on route > builder and xml files level, but not on route ids. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13609) camel-spark: align spark and jackson versions
[ https://issues.apache.org/jira/browse/CAMEL-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16855425#comment-16855425 ] Alex Dettinger commented on CAMEL-13609: Should be shipped with camel-3.0.0-M4 > camel-spark: align spark and jackson versions > - > > Key: CAMEL-13609 > URL: https://issues.apache.org/jira/browse/CAMEL-13609 > Project: Camel > Issue Type: Task > Components: camel-spark >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13609) camel-spark: align spark and jackson versions
[ https://issues.apache.org/jira/browse/CAMEL-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-13609. Resolution: Fixed > camel-spark: align spark and jackson versions > - > > Key: CAMEL-13609 > URL: https://issues.apache.org/jira/browse/CAMEL-13609 > Project: Camel > Issue Type: Task > Components: camel-spark >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13609) camel-spark: align spark and jackson versions
[ https://issues.apache.org/jira/browse/CAMEL-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-13609: -- Assignee: Alex Dettinger > camel-spark: align spark and jackson versions > - > > Key: CAMEL-13609 > URL: https://issues.apache.org/jira/browse/CAMEL-13609 > Project: Camel > Issue Type: Task > Components: camel-spark >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13609) camel-spark: align spark and jackson versions
Alex Dettinger created CAMEL-13609: -- Summary: camel-spark: align spark and jackson versions Key: CAMEL-13609 URL: https://issues.apache.org/jira/browse/CAMEL-13609 Project: Camel Issue Type: Task Components: camel-spark Affects Versions: 3.0.0-M3 Reporter: Alex Dettinger -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13605) Support setup proxy host and port on Telegram
[ https://issues.apache.org/jira/browse/CAMEL-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-13605. -- Resolution: Fixed Merged the patch into master and camel-2.x branch. > Support setup proxy host and port on Telegram > - > > Key: CAMEL-13605 > URL: https://issues.apache.org/jira/browse/CAMEL-13605 > Project: Camel > Issue Type: Improvement > Components: camel-telegram >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.25.0, 3.0.0.M4 > > > As we may run the camel-telegram application behind a proxy, it could be > handy if camel-telegram support setting http proxy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
