[jira] [Created] (CAMEL-7427) camel-netty-http component should skip reading the form body if it is bridgeEndpoint
Willem Jiang created CAMEL-7427: --- Summary: camel-netty-http component should skip reading the form body if it is bridgeEndpoint Key: CAMEL-7427 URL: https://issues.apache.org/jira/browse/CAMEL-7427 Project: Camel Issue Type: Bug Components: camel-netty-http Affects Versions: 2.13.0 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.13.2 We need fix the same issue of CAMEL-7426 in camel-netty-http -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-6543) provide a way to expose common header names, types and payload types for endpoints
[ https://issues.apache.org/jira/browse/CAMEL-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned CAMEL-6543: --- Assignee: Grzegorz Grzybek > provide a way to expose common header names, types and payload types for > endpoints > -- > > Key: CAMEL-6543 > URL: https://issues.apache.org/jira/browse/CAMEL-6543 > Project: Camel > Issue Type: Improvement >Reporter: james strachan >Assignee: Grzegorz Grzybek > > Given a configuration of an Endpoint, it'd be nice if there was a way for > endpoints to expose what a consumer will receive up front (at design time, > before it actually runs), in terms of headers (their name & types) and the > payload type. > Most of this is documented on the wiki in places already - its useful stuff > to konw; but there's no way to introspect an endpoint and know this (so we > can, for example, visualise the things exposed by an endpoint - or provide > better validation of what can connect to what, what will work or fail; what > type conversions could be done after consuming from an endpoint, what headers > are available by default in expression languages and so forth. > I guess other steps in a camel flow can change this data too (e.g. > adding/removing headers, changing the payload value). > But as a start - and endpoint consumer specific plugin would be great. > e.g. maybe we can add a new method to ComponentConfiguration which allows > endpoints to return the header/payload metadata (if its known) > https://cwiki.apache.org/confluence/display/CAMEL/ComponentConfiguration > We could maybe add some annotations, metadata or code which could then be > introspected by the generated endpoint documentation: > https://cwiki.apache.org/confluence/display/CAMEL/Endpoint+Annotations > afterall we often define constants for the header values already for a > component; so it would be easy to add an annotation and have them discovered; > its mostly just being able to find all the headers exposed by default (and > which are optional I guess) on messages from an endpoint. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7435) Create a generic callback to configure the APNS service builder
[
https://issues.apache.org/jira/browse/CAMEL-7435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henryk Konsek updated CAMEL-7435:
-
Description:
We should add an empty callback method to {{ApnsServiceFactory}} that could be
used to configure (or even replace) the default {{ApnsServiceBuilder}} instance.
Signature of the method could look as follows:
{code}
protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
serviceBuilder)
{code}
And could be used like:
{code}
ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
@Override
protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
serviceBuilder) {
return serviceBuilder.withSocksProxy("my.proxy.com", );
}
};
{code}
was:
We should add an empty callback method to {{ApnsServiceFactory}} that could be
used to configure (or even replace) the default {{ApnsService}} instance.
Signature of the method could look as follows:
{code}
protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
serviceBuilder)
{code}
And could be used like:
{code}
ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
@Override
protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
serviceBuilder) {
return serviceBuilder.withSocksProxy("my.proxy.com", );
}
};
{code}
> Create a generic callback to configure the APNS service builder
> ---
>
> Key: CAMEL-7435
> URL: https://issues.apache.org/jira/browse/CAMEL-7435
> Project: Camel
> Issue Type: Improvement
> Components: camel-apns
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.14.0
>
>
> We should add an empty callback method to {{ApnsServiceFactory}} that could
> be used to configure (or even replace) the default {{ApnsServiceBuilder}}
> instance.
> Signature of the method could look as follows:
> {code}
> protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
> serviceBuilder)
> {code}
> And could be used like:
> {code}
> ApnsServiceFactory proxiedApnsServiceFactory = new ApnsServiceFactory(){
> @Override
> protected ApnsServiceBuilder configureServiceBuilder(ApnsServiceBuilder
> serviceBuilder) {
> return serviceBuilder.withSocksProxy("my.proxy.com", );
> }
> };
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7440) Camel Bindy compoent does not log the correct property when quoting is enabled
[
https://issues.apache.org/jira/browse/CAMEL-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997671#comment-13997671
]
ASF GitHub Bot commented on CAMEL-7440:
---
GitHub user jsherman1 opened a pull request:
https://github.com/apache/camel/pull/152
CSV log message should log the quoting property
Fix for https://issues.apache.org/jira/browse/CAMEL-7440
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsherman1/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/152.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #152
commit 7dd3a69796b66c08af20da7a0a0bad6f005e1d34
Author: Jason Sherman
Date: 2014-05-14T15:41:24Z
CSV log message should log the quoting property
> Camel Bindy compoent does not log the correct property when quoting is enabled
> --
>
> Key: CAMEL-7440
> URL: https://issues.apache.org/jira/browse/CAMEL-7440
> Project: Camel
> Issue Type: Bug
> Components: camel-bindy
>Affects Versions: 2.13.0
>Reporter: Jason Sherman
>
> The property quoting is not logging the correct value in
> ./org/apache/camel/dataformat/bindy/BindyCsvFactory.java:
> {code}
> ...
> quoting = record.quoting();
> LOG.debug("CSV will be quoted: {}", messageOrdered);
> ...
> {code}
> The value for messageOrdered is being logged instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CAMEL-7423) Netty HTTP producer ignores requestTimeout option
[
https://issues.apache.org/jira/browse/CAMEL-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henryk Konsek updated CAMEL-7423:
-
Description: {{DefaultClientPipelineFactory}} respects the
{{requestTimeout}} option, but {{HttpClientPipelineFactory}} doesn't. We should
add {{requestTimeout}} resolution logic (and {{ReadTimeoutHandler}}) to the
HTTP pipeline creation process.
> Netty HTTP producer ignores requestTimeout option
> -
>
> Key: CAMEL-7423
> URL: https://issues.apache.org/jira/browse/CAMEL-7423
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.14.0
>
>
> {{DefaultClientPipelineFactory}} respects the {{requestTimeout}} option, but
> {{HttpClientPipelineFactory}} doesn't. We should add {{requestTimeout}}
> resolution logic (and {{ReadTimeoutHandler}}) to the HTTP pipeline creation
> process.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CAMEL-7440) Camel Bindy compoent does not log the correct property when quoting is enabled
Jason Sherman created CAMEL-7440:
Summary: Camel Bindy compoent does not log the correct property
when quoting is enabled
Key: CAMEL-7440
URL: https://issues.apache.org/jira/browse/CAMEL-7440
Project: Camel
Issue Type: Bug
Components: camel-bindy
Affects Versions: 2.13.0
Reporter: Jason Sherman
The property quoting is not logging the correct value in
./org/apache/camel/dataformat/bindy/BindyCsvFactory.java:
{code}
...
quoting = record.quoting();
LOG.debug("CSV will be quoted: {}", messageOrdered);
...
{code}
The value for messageOrdered is being logged instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CAMEL-7427) camel-netty-http component should skip reading the form body if it is bridgeEndpoint
[ https://issues.apache.org/jira/browse/CAMEL-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7427. - Resolution: Fixed Applied the patch into camel master and camel-2.13.x. > camel-netty-http component should skip reading the form body if it is > bridgeEndpoint > > > Key: CAMEL-7427 > URL: https://issues.apache.org/jira/browse/CAMEL-7427 > Project: Camel > Issue Type: Bug > Components: camel-netty-http >Affects Versions: 2.13.0 >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.13.2 > > > We need to fix the same issue of CAMEL-7426 in camel-netty-http -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7441) The Camel Bindy documentation does not provide information on the quoting property
Jason Sherman created CAMEL-7441: Summary: The Camel Bindy documentation does not provide information on the quoting property Key: CAMEL-7441 URL: https://issues.apache.org/jira/browse/CAMEL-7441 Project: Camel Issue Type: Bug Components: camel-bindy, documentation Reporter: Jason Sherman Priority: Minor The documentation at http://camel.apache.org/bindy.html does not provide information on the quoting property. Can the doc be updated to provide details on this option? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7440) Camel Bindy compoent does not log the correct property when quoting is enabled
[
https://issues.apache.org/jira/browse/CAMEL-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997674#comment-13997674
]
Jason Sherman commented on CAMEL-7440:
--
Pull request created to resolve this issue:
https://github.com/apache/camel/pull/152
Diff:
https://github.com/apache/camel/pull/152.diff
> Camel Bindy compoent does not log the correct property when quoting is enabled
> --
>
> Key: CAMEL-7440
> URL: https://issues.apache.org/jira/browse/CAMEL-7440
> Project: Camel
> Issue Type: Bug
> Components: camel-bindy
>Affects Versions: 2.13.0
>Reporter: Jason Sherman
>
> The property quoting is not logging the correct value in
> ./org/apache/camel/dataformat/bindy/BindyCsvFactory.java:
> {code}
> ...
> quoting = record.quoting();
> LOG.debug("CSV will be quoted: {}", messageOrdered);
> ...
> {code}
> The value for messageOrdered is being logged instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
