[jira] [Resolved] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13953. -- Resolution: Information Provided > The url http://camel.apache.org/schema/blueprint/cxf is

[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925839#comment-16925839 ] Freeman Fang commented on CAMEL-13953: -- Hi [~4535992], I may miss something but the

[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925744#comment-16925744 ] Freeman Fang commented on CAMEL-13953: -- Thanks [~4535992] for the reproducer, I will take a close

[jira] [Comment Edited] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924458#comment-16924458 ] Freeman Fang edited comment on CAMEL-13953 at 9/6/19 5:34 PM: -- Hi

[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924458#comment-16924458 ] Freeman Fang commented on CAMEL-13953: -- Hi [~4535992], Thanks for the update. In your blueprint

[jira] [Assigned] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13953: Assignee: Freeman Fang > The url http://camel.apache.org/schema/blueprint/cxf is down >

[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924344#comment-16924344 ] Freeman Fang commented on CAMEL-13953: -- Yes, camel-cxf always load schema/blueprint/camel-cxf.xsd

[jira] [Commented] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924257#comment-16924257 ] Freeman Fang commented on CAMEL-13953: -- Hi [~4535992], This should be taken care of by Apache

[jira] [Moved] (CAMEL-13953) The url http://camel.apache.org/schema/blueprint/cxf is down

[ https://issues.apache.org/jira/browse/CAMEL-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang moved DOSGI-281 to CAMEL-13953: Key: CAMEL-13953 (was: DOSGI-281) Project: Camel (was: CXF

[jira] [Resolved] (CAMEL-13942) camel-undertow - UnitOfWork should be done after send back response

[ https://issues.apache.org/jira/browse/CAMEL-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13942. -- Resolution: Fixed > camel-undertow - UnitOfWork should be done after send back response >

[jira] [Commented] (CAMEL-13942) camel-undertow - UnitOfWork should be done after send back response

[ https://issues.apache.org/jira/browse/CAMEL-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923297#comment-16923297 ] Freeman Fang commented on CAMEL-13942: -- [~davsclaus], sure, will do > camel-undertow - UnitOfWork

[jira] [Updated] (CAMEL-13942) UnitOfWork should be done after send back response

[ https://issues.apache.org/jira/browse/CAMEL-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13942: - Issue Type: Bug (was: Improvement) > UnitOfWork should be done after send back response >

[jira] [Created] (CAMEL-13942) UnitOfWork should be done after send back response

Freeman Fang created CAMEL-13942: Summary: UnitOfWork should be done after send back response Key: CAMEL-13942 URL: https://issues.apache.org/jira/browse/CAMEL-13942 Project: Camel Issue

[jira] [Assigned] (CAMEL-13942) UnitOfWork should be done after send back response

[ https://issues.apache.org/jira/browse/CAMEL-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13942: Assignee: Freeman Fang > UnitOfWork should be done after send back response >

[jira] [Updated] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault

[ https://issues.apache.org/jira/browse/CAMEL-13898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13898: - Component/s: camel-cxf > ensure camel-cxf consumer can propagate protocol headers from camel

[jira] [Resolved] (CAMEL-13891) camel-cxf - Add spring.schemas for -spring URL so it works for same online url

[ https://issues.apache.org/jira/browse/CAMEL-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13891. -- Resolution: Fixed > camel-cxf - Add spring.schemas for -spring URL so it works for same

[jira] [Resolved] (CAMEL-13876) enable camel-undertow component to set custom HttpHandler

[ https://issues.apache.org/jira/browse/CAMEL-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13876. -- Fix Version/s: 3.0.0.RC1 3.0.0 Resolution: Fixed > enable

[jira] [Resolved] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault

[ https://issues.apache.org/jira/browse/CAMEL-13898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13898. -- Fix Version/s: 3.0.0.RC1 2.25.0 2.24.2

[jira] [Assigned] (CAMEL-13891) camel-cxf - Add spring.schemas for -spring URL so it works for same online url

[ https://issues.apache.org/jira/browse/CAMEL-13891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13891: Assignee: Freeman Fang > camel-cxf - Add spring.schemas for -spring URL so it works for

[jira] [Assigned] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault

[ https://issues.apache.org/jira/browse/CAMEL-13898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13898: Assignee: Freeman Fang > ensure camel-cxf consumer can propagate protocol headers from

[jira] [Created] (CAMEL-13898) ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault

Freeman Fang created CAMEL-13898: Summary: ensure camel-cxf consumer can propagate protocol headers from camel exchange headers when throwing a soap fault Key: CAMEL-13898 URL:

[jira] [Assigned] (CAMEL-13876) enable camel-undertow component to set custom HttpHandler

[ https://issues.apache.org/jira/browse/CAMEL-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13876: Assignee: Freeman Fang > enable camel-undertow component to set custom HttpHandler >

[jira] [Updated] (CAMEL-13876) enable camel-undertow component to set custom HttpHandler

[ https://issues.apache.org/jira/browse/CAMEL-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13876: - Description: such as security related undertow HttpHandlers > enable camel-undertow component

[jira] [Created] (CAMEL-13876) enable camel-undertow component to set custom HttpHandler

Freeman Fang created CAMEL-13876: Summary: enable camel-undertow component to set custom HttpHandler Key: CAMEL-13876 URL: https://issues.apache.org/jira/browse/CAMEL-13876 Project: Camel

[jira] [Resolved] (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:all-tabpanel ] Freeman Fang resolved CAMEL-12957. -- Resolution: Fixed Fix Version/s: 2.25.0 > camel-cxf - Swagger/OpenAPI feature should

[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=16906274#comment-16906274 ] Freeman Fang commented on CAMEL-12957: -- CXF 3.3.3 is out, I will update to use it and close this

[jira] [Resolved] (CAMEL-13424) Rest Component custom routeId is not accessible in processor

[ https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13424. -- Resolution: Fixed Fix Version/s: 3.0.0.M5 2.25.0

[jira] [Commented] (CAMEL-13424) Rest Component custom routeId is not accessible in processor

[ https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884120#comment-16884120 ] Freeman Fang commented on CAMEL-13424: -- test case added in camel code base to ensure it works >

[jira] [Commented] (CAMEL-13724) camel route customized id isn't correct if there are more than one Rest DSL route availble

[ https://issues.apache.org/jira/browse/CAMEL-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882989#comment-16882989 ] Freeman Fang commented on CAMEL-13724: -- No problem [~acosentino]! Another pair of eyes is always

[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=16881259#comment-16881259 ] Freeman Fang commented on CAMEL-12957: -- [~jen...@gmx.net], great! thanks for the feedback, will

[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=16879444#comment-16879444 ] Freeman Fang commented on CAMEL-12957: -- [~jen...@gmx.net], FYI, this is addressed on CXF side,

[jira] [Resolved] (CAMEL-13724) camel route customized id isn't correct if there are more than one Rest DSL route availble

[ https://issues.apache.org/jira/browse/CAMEL-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13724. -- Resolution: Fixed > camel route customized id isn't correct if there are more than one Rest

[jira] [Assigned] (CAMEL-13424) Rest Component custom routeId is not accessible in processor

[ https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13424: Assignee: Freeman Fang > Rest Component custom routeId is not accessible in processor >

[jira] [Commented] (CAMEL-13424) Rest Component custom routeId is not accessible in processor

[ https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879441#comment-16879441 ] Freeman Fang commented on CAMEL-13424: -- I will verify the testcase here > Rest Component custom

[jira] [Commented] (CAMEL-13724) camel route customized id isn't correct if there are more than one Rest DSL route availble

[ https://issues.apache.org/jira/browse/CAMEL-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879259#comment-16879259 ] Freeman Fang commented on CAMEL-13724: -- [~davsclaus], sure, I will do it. Freeman > camel route

[jira] [Updated] (CAMEL-13724) camel route customized id isn't correct if there are more than one Rest DSL route availble

[ https://issues.apache.org/jira/browse/CAMEL-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13724: - Summary: camel route customized id isn't correct if there are more than one Rest DSL route

[jira] [Created] (CAMEL-13724) camel route id isn't correct if there are more than one Rest DSL route availble

Freeman Fang created CAMEL-13724: Summary: camel route id isn't correct if there are more than one Rest DSL route availble Key: CAMEL-13724 URL: https://issues.apache.org/jira/browse/CAMEL-13724

[jira] [Assigned] (CAMEL-13724) camel route id isn't correct if there are more than one Rest DSL route availble

[ https://issues.apache.org/jira/browse/CAMEL-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13724: Assignee: Freeman Fang > camel route id isn't correct if there are more than one Rest

[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=16875192#comment-16875192 ] Freeman Fang commented on CAMEL-12957: -- As for OpenApiFeature(OpenApi V3), created CXF-8064 on CXF

[jira] [Resolved] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.

[ https://issues.apache.org/jira/browse/CAMEL-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13693. -- Resolution: Fixed Fix Version/s: 2.25.0 > avoid

[jira] [Commented] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.

[ https://issues.apache.org/jira/browse/CAMEL-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874888#comment-16874888 ] Freeman Fang commented on CAMEL-13693: -- Hi [~davsclaus], Yes, I believe so, will do it. Freeman

[jira] [Assigned] (CAMEL-13693) avoid useOverridePropertiesWithPropertiesComponent being invoked twice when running a unit-test with OSGI Blueprint XML.

[ https://issues.apache.org/jira/browse/CAMEL-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13693: Assignee: Freeman Fang > avoid useOverridePropertiesWithPropertiesComponent being

[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=16871751#comment-16871751 ] Freeman Fang commented on CAMEL-12957: -- Hi [~jen...@gmx.net], A quick update, you do need to set

[jira] [Updated] (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:all-tabpanel ] Freeman Fang updated CAMEL-12957: - Attachment: camel-openapi-test-swagger2feature.tar > camel-cxf - Swagger/OpenAPI feature should

[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=16871536#comment-16871536 ] Freeman Fang commented on CAMEL-12957: -- Thanks [~jen...@gmx.net]! I will take a close look!

[jira] [Assigned] (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:all-tabpanel ] Freeman Fang reassigned CAMEL-12957: Assignee: Freeman Fang > camel-cxf - Swagger/OpenAPI feature should not involve the

[jira] [Resolved] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13664. -- Resolution: Fixed > OSGi tests broken for both JDK8 and JDK11 >

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871479#comment-16871479 ] Freeman Fang commented on CAMEL-13664: -- 24b7cf6090aa6c4476bc2265385aa21bd5ca02d4 add the previous

[jira] [Reopened] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reopened CAMEL-13664: -- [~davsclaus], I will take a close look. > OSGi tests broken for both JDK8 and JDK11 >

[jira] [Resolved] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13664. -- Resolution: Fixed > OSGi tests broken for both JDK8 and JDK11 >

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870262#comment-16870262 ] Freeman Fang commented on CAMEL-13664: -- Thanks [~davsclaus]! > OSGi tests broken for both JDK8 and

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869844#comment-16869844 ] Freeman Fang commented on CAMEL-13664: -- Hi [~davsclaus], Indeed, the

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869472#comment-16869472 ] Freeman Fang commented on CAMEL-13664: -- Hi [~davsclaus], CamelGroovyTest is fixed by setting

[jira] [Comment Edited] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868899#comment-16868899 ] Freeman Fang edited comment on CAMEL-13664 at 6/20/19 8:09 PM: --- OK, the

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868899#comment-16868899 ] Freeman Fang commented on CAMEL-13664: -- OK, the thing is that any blueprint bundle(like drop a

[jira] [Commented] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868891#comment-16868891 ] Freeman Fang commented on CAMEL-13664: -- If I deploy the blueprint file used in CamelGroovyTest in

[jira] [Commented] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x

[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867660#comment-16867660 ] Freeman Fang commented on CAMEL-13660: -- [~acosentino], Yes, only

[jira] [Moved] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang moved CXF-8058 to CAMEL-13664: --- Workflow: classic default workflow (was: Default workflow, editable Closed

[jira] [Assigned] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13664: Assignee: Freeman Fang > OSGi tests broken for both JDK8 and JDK11 >

[jira] [Updated] (CAMEL-13664) OSGi tests broken for both JDK8 and JDK11

[ https://issues.apache.org/jira/browse/CAMEL-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13664: - Fix Version/s: 3.0.0 Component/s: osgi > OSGi tests broken for both JDK8 and JDK11 >

[jira] [Commented] (CAMEL-13660) xml-specs - Can we upgrade stax2-api from 3.x to 4.x

[ https://issues.apache.org/jira/browse/CAMEL-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866809#comment-16866809 ] Freeman Fang commented on CAMEL-13660: -- In OSGi if we upgrade to stax2 4.x, we also should upgrade

[jira] [Resolved] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter

[ https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-12975. -- Resolution: Fixed Fix Version/s: 2.25.0 2.24.1

[jira] [Updated] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter

[ https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-12975: - Fix Version/s: (was: 3.0.0) > WARN: No CamelContext defined yet so cannot inject into bean:

[jira] [Assigned] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter

[ https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-12975: Assignee: Freeman Fang > WARN: No CamelContext defined yet so cannot inject into bean:

[jira] [Comment Edited] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter

[ https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865807#comment-16865807 ] Freeman Fang edited comment on CAMEL-12975 at 6/17/19 5:33 PM: --- I think we

[jira] [Commented] (CAMEL-12975) WARN: No CamelContext defined yet so cannot inject into bean: org.apache.camel.converter.jaxb.FallbackTypeConverter

[ https://issues.apache.org/jira/browse/CAMEL-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865807#comment-16865807 ] Freeman Fang commented on CAMEL-12975: -- I think we also need to add

[jira] [Resolved] (CAMEL-13038) Type Convert Problem for XQuery Build In founction

[ https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13038. -- Resolution: Information Provided > Type Convert Problem for XQuery Build In founction >

[jira] [Commented] (CAMEL-13038) Type Convert Problem for XQuery Build In founction

[ https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864405#comment-16864405 ] Freeman Fang commented on CAMEL-13038: -- I'd like to close this one for now. > Type Convert

[jira] [Resolved] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint

[ https://issues.apache.org/jira/browse/CAMEL-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13637. -- Resolution: Fixed > be able to enable access log for camel-undertow consumer endpoint >

[jira] [Commented] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint

[ https://issues.apache.org/jira/browse/CAMEL-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864404#comment-16864404 ] Freeman Fang commented on CAMEL-13637: -- Hi [~bedla], Yup, the AccessLogReceiver is pluggable.

[jira] [Assigned] (CAMEL-13644) CxfConsumer - Should not create server in constructor

[ https://issues.apache.org/jira/browse/CAMEL-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13644: Assignee: Freeman Fang > CxfConsumer - Should not create server in constructor >

[jira] [Commented] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint

[ https://issues.apache.org/jira/browse/CAMEL-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862136#comment-16862136 ] Freeman Fang commented on CAMEL-13637: -- an access log entry for one request looks like "2019-06-12

[jira] [Created] (CAMEL-13637) be able to enable access log for camel-undertow consumer endpoint

Freeman Fang created CAMEL-13637: Summary: be able to enable access log for camel-undertow consumer endpoint Key: CAMEL-13637 URL: https://issues.apache.org/jira/browse/CAMEL-13637 Project: Camel

[jira] [Commented] (CAMEL-13038) Type Convert Problem for XQuery Build In founction

[ https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861364#comment-16861364 ] Freeman Fang commented on CAMEL-13038: -- Hi [~W.Y], I think in your testcase, in the

[jira] [Resolved] (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 resolved CAMEL-9103. - Resolution: Information Provided > camel-cxf does not handle soapfaults with ws-addressing

[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

[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

[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:

[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

[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

[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:

[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

[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

[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

[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

[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

[jira] [Commented] (CAMEL-13607) camel-mail-starter - com.sun.mail:javax.mail:jar is not in dependency

[ https://issues.apache.org/jira/browse/CAMEL-13607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854740#comment-16854740 ] Freeman Fang commented on CAMEL-13607: -- sorry I broke it in the first place :P >

[jira] [Resolved] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13560. -- Resolution: Fixed > Mail component is not reading attachments in OSGi >

[jira] [Commented] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853049#comment-16853049 ] Freeman Fang commented on CAMEL-13560: -- [~eximius] FYI, this is fixed by KARAF-6299 Cheers Freeman

[jira] [Commented] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852021#comment-16852021 ] Freeman Fang commented on CAMEL-13560: -- Hi [~eximius], I figured out the problem under the hood.

[jira] [Assigned] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13560: Assignee: Freeman Fang > Mail component is not reading attachments in OSGi >

[jira] [Commented] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850120#comment-16850120 ] Freeman Fang commented on CAMEL-13560: -- [~eximius], thanks! I will take a look Freeman > Mail

[jira] [Commented] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850098#comment-16850098 ] Freeman Fang commented on CAMEL-13560: -- Thanks [~eximius]! Could you please put all in a project

[jira] [Resolved] (CAMEL-13593) avoid “expected resource not found” warnings when using camel-mail in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13593. -- Resolution: Fixed Fix Version/s: 2.25.0 2.24.1

[jira] [Commented] (CAMEL-13560) Mail component is not reading attachments in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849914#comment-16849914 ] Freeman Fang commented on CAMEL-13560: -- Hi [~eximius], If you can append a test application bundle

[jira] [Updated] (CAMEL-13593) avoid “expected resource not found” warnings when using camel-mail in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang updated CAMEL-13593: - Description: In javax.mail API(1.6), it(javax.mail.Session) will use authenticator's

[jira] [Assigned] (CAMEL-13593) avoid “expected resource not found” warnings when using camel-mail in OSGi

[ https://issues.apache.org/jira/browse/CAMEL-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-13593: Assignee: Freeman Fang > avoid “expected resource not found” warnings when using

[jira] [Created] (CAMEL-13593) avoid “expected resource not found” warnings when using camel-mail in OSGi

Freeman Fang created CAMEL-13593: Summary: avoid “expected resource not found” warnings when using camel-mail in OSGi Key: CAMEL-13593 URL: https://issues.apache.org/jira/browse/CAMEL-13593 Project:

[jira] [Resolved] (CAMEL-13376) camel-cxf - failure processor for custom exception handling cannot get the original message

[ https://issues.apache.org/jira/browse/CAMEL-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-13376. -- Resolution: Fixed Fix Version/s: 2.25.0 2.24.1

[jira] [Commented] (CAMEL-13376) camel-cxf - failure processor for custom exception handling cannot get the original message

[ https://issues.apache.org/jira/browse/CAMEL-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849092#comment-16849092 ] Freeman Fang commented on CAMEL-13376: -- We need to set the body back to original CxfPayload with

  1   2   3   >