[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 down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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
src/main/resources/OSGI-INF/blueprint/blueprint.xml
in your test case seems messy for me.
1. There's several places use ref component-id="" but can't find where you
define the bean in ref
{code}
{code}
2. You have lots of Import-Package such as commons package with different
versions but I don't see where those packages comes from your test code(they
may be necessary for your real project but normally in Karaf the best practice
is to use a feature.xml to define all bundles you need, I don't see this
features.xml in your reproducer, nor in your README)
3. Plus I think most namespace in your blueprint.xml are not necessary.
Since we are talking about a Red Hat FUSE kit, I don't think community JIRA is
the appropriate place to discuss it. So please use your FUSE support channel to
get in touch with us.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 look.
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
> REPRODUCER PROJECT : https://github.com/p4535992/bug-load-namespace-blueprint
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 [~4535992],
Thanks for the update.
In your blueprint do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features. And for
namespace like
http://camel.apache.org/schema/cxf/camel-cxf-blueprint
I don't think this is correct, does it work previously?
Anyway, could you please append a reproducer project? A reproducer absolutely
can help speed up the process to address this issue. If you are the Red Hat
Fuse customer, you can use that channel to put your reproducer.
Thanks!
Freeman
was (Author: ffang):
Hi [~4535992],
Thanks for the update.
In your blueprint do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features.
Could you please append a reproducer project? A reproducer absolutely can help
speed up the process to address this issue. If you are the Red Hat Fuse
customer, you can use that channel to put your reproducer.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 do you really need to use so many xsds? Like undertow and
security related xsds you definitely need to install more features.
Could you please append a reproducer project? A reproducer absolutely can help
speed up the process to address this issue. If you are the Red Hat Fuse
customer, you can use that channel to put your reproducer.
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Assignee: Freeman Fang
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 from camel-cxf bundle.
[~4535992]
Any chance you can append a reproducer project?
Thanks!
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 Camel community so I move this to Camel
jira.
Freeman
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 Distributed OSGi)
> The url http://camel.apache.org/schema/blueprint/cxf is down
>
>
> Key: CAMEL-13953
> URL: https://issues.apache.org/jira/browse/CAMEL-13953
> Project: Camel
> Issue Type: Bug
>Reporter: Marco Tenti
>Priority: Critical
>
> My bundle OSGI remains in "grace period" because of this error
> {code}
> is waiting for namespace handlers [http://cxf.apache.org/blueprint/core,
> http://cxf.apache.org/transports/http/configuration,
> http://camel.apache.org/schema/cxf/camel-cxf-blueprint,
> http://cxf.apache.org/configuration/security,
> http://camel.apache.org/schema/blueprint,
> http://cxf.apache.org/transports/http-undertow/configuration,
> [http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0]
> {code}
> it' seem some url is down in the specific the url
> http://camel.apache.org/schema/blueprint/cxf
> is a couple of days is not reachable and give me error code 404 "Page not
> found".
> Is down for a error or the XSD is migrate to another url?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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 > --- > > Key: CAMEL-13942 > URL: https://issues.apache.org/jira/browse/CAMEL-13942 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2 > > > since done UoW will close the CachedStream and delete the temp file used by > the CachedStream on the Camel Exchange, done UoW too early will cause error > when process the response message which still reply on the CachedStream -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 should be done after send back response > --- > > Key: CAMEL-13942 > URL: https://issues.apache.org/jira/browse/CAMEL-13942 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC2 > > > since done UoW will close the CachedStream and delete the temp file used by > the CachedStream on the Camel Exchange, done UoW too early will cause error > when process the response message which still reply on the CachedStream -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 > -- > > Key: CAMEL-13942 > URL: https://issues.apache.org/jira/browse/CAMEL-13942 > Project: Camel > Issue Type: Bug > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > since done UoW will close the CachedStream and delete the temp file used by > the CachedStream on the Camel Exchange, done UoW too early will cause error > when process the response message which still reply on the CachedStream -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 Type: Improvement Components: camel-undertow Reporter: Freeman Fang since done UoW will close the CachedStream and delete the temp file used by the CachedStream on the Camel Exchange, done UoW too early will cause error when process the response message which still reply on the CachedStream -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 > -- > > Key: CAMEL-13942 > URL: https://issues.apache.org/jira/browse/CAMEL-13942 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > since done UoW will close the CachedStream and delete the temp file used by > the CachedStream on the Camel Exchange, done UoW too early will cause error > when process the response message which still reply on the CachedStream -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 exchange > headers when throwing a soap fault > --- > > Key: CAMEL-13898 > URL: https://issues.apache.org/jira/browse/CAMEL-13898 > Project: Camel > Issue Type: New Feature > Components: camel-cxf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC1 > > > to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 online url > -- > > Key: CAMEL-13891 > URL: https://issues.apache.org/jira/browse/CAMEL-13891 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resources/META-INF/spring.schemas > Should have 2x for each pair > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3.xsd=schema/cxfEndpoint.xsd > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3-spring.xsd=schema/cxfEndpoint.xsd > For all of them, as then we have for old and new locations (eg when we had > blueprint later) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 camel-undertow component to set custom HttpHandler > - > > Key: CAMEL-13876 > URL: https://issues.apache.org/jira/browse/CAMEL-13876 > Project: Camel > Issue Type: New Feature > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > such as security related undertow HttpHandlers -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 2.23.4 3.0.0 Resolution: Fixed > ensure camel-cxf consumer can propagate protocol headers from camel exchange > headers when throwing a soap fault > --- > > Key: CAMEL-13898 > URL: https://issues.apache.org/jira/browse/CAMEL-13898 > Project: Camel > Issue Type: New Feature >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.RC1 > > > to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 same online url > -- > > Key: CAMEL-13891 > URL: https://issues.apache.org/jira/browse/CAMEL-13891 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Claus Ibsen >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.RC1 > > > https://github.com/apache/camel/blob/master/components/camel-cxf/src/main/resources/META-INF/spring.schemas > Should have 2x for each pair > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3.xsd=schema/cxfEndpoint.xsd > http\://camel.apache.org/schema/cxf/camel-cxf-3.0.0-M3-spring.xsd=schema/cxfEndpoint.xsd > For all of them, as then we have for old and new locations (eg when we had > blueprint later) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 camel exchange > headers when throwing a soap fault > --- > > Key: CAMEL-13898 > URL: https://issues.apache.org/jira/browse/CAMEL-13898 > Project: Camel > Issue Type: New Feature >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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: https://issues.apache.org/jira/browse/CAMEL-13898 Project: Camel Issue Type: New Feature Reporter: Freeman Fang to keep the same behavior as normal soap response -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 > - > > Key: CAMEL-13876 > URL: https://issues.apache.org/jira/browse/CAMEL-13876 > Project: Camel > Issue Type: New Feature > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > such as security related undertow HttpHandlers -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 to set custom HttpHandler > - > > Key: CAMEL-13876 > URL: https://issues.apache.org/jira/browse/CAMEL-13876 > Project: Camel > Issue Type: New Feature > Components: camel-undertow >Reporter: Freeman Fang >Priority: Major > > such as security related undertow HttpHandlers -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 Issue Type: New Feature Components: camel-undertow Reporter: Freeman Fang -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 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 >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.0.0, 2.25.0 > > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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.14#76016)
[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 issue > 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 >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.0.0 > > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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.14#76016)
[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
2.24.2
2.23.4
3.0.0
> Rest Component custom routeId is not accessible in processor
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M5
>
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[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
> Rest Component custom routeId is not accessible in processor
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[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 great!
I did run the tests in camel-restlet when committing and I did it again this
morning, all passed.
Cheers
Freeman
> camel route customized 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
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.23.3, 2.24.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M4
>
>
> If rest dsl routes have their own customer ids, the id would be ignored,
> hence generate invalid swagger operation Id
> the testcase here can expose this problem
> {code}
> ---
> a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> +++
> b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> @@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> public void configure() throws Exception {
> from("direct:start1?timeout=3").to("mock:result");
> from("direct:start2").to("mock:result");
> -
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
> +
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
> +
> .get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
> }
> };
> }
> @@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> @Test
> public void testSayHelloBar() {
> assertEquals("getSayHelloBar",
> context.getRouteDefinitions().get(2).getId());
> +assertEquals("getSayHelloBarWithUser",
> context.getRouteDefinitions().get(3).getId());
> }
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[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 mark this issue as "resolved" once we upgrade new cxf version contains the fix > 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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] [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, could you test with lastest CXF snapshot with your testcase? 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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-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 DSL
> route availble
> --
>
> Key: CAMEL-13724
> URL: https://issues.apache.org/jira/browse/CAMEL-13724
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.23.3, 2.24.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M4
>
>
> If rest dsl routes have their own customer ids, the id would be ignored,
> hence generate invalid swagger operation Id
> the testcase here can expose this problem
> {code}
> ---
> a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> +++
> b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> @@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> public void configure() throws Exception {
> from("direct:start1?timeout=3").to("mock:result");
> from("direct:start2").to("mock:result");
> -
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
> +
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
> +
> .get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
> }
> };
> }
> @@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> @Test
> public void testSayHelloBar() {
> assertEquals("getSayHelloBar",
> context.getRouteDefinitions().get(2).getId());
> +assertEquals("getSayHelloBarWithUser",
> context.getRouteDefinitions().get(3).getId());
> }
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 routeId is not accessible in processor
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 customized 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
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.23.3, 2.24.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M4
>
>
> If rest dsl routes have their own customer ids, the id would be ignored,
> hence generate invalid swagger operation Id
> the testcase here can expose this problem
> {code}
> ---
> a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> +++
> b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> @@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> public void configure() throws Exception {
> from("direct:start1?timeout=3").to("mock:result");
> from("direct:start2").to("mock:result");
> -
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
> +
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
> +
> .get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
> }
> };
> }
> @@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> @Test
> public void testSayHelloBar() {
> assertEquals("getSayHelloBar",
> context.getRouteDefinitions().get(2).getId());
> +assertEquals("getSayHelloBarWithUser",
> context.getRouteDefinitions().get(3).getId());
> }
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 availble (was: camel route id isn't correct if there are more
than one Rest DSL route availble)
> camel route customized 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
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.23.3, 2.24.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> If rest dsl routes have their own customer ids, the id would be ignored,
> hence generate invalid swagger operation Id
> the testcase here can expose this problem
> {code}
> ---
> a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> +++
> b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> @@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> public void configure() throws Exception {
> from("direct:start1?timeout=3").to("mock:result");
> from("direct:start2").to("mock:result");
> -
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
> +
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
> +
> .get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
> }
> };
> }
> @@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> @Test
> public void testSayHelloBar() {
> assertEquals("getSayHelloBar",
> context.getRouteDefinitions().get(2).getId());
> +assertEquals("getSayHelloBarWithUser",
> context.getRouteDefinitions().get(3).getId());
> }
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
Project: Camel
Issue Type: Bug
Affects Versions: 2.24.1, 2.23.3
Reporter: Freeman Fang
If rest dsl routes have their own customer ids, the id would be ignored, hence
generate invalid swagger operation Id
the testcase here can expose this problem
{code}
---
a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
+++
b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
@@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
ContextTestSupport {
public void configure() throws Exception {
from("direct:start1?timeout=3").to("mock:result");
from("direct:start2").to("mock:result");
-
rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
+
rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
+
.get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
}
};
}
@@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
ContextTestSupport {
@Test
public void testSayHelloBar() {
assertEquals("getSayHelloBar",
context.getRouteDefinitions().get(2).getId());
+assertEquals("getSayHelloBarWithUser",
context.getRouteDefinitions().get(3).getId());
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 DSL route
> availble
> ---
>
> Key: CAMEL-13724
> URL: https://issues.apache.org/jira/browse/CAMEL-13724
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.23.3, 2.24.1
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> If rest dsl routes have their own customer ids, the id would be ignored,
> hence generate invalid swagger operation Id
> the testcase here can expose this problem
> {code}
> ---
> a/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> +++
> b/core/camel-core/src/test/java/org/apache/camel/impl/RouteIdRestDefinitionTest.java
> @@ -39,7 +39,8 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> public void configure() throws Exception {
> from("direct:start1?timeout=3").to("mock:result");
> from("direct:start2").to("mock:result");
> -
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result");
> +
> rest("/say/hello").get("/bar").id("getSayHelloBar").to("mock:result")
> +
> .get("/bar/{user}").id("getSayHelloBarWithUser").to("mock:result");
> }
> };
> }
> @@ -47,6 +48,7 @@ public class RouteIdRestDefinitionTest extends
> ContextTestSupport {
> @Test
> public void testSayHelloBar() {
> assertEquals("getSayHelloBar",
> context.getRouteDefinitions().get(2).getId());
> +assertEquals("getSayHelloBarWithUser",
> context.getRouteDefinitions().get(3).getId());
> }
>
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 side to address this issue > 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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-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 useOverridePropertiesWithPropertiesComponent being invoked twice when
> running a unit-test with OSGI Blueprint XML.
>
>
> Key: CAMEL-13693
> URL: https://issues.apache.org/jira/browse/CAMEL-13693
> Project: Camel
> Issue Type: Test
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
>
> One from
> {code}
> at
> camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
> {code}
> one from
> {code}
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
> avoid useOverridePropertiesWithPropertiesComponent being invoked twice when
> running a unit-test with OSGI Blueprint XML.
>
>
> Key: CAMEL-13693
> URL: https://issues.apache.org/jira/browse/CAMEL-13693
> Project: Camel
> Issue Type: Test
> Components: camel-blueprint, camel-test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> One from
> {code}
> at
> camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
> {code}
> one from
> {code}
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 invoked twice when
> running a unit-test with OSGI Blueprint XML.
>
>
> Key: CAMEL-13693
> URL: https://issues.apache.org/jira/browse/CAMEL-13693
> Project: Camel
> Issue Type: Test
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> One from
> {code}
> at
> camelinaction.BlueprintFirstTest.useOverridePropertiesWithPropertiesComponent(BlueprintFirstTest.java:56)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createBundleContext(CamelBlueprintTestSupport.java:132)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:248)
> {code}
> one from
> {code}
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:368)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:281)
> at
> org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 "runAsFilter" as true, this is by design to avoid swagger request run into the camel router. And I can confirm that this way Swagger2Feature works, please see attached camel-openapi-test-swagger2feature.tar, you can access http://localhost:8080/api-docs?url=/swagger.json (to get the swagger UI render) or http://localhost:8080/swagger.json (to get the raw swagger payload). I'm still checking the OpenApiFeature(OpenApi V3), to see it's just a configuration problem or we do need some work in cxf OpenApiFeature to make it work with camel-cxfrs. Cheers 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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] [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 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test-swagger2feature.tar, > camel-openapi-test.zip > > > 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] [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! 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test.zip > > > 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] [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 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 >Assignee: Freeman Fang >Priority: Minor > Attachments: camel-openapi-test.zip > > > 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-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 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 default BundleTypeConverterLoader as fallback fixed the broken test, sorry about it. > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 CamelJacksonFallbackConverterTest failure is caused by the auto-generated TypeConverterLoader. However, I found that in OSGi bundle, the TypeConverterLoader will never be used, that's why can't find the expected TypeConverter. I have a a quick fix, to ensure I did it right, I will send a PR for review soon. Cheers Freeman > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 "DynamicImport-Package", but I'm still looking at CamelJacksonFallbackConverterTest, this test only fail on master branch, somehow can't find the JacksonConverter in OSGi. Cheers Freeman > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 thing is that any blueprint bundle(like drop a blueprint file in karaf
deploy folder, a bundle based on this blueprint file will be generated on the
fly, with some OSGi headers added automatically) in Karaf will be added
"DynamicImport-Package =
*", but it's not this case in OSGi test of camel, this is the problem,
it can't reflect exactly the same behavior as it should be in real Karaf
container.
We should do the change like this
{code}
---
a/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
+++
b/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
@@ -121,7 +121,8 @@ public abstract class AbstractFeatureTest {
bundle.set("Manifest-Version", "2")
.set("Bundle-ManifestVersion", "2")
.set("Bundle-SymbolicName", name)
-.set("Bundle-Version", "1.0.0");
+.set("Bundle-Version", "1.0.0")
+.set("DynamicImport-Package", "*");
{code}
in installBlueprintAsBundle method
was (Author: ffang):
OK, the thing is that any blueprint bundle(like drop a blueprint file in karaf
deploy folder, a bundle based on this blueprint file will be generated on the
fly, with some OSGi headers added automatically) in Karaf will be added
"DynamicImport-Package =
*", but it's not this case in OSGi test of camel, this is the problem,
it can't reflect exactly the same behavior as it should be in real Karaf
container.
We should do the change like this
{code}
---
a/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
+++
b/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
@@ -121,7 +121,8 @@ public abstract class AbstractFeatureTest {
bundle.set("Manifest-Version", "2")
.set("Bundle-ManifestVersion", "2")
.set("Bundle-SymbolicName", name)
-.set("Bundle-Version", "1.0.0");
+.set("Bundle-Version", "1.0.0")
+.set("DynamicImport-Package", "*");
{code}
> OSGi tests broken for both JDK8 and JDK11
> -
>
> Key: CAMEL-13664
> URL: https://issues.apache.org/jira/browse/CAMEL-13664
> Project: Camel
> Issue Type: Test
> Components: osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> [ERROR] Errors:
> [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer
> [testCamelGroovy(org...
> [ERROR] CamelJacksonFallbackConverterTest.test:56 »
> NoTypeConversionAvailable No type ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 blueprint file in karaf
deploy folder, a bundle based on this blueprint file will be generated on the
fly, with some OSGi headers added automatically) in Karaf will be added
"DynamicImport-Package =
*", but it's not this case in OSGi test of camel, this is the problem,
it can't reflect exactly the same behavior as it should be in real Karaf
container.
We should do the change like this
{code}
---
a/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
+++
b/components/camel-test-karaf/src/main/java/org/apache/camel/test/karaf/AbstractFeatureTest.java
@@ -121,7 +121,8 @@ public abstract class AbstractFeatureTest {
bundle.set("Manifest-Version", "2")
.set("Bundle-ManifestVersion", "2")
.set("Bundle-SymbolicName", name)
-.set("Bundle-Version", "1.0.0");
+.set("Bundle-Version", "1.0.0")
+.set("DynamicImport-Package", "*");
{code}
> OSGi tests broken for both JDK8 and JDK11
> -
>
> Key: CAMEL-13664
> URL: https://issues.apache.org/jira/browse/CAMEL-13664
> Project: Camel
> Issue Type: Test
> Components: osgi
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> [ERROR] Errors:
> [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer
> [testCamelGroovy(org...
> [ERROR] CamelJacksonFallbackConverterTest.test:56 »
> NoTypeConversionAvailable No type ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 Karaf, it works. > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 mvn:com.fasterxml.woodstox/woodstox-core/ should be upgraded to 5.2.1 and needn't touch mvn:org.codehaus.woodstox/woodstox-core-asl, seems already this case. Freeman > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 status) Key: CAMEL-13664 (was: CXF-8058) Project: Camel (was: CXF) > OSGi tests broken for both JDK8 and JDK11 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test >Reporter: Freeman Fang >Priority: Major > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 > - > > Key: CAMEL-13664 > URL: https://issues.apache.org/jira/browse/CAMEL-13664 > Project: Camel > Issue Type: Test > Components: osgi >Reporter: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > [ERROR] Errors: > [ERROR] CamelGroovyTest.testCamelGroovy:48 » WrappedTestContainer > [testCamelGroovy(org... > [ERROR] CamelJacksonFallbackConverterTest.test:56 » > NoTypeConversionAvailable No type ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 to woodstox-core 5.x > xml-specs - Can we upgrade stax2-api from 3.x to 4.x > > > Key: CAMEL-13660 > URL: https://issues.apache.org/jira/browse/CAMEL-13660 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > > I wonder if we can upgrade to use the v4 of stax2-api's? The camel-stax > component now uses that, but the xml-specs feature is using the old v3 from > 2014 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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
2.23.3
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Assignee: Freeman Fang
>Priority: Minor
> Fix For: 2.23.3, 2.24.1, 2.25.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Assignee: Freeman Fang
>Priority: Minor
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 also need to add org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter(for camel 2.x) to get
rid of the WARN message.
Btw, it's not a problem anymore for Camel 3.x since FallbackTypeConverter isn't
CamelContextAware anymore.
was (Author: ffang):
I think we also need to add org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter to get rid of the WARN
message
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
> Fix For: 3.0.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 org.apache.camel.DeferredContextBinding annotation
to org.apache.camel.converter.jaxb.FallbackTypeConverter to get rid of the WARN
message
> WARN: No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter
> ---
>
> Key: CAMEL-12975
> URL: https://issues.apache.org/jira/browse/CAMEL-12975
> Project: Camel
> Issue Type: Bug
> Components: camel-jaxb, camel-spring-boot-starters
>Affects Versions: 2.23.0, 2.24.0
>Reporter: Pascal Schumacher
>Priority: Minor
> Fix For: 3.0.0
>
>
> I'm using camel-jaxb-starter 2.23.0 in combination with Spring Boot 2.1.1.
> During start-up this warning is displayed:
> {{WARN 15204 --- [ main] o.a.c.i.DefaultCamelBeanPostProcessor:
> No CamelContext defined yet so cannot inject into bean:
> org.apache.camel.converter.jaxb.FallbackTypeConverter}}
> Otherwise everything is working fine (as far as I can tell).
> I created a minimal project that allows reproducing this warning:
> https://github.com/PascalSchumacher/CamelJaxbStartupWarning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Minor
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
>
[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 Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Minor
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
>
[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 > - > > Key: CAMEL-13637 > URL: https://issues.apache.org/jira/browse/CAMEL-13637 > Project: Camel > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > add a option/flag so we can configure camel-undertow consumer endpoint to > enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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. Cheers Freeman > 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 > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > add a option/flag so we can configure camel-undertow consumer endpoint to > enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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
> -
>
> Key: CAMEL-13644
> URL: https://issues.apache.org/jira/browse/CAMEL-13644
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
>Reporter: Claus Ibsen
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
>
> public CxfConsumer(final CxfEndpoint endpoint, Processor processor)
> throws Exception {
> super(endpoint, processor);
> cxfEndpoint = endpoint;
> server = createServer();
> }
> The create server should just be removed as its done in doStart where we
> create resources etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 10:07:54,919 [XNIO-18 task-1 ] INFO accesslog - 127.0.0.1 - - [12/Jun/2019:10:07:54 -0400] "POST /foo HTTP/1.1" 200 4" > 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 > Issue Type: Improvement > Components: camel-undertow >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0 > > > add a option/flag so we can configure camel-undertow consumer endpoint to > enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 Issue Type: Improvement Components: camel-undertow Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 3.0.0 add a option/flag so we can configure camel-undertow consumer endpoint to enable access log per each request -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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
src/main/resources/xquerytemplate/xqueryfile.xq
you should simply use
{code}
declare variable $in.body as xs:string external;
let $codetableRequest :=parse-xml($in.body)/*
{code}
instead of
{code}
declare variable $in.body as element() external;
let $codetableRequest :=$in.body
{code}
It works for me with this change.
Cheers
Freeman
> Type Convert Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Major
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
>
[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 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-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] [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-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] [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 > camel-mail-starter - com.sun.mail:javax.mail:jar is not in dependency > - > > Key: CAMEL-13607 > URL: https://issues.apache.org/jira/browse/CAMEL-13607 > Project: Camel > Issue Type: Task > Components: camel-mail >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Freeman Fang >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > For some weird issues then camel-mail-starter JAR does not include javax mail > JAR and then it cannot compile, on my local system > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile > (default-compile) on project camel-mail-starter: Compilation failure: > Compilation failure: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
> Attachments: karaf.mail.issue.zip
>
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received: from
[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
> Mail component is not reading attachments in OSGi
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
> Attachments: karaf.mail.issue.zip
>
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
>
[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.
This is caused by when using jdk9/jdk11, it exposes a javax.activation version
which isn't OSGi compatible.
So far you can edit $KARAF_HOME/etc/jre.properties
remove
{code}
javax.activation;version="1.2", \
{code}
from jre-9(jre-11 also use it) property, then it should work for you.
And I will fix it for next Karaf release.
Cheers
Freeman
> Mail component is not reading attachments in OSGi
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
> Attachments: karaf.mail.issue.zip
>
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
>
[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
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Assignee: Freeman Fang
>Priority: Minor
> Attachments: karaf.mail.issue.zip
>
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
> Return-Path:
> Received:
[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 component is not reading attachments in OSGi
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
> Attachments: karaf.mail.issue.zip
>
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019 07:13:59 -0700 (PDT)
>
[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 with pom.xml so that I can build and
deploy? That's more handy.
> Mail component is not reading attachments in OSGi
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id w23mr27342169lfe.73.1558534439904;
> Wed, 22 May 2019
[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
2.22.5
2.23.3
3.0.0
> 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: Camel
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.3, 2.22.5, 2.24.1, 2.25.0
>
>
> In javax.mail API(1.6), it(javax.mail.Session) will use authenticator's
> classloader to load two default files
> {code}
> META-INF/javamail.default.address.map
> META-INF/javamail.default.providers
> {code}
> Since camel-mail provider a DefaultAuthenticator, which means javax mail api
> will try to use camel-mail bundle classloader in OSGi to load above default
> files. Those files aren't available for camel-mail bundle classloader, so we
> see warning message as
> {code}
> 2019-04-25 12:42:09,806 | WARN | 23 - scheduler://foo | j.mail | 21 -
> com.sun.mail.javax.mail - 1.6.1 | expected resource not found:
> /META-INF/javamail.default.providers
> 2019-04-25 12:42:09,807 | WARN | 23 - scheduler://foo | j.mail | 21 -
> com.sun.mail.javax.mail - 1.6.1| expected resource not found:
> /META-INF/javamail.default.address.map
> {code}
> This warning message isn't harmful but annoying. The javax.mail.Session will
> always add default stuff by code if can't find the default configuration file
> {code}
>if (providers.size() == 0) {
> logger.config("failed to load any providers, using defaults");
> // failed to load any providers, initialize with our defaults
> addProvider(new Provider(Provider.Type.STORE,
> "imap", "com.sun.mail.imap.IMAPStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "imaps", "com.sun.mail.imap.IMAPSSLStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "pop3", "com.sun.mail.pop3.POP3Store",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "pop3s", "com.sun.mail.pop3.POP3SSLStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.TRANSPORT,
> "smtp", "com.sun.mail.smtp.SMTPTransport",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.TRANSPORT,
> "smtps", "com.sun.mail.smtp.SMTPSSLTransport",
> "Oracle", Version.version));
> }
>if (addressMap.isEmpty()) {
> logger.config("failed to load address map, using defaults");
> addressMap.put("rfc822", "smtp");
> }
> {code}
> But it's better we can avoid such WARN message when using camel-mail in OSGi
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 which I can build and deploy into
Karaf, I can take a close look at this JDK11 issue with Karaf.
Thanks!
Freeman
> Mail component is not reading attachments in OSGi
> -
>
> Key: CAMEL-13560
> URL: https://issues.apache.org/jira/browse/CAMEL-13560
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Minor
>
> I have such route (taken from
> [documentation|https://camel.apache.org/mail.html]):
> {code:java}
> @Override
> public void configure() throws Exception {
> from("imaps://login@host:993?password=pass=true")
> .process(new Processor() {
> @Override
> public void process(final Exchange exchange) throws Exception {
> final Message in = exchange.getIn();
>
> Map attachments = in.getAttachments();
> System.out.println("ATTACHMENTS: "+attachments.size());
> }
> });
> }
> {code}
> When I sent email with images.jpg attachment, email is read, but attachment
> Map is empty.
> Debug shows:
> {code:java}
> DEBUG: setDebug: JavaMail version 1.6.1
> DEBUG: getProvider() returning
> javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Oracle,1.6.1]
> DEBUG IMAPS: mail.imap.fetchsize: 16384
> DEBUG IMAPS: mail.imap.ignorebodystructuresize: false
> DEBUG IMAPS: mail.imap.statuscachetimeout: 1000
> DEBUG IMAPS: mail.imap.appendbuffersize: -1
> DEBUG IMAPS: mail.imap.minidletime: 10
> DEBUG IMAPS: closeFoldersOnStoreFailure
> DEBUG IMAPS: trying to connect to host "XX.com", port 993, isSSL true
> * OK IMAP4 ready
> A0 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST IDLE MOVE
> XAOL-MOVE AUTH=PLAIN
> A0 OK completed
> DEBUG IMAPS: AUTH: PLAIN
> DEBUG IMAPS: protocolConnect login, host=XX.com, user=XXX,
> password=
> DEBUG IMAPS: AUTHENTICATE PLAIN command trace suppressed
> DEBUG IMAPS: AUTHENTICATE PLAIN command result: A1 OK Login completed
> A2 CAPABILITY
> * CAPABILITY IMAP4rev1 UIDPLUS LITERAL+ CHILDREN NAMESPACE XLIST ID IDLE MOVE
> XAOL-MOVE
> A2 OK CAPABILITY completed
> A3 LIST "" INBOX
> * LIST (\Noinferiors) "/" "INBOX"
> A3 OK List completed
> DEBUG IMAPS: connection available -- size: 1
> A4 SELECT INBOX
> * 13 EXISTS
> * 0 RECENT
> * OK [UNSEEN 13] UIDs valid
> * OK [UIDVALIDITY 1549376878] UIDs valid
> * OK [UIDNEXT 36] Predicted next UID
> * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
> * OK [NOMODSEQ] Sorry, this mailbox format doesn't support modsequences
> A4 OK [READ-WRITE] SELECT completed
> A5 SEARCH UNSEEN 1:13
> * SEARCH 13
> A5 OK Search completed
> A6 FETCH 13 (BODY.PEEK[HEADER.FIELDS (Message-ID)])
> * 13 FETCH (BODY[HEADER.FIELDS (Message-ID)] {65}
> Message-ID: <175c8cc9-19fa-fc48-40c8-e42148578...@xx.com>
> )
> A6 OK Fetch completed
> A7 FETCH 13 (FLAGS)
> * 13 FETCH (FLAGS ())
> A7 OK Fetch completed
> A8 FETCH 13 (BODYSTRUCTURE)
> * 13 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "utf-8" "format"
> "flowed") NIL NIL "7bit" 10 3 NIL NIL NIL)("image" "jpeg" ("name"
> "images.jpg") NIL NIL "base64" 16794 NIL ("attachment" ("filename"
> "images.jpg")) NIL) "mixed" ("boundary"
> "53A9AD932142735A4433B153") NIL NIL))
> A8 OK Fetch completed
> A9 FETCH 13 (BODY.PEEK[HEADER])
> * 13 FETCH (BODY[HEADER] {3286}
> Return-Path:
> Delivered-To: xxx...@xx.com
> Received: (wp-smtpd mx.XX.com 31103 invoked from network); 22 May 2019
> 16:14:00 +0200
> Received: from mail-XXX.google.com ([209.85.167.54])
> (envelope-sender )
> by mx.tlen.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
> SMTP
> for ; 22 May 2019 16:14:00 +0200
> Received: by mail-XXX.google.com with SMTP id d8so1XXXb.8
> for ; Wed, 22 May 2019 07:14:00 -0700 (PDT)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=XXX.gappssmtp.com; s=XXX;
> h=to:from:subject:message-id:date:user-agent:mime-version
> :content-language;
> bh=8Bw7uLBuofXm3FHknjhDSjXXX=;
> b=kqcK74fTrzyDas7Wsn7EJfSxJuXXX==
> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
> d=1e100.net; s=20161025;
> h=x-gm-message-state:to:from:subject:message-id:date:user-agent
> :mime-version:content-language;
> bh=8Bw7uLBuofXm6oDyAiCFLfHU=;
> b=F1EsLfk3qaiJXiNX0XXX==
> X-Gm-Message-State: APXX=
> X-Google-Smtp-Source: APXvXWYQ==
> X-Received: by 2002:a19:c517:: with SMTP id
[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
classloader to load two default files
{code}
META-INF/javamail.default.address.map
META-INF/javamail.default.providers
{code}
Since camel-mail provider a DefaultAuthenticator, which means javax mail api
will try to use camel-mail bundle classloader in OSGi to load above default
files. Those files aren't available for camel-mail bundle classloader, so we
see warning message as
{code}
2019-04-25 12:42:09,806 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1 | expected resource not found:
/META-INF/javamail.default.providers
2019-04-25 12:42:09,807 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1| expected resource not found:
/META-INF/javamail.default.address.map
{code}
This warning message isn't harmful but annoying. The javax.mail.Session will
always add default stuff by code if can't find the default configuration file
{code}
if (providers.size() == 0) {
logger.config("failed to load any providers, using defaults");
// failed to load any providers, initialize with our defaults
addProvider(new Provider(Provider.Type.STORE,
"imap", "com.sun.mail.imap.IMAPStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"imaps", "com.sun.mail.imap.IMAPSSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3", "com.sun.mail.pop3.POP3Store",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3s", "com.sun.mail.pop3.POP3SSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtp", "com.sun.mail.smtp.SMTPTransport",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtps", "com.sun.mail.smtp.SMTPSSLTransport",
"Oracle", Version.version));
}
if (addressMap.isEmpty()) {
logger.config("failed to load address map, using defaults");
addressMap.put("rfc822", "smtp");
}
{code}
But it's better we can avoid such WARN message when using camel-mail in OSGi
was:
In javax.mail API(1.6), it(javax.mail.Session) will use authenticator's
classloader to load two default files
{code}
META-INF/javamail.default.address.map
META-INF/javamail.default.providers
{code}
Since camel-mail provider a DefaultAuthenticator, which means javax mail api
will try to use camel-mail bundle classloader in OSGi to load above default
files. Those files aren't available for camel-mail bundle classloader, so we
see warning message as
{code}
2019-04-25 12:42:09,806 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1 | expected resource not found:
/META-INF/javamail.default.providers
2019-04-25 12:42:09,807 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1| expected resource not found:
/META-INF/javamail.default.address.map
{code}
This warning message isn't harmful but annoying. The javax.mail.Session will
always add default stuff by code if can't find the default configuration file
{code}
if (providers.size() == 0) {
logger.config("failed to load any providers, using defaults");
// failed to load any providers, initialize with our defaults
addProvider(new Provider(Provider.Type.STORE,
"imap", "com.sun.mail.imap.IMAPStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"imaps", "com.sun.mail.imap.IMAPSSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3", "com.sun.mail.pop3.POP3Store",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3s", "com.sun.mail.pop3.POP3SSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtp", "com.sun.mail.smtp.SMTPTransport",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtps", "com.sun.mail.smtp.SMTPSSLTransport",
"Oracle", Version.version));
}
if
[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 camel-mail in OSGi
> --
>
> Key: CAMEL-13593
> URL: https://issues.apache.org/jira/browse/CAMEL-13593
> Project: Camel
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
>Priority: Major
>
> In javax.mail API(1.6), it(javax.mail.Session) will use authenticator's
> classloader to load two default files
> {code}
> META-INF/javamail.default.address.map
> META-INF/javamail.default.providers
> {code}
> Since camel-mail provider a DefaultAuthenticator, which means javax mail api
> will try to use camel-mail bundle classloader in OSGi to load above default
> files. Those files aren't available for camel-mail bundle classloader, so we
> see warning message as
> {code}
> 2019-04-25 12:42:09,806 | WARN | 23 - scheduler://foo | j.mail | 21 -
> com.sun.mail.javax.mail - 1.6.1 | expected resource not found:
> /META-INF/javamail.default.providers
> 2019-04-25 12:42:09,807 | WARN | 23 - scheduler://foo | j.mail | 21 -
> com.sun.mail.javax.mail - 1.6.1| expected resource not found:
> /META-INF/javamail.default.address.map
> {code}
> This warning message isn't harmful but annoying. The javax.mail.Session will
> always add default stuff by code if can't find the default configuration file
> {code}
>if (providers.size() == 0) {
> logger.config("failed to load any providers, using defaults");
> // failed to load any providers, initialize with our defaults
> addProvider(new Provider(Provider.Type.STORE,
> "imap", "com.sun.mail.imap.IMAPStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "imaps", "com.sun.mail.imap.IMAPSSLStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "pop3", "com.sun.mail.pop3.POP3Store",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.STORE,
> "pop3s", "com.sun.mail.pop3.POP3SSLStore",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.TRANSPORT,
> "smtp", "com.sun.mail.smtp.SMTPTransport",
> "Oracle", Version.version));
> addProvider(new Provider(Provider.Type.TRANSPORT,
> "smtps", "com.sun.mail.smtp.SMTPSSLTransport",
> "Oracle", Version.version));
> }
>if (addressMap.isEmpty()) {
> logger.config("failed to load address map, using defaults");
> addressMap.put("rfc822", "smtp");
> }
> {code}
> It's better we can avoid such WARN message when using camel-mail in OSGi
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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: Camel
Issue Type: Improvement
Reporter: Freeman Fang
In javax.mail API(1.6), it(javax.mail.Session) will use authenticator's
classloader to load two default files
{code}
META-INF/javamail.default.address.map
META-INF/javamail.default.providers
{code}
Since camel-mail provider a DefaultAuthenticator, which means javax mail api
will try to use camel-mail bundle classloader in OSGi to load above default
files. Those files aren't available for camel-mail bundle classloader, so we
see warning message as
{code}
2019-04-25 12:42:09,806 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1 | expected resource not found:
/META-INF/javamail.default.providers
2019-04-25 12:42:09,807 | WARN | 23 - scheduler://foo | j.mail | 21 -
com.sun.mail.javax.mail - 1.6.1| expected resource not found:
/META-INF/javamail.default.address.map
{code}
This warning message isn't harmful but annoying. The javax.mail.Session will
always add default stuff by code if can't find the default configuration file
{code}
if (providers.size() == 0) {
logger.config("failed to load any providers, using defaults");
// failed to load any providers, initialize with our defaults
addProvider(new Provider(Provider.Type.STORE,
"imap", "com.sun.mail.imap.IMAPStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"imaps", "com.sun.mail.imap.IMAPSSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3", "com.sun.mail.pop3.POP3Store",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.STORE,
"pop3s", "com.sun.mail.pop3.POP3SSLStore",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtp", "com.sun.mail.smtp.SMTPTransport",
"Oracle", Version.version));
addProvider(new Provider(Provider.Type.TRANSPORT,
"smtps", "com.sun.mail.smtp.SMTPSSLTransport",
"Oracle", Version.version));
}
if (addressMap.isEmpty()) {
logger.config("failed to load address map, using defaults");
addressMap.put("rfc822", "smtp");
}
{code}
It's better we can avoid such WARN message when using camel-mail in OSGi
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 2.22.5 2.23.3 3.0.0 > camel-cxf - failure processor for custom exception handling cannot get the > original message > --- > > Key: CAMEL-13376 > URL: https://issues.apache.org/jira/browse/CAMEL-13376 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.21.0 > Environment: Redhat Fuse 7.0 (on EAP) > reproduced with current "camel-example-cxf-proxy" example >Reporter: Jochen Riedlinger >Assignee: Freeman Fang >Priority: Minor > Fix For: 3.0.0, 2.23.3, 2.22.5, 2.24.1, 2.25.0 > > > I configured custom exception handling for a CXF consumer where I want to use > my own processor. > > Lile this: > > onException(Exception.class) > .handled(false) > .useOriginalMessage() > .process(failureResponseProcessor); > > or: > > > java.lang.Exception > false > > > If allowStreaming is enabled on the CXF consumer endpoint, my > FailureResponseProcessor cannot get the original body (the body part of > CachedCxfPayload seems to be empty). > If I set allowStreaming to false, the processor works as expected. > I did a branch on my fork to create this reproducer: > https://github.com/jochenr/camel/tree/Reproducer-CXF-CustomExceptionHandling-in-StreamingMode/examples/camel-example-cxf-proxy > If you toggle the setting of allowStreaming between true and false, you see > the different output to the console, right after the string > "This was the original BODY that caused the fault:" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 cached stream source so CxfPayload is re-readable > camel-cxf - failure processor for custom exception handling cannot get the > original message > --- > > Key: CAMEL-13376 > URL: https://issues.apache.org/jira/browse/CAMEL-13376 > Project: Camel > Issue Type: Bug > Components: camel-cxf >Affects Versions: 2.21.0 > Environment: Redhat Fuse 7.0 (on EAP) > reproduced with current "camel-example-cxf-proxy" example >Reporter: Jochen Riedlinger >Assignee: Freeman Fang >Priority: Minor > > I configured custom exception handling for a CXF consumer where I want to use > my own processor. > > Lile this: > > onException(Exception.class) > .handled(false) > .useOriginalMessage() > .process(failureResponseProcessor); > > or: > > > java.lang.Exception > false > > > If allowStreaming is enabled on the CXF consumer endpoint, my > FailureResponseProcessor cannot get the original body (the body part of > CachedCxfPayload seems to be empty). > If I set allowStreaming to false, the processor works as expected. > I did a branch on my fork to create this reproducer: > https://github.com/jochenr/camel/tree/Reproducer-CXF-CustomExceptionHandling-in-StreamingMode/examples/camel-example-cxf-proxy > If you toggle the setting of allowStreaming between true and false, you see > the different output to the console, right after the string > "This was the original BODY that caused the fault:" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
