[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-13889) website - Tab title should be just Apache Camel
[ https://issues.apache.org/jira/browse/CAMEL-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929414#comment-16929414 ] Alexandre Kieling commented on CAMEL-13889: --- Each page has a different title, which is - . Do you want to only show the site title? > website - Tab title should be just Apache Camel > --- > > Key: CAMEL-13889 > URL: https://issues.apache.org/jira/browse/CAMEL-13889 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Minor > Labels: help-wanted > Attachments: Screenshot 2019-08-21 at 09.26.43.png > > > Use Apache Camel instead of > Homepage - Apache Camel -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13957) Dead link from Writing components documentation page
[ https://issues.apache.org/jira/browse/CAMEL-13957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929392#comment-16929392 ] Alexandre Kieling commented on CAMEL-13957: --- Are the files with broken links available somewhere else? > Dead link from Writing components documentation page > > > Key: CAMEL-13957 > URL: https://issues.apache.org/jira/browse/CAMEL-13957 > Project: Camel > Issue Type: Bug > Components: documentation, website >Reporter: Aurélien Pupier >Priority: Major > Labels: help-wanted > > from [https://camel.apache.org/manual/latest/writing-components.html there > are several dead > links:|https://camel.apache.org/manual/latest/writing-components.html] > * Component > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/Component.html] > * DefaultComponent > [http://activemq.apache.org/camel/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultComponent.html] > * CamelContext > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html] > * createProducer() > [http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Endpoint.html#createProducer()] > * and not checked after that -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13977) Expose additional Camel metrics from MicroProfile metrics component
James Netherton created CAMEL-13977: --- Summary: Expose additional Camel metrics from MicroProfile metrics component Key: CAMEL-13977 URL: https://issues.apache.org/jira/browse/CAMEL-13977 Project: Camel Issue Type: Improvement Affects Versions: 3.x, 3.0.0.RC2 Reporter: James Netherton Assignee: James Netherton Fix For: 3.x, 3.0.0.RC2 It would be good to add some additional metrics to the route policy and event notifier. I.e mimic some of the stats that Camel has traditionally exposed via JMX, like number of failed / completed / inflight exchanges. At the moment some of them would have to be calculated or inferred from other metrics, which isn't very user friendly. Also it'd be good to ensure all of the metric names and tags conform better to the MicoProfile metrics spec. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13964) Create camel-debezium examples
[ https://issues.apache.org/jira/browse/CAMEL-13964?focusedWorklogId=312100&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312100 ] ASF GitHub Bot logged work on CAMEL-13964: -- Author: ASF GitHub Bot Created on: 13/Sep/19 14:50 Start Date: 13/Sep/19 14:50 Worklog Time Spent: 10m Work Description: omarsmak commented on pull request #3171: CAMEL-13964: Add debezium example using Cassandra with MySQL URL: https://github.com/apache/camel/pull/3171 This PR shall add a complete example to stream changes from MySQL using Debezium to Kinesis and then finally sink changes into Cassandra. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 312100) Remaining Estimate: 0h Time Spent: 10m > Create camel-debezium examples > -- > > Key: CAMEL-13964 > URL: https://issues.apache.org/jira/browse/CAMEL-13964 > Project: Camel > Issue Type: Task > Components: camel-debezium >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.0.0.RC2 > > Time Spent: 10m > Remaining Estimate: 0h > > Per the title, add couple of useful examples for camel-debezium that can help > the users to use this components -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?focusedWorklogId=312041&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312041 ] ASF GitHub Bot logged work on CAMEL-13968: -- Author: ASF GitHub Bot Created on: 13/Sep/19 13:33 Start Date: 13/Sep/19 13:33 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3169: CAMEL-13968: resolved HTTP header case sensitivity while parsing URL: https://github.com/apache/camel/pull/3169 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 312041) Remaining Estimate: 3h 20m (was: 3.5h) Time Spent: 40m (was: 0.5h) > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Assignee: Andrea Cosentino >Priority: Major > Labels: as2, content-type, http-headers, patch > Fix For: 2.25.0, 3.0.0.RC2 > > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 40m > Remaining Estimate: 3h 20m > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13968: - Fix Version/s: 2.25.0 > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Assignee: Andrea Cosentino >Priority: Major > Labels: as2, content-type, http-headers, patch > Fix For: 2.25.0, 3.0.0.RC2 > > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13968: - Fix Version/s: 3.0.0.RC2 > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Assignee: Andrea Cosentino >Priority: Major > Labels: as2, content-type, http-headers, patch > Fix For: 3.0.0.RC2 > > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13968: Assignee: Andrea Cosentino > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Assignee: Andrea Cosentino >Priority: Major > Labels: as2, content-type, http-headers, patch > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13976) Allow AS2 Component to reply disposition type failed in the MDN
[ https://issues.apache.org/jira/browse/CAMEL-13976?focusedWorklogId=312006&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-312006 ] ASF GitHub Bot logged work on CAMEL-13976: -- Author: ASF GitHub Bot Created on: 13/Sep/19 12:20 Start Date: 13/Sep/19 12:20 Worklog Time Spent: 10m Work Description: Maurice-Betzel commented on pull request #3170: CAMEL-13976: added disposition type Failed URL: https://github.com/apache/camel/pull/3170 Allow AS2 Component to reply disposition type failed in the MDN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 312006) Remaining Estimate: 0h Time Spent: 10m > Allow AS2 Component to reply disposition type failed in the MDN > --- > > Key: CAMEL-13976 > URL: https://issues.apache.org/jira/browse/CAMEL-13976 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.2, 3.0.0.RC1 >Reporter: Maurice Betzel >Priority: Minor > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > If on the receiving side of the AS2 request the payload processing fails, no > MDN at all is returned. Add an option for returning a MDN with the > Disposition type: Failed. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?focusedWorklogId=311998&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-311998 ] ASF GitHub Bot logged work on CAMEL-13968: -- Author: ASF GitHub Bot Created on: 13/Sep/19 12:12 Start Date: 13/Sep/19 12:12 Worklog Time Spent: 10m Work Description: Maurice-Betzel commented on pull request #3167: CAMEL-13968: resolved HTTP header case sensitivity while parsing URL: https://github.com/apache/camel/pull/3167 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 311998) Remaining Estimate: 3.5h (was: 3h 40m) Time Spent: 0.5h (was: 20m) > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Priority: Major > Labels: as2, content-type, http-headers, patch > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 0.5h > Remaining Estimate: 3.5h > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (CAMEL-13976) Allow AS2 Component to reply disposition type failed
Maurice Betzel created CAMEL-13976: -- Summary: Allow AS2 Component to reply disposition type failed Key: CAMEL-13976 URL: https://issues.apache.org/jira/browse/CAMEL-13976 Project: Camel Issue Type: Bug Components: camel-as2 Affects Versions: 3.0.0.RC1, 2.24.2 Reporter: Maurice Betzel Fix For: 3.0.0 If on the receiving side of the AS2 request the payload processing fails, no MDN at all is returned. Add an option for returning a MDN with the Disposition type: Failed. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13976) Allow AS2 Component to reply disposition type failed in the MDN
[ https://issues.apache.org/jira/browse/CAMEL-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maurice Betzel updated CAMEL-13976: --- Summary: Allow AS2 Component to reply disposition type failed in the MDN (was: Allow AS2 Component to reply disposition type failed) > Allow AS2 Component to reply disposition type failed in the MDN > --- > > Key: CAMEL-13976 > URL: https://issues.apache.org/jira/browse/CAMEL-13976 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.2, 3.0.0.RC1 >Reporter: Maurice Betzel >Priority: Minor > Fix For: 3.0.0 > > > If on the receiving side of the AS2 request the payload processing fails, no > MDN at all is returned. Add an option for returning a MDN with the > Disposition type: Failed. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (CAMEL-13886) camel-servlet + camel-http4 with null body causes "Stream closed" IOException
[
https://issues.apache.org/jira/browse/CAMEL-13886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tadayoshi Sato updated CAMEL-13886:
---
Fix Version/s: 2.25.0
> camel-servlet + camel-http4 with null body causes "Stream closed" IOException
> -
>
> Key: CAMEL-13886
> URL: https://issues.apache.org/jira/browse/CAMEL-13886
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-http4, camel-servlet
>Affects Versions: 2.25.0, 3.0.0.M4
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 2.25.0, 3.0.0.RC2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A Rest DSL route like the following causes {{java.io.IOException: Stream
> closed}} when invoked at http://localhost:8000/test/proxy:
> {code:java}
> rest("/test")
> .get("/proxy")
> .to("direct:callInternalRestService");
> from("direct:callInternalRestService")
> .setHeader(Exchange.HTTP_METHOD, constant("DELETE"))
> //.setBody(constant("")) // workaround for null body and
> http4 component
> .to("http4://localhost:9000/test?bridgeEndpoint=true")
> .log("${body}");
> {code}
> The error stacktrace:
> {code}
> Caused by: java.io.IOException: Stream closed
> at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:372)
> at
> org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:156)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:202)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:174)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:234)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:230)
> at
> org.apache.camel.http.common.HttpHelper.readResponseBodyFromInputStream(HttpHelper.java:245)
> at
> org.apache.camel.http.common.HttpHelper.readRequestBodyFromServletRequest(HttpHelper.java:196)
> at
> org.apache.camel.http.common.DefaultHttpBinding.parseBody(DefaultHttpBinding.java:577)
> at
> org.apache.camel.http.common.HttpMessage.createBody(HttpMessage.java:78)
> ... 54 common frames omitted
> {code}
> -This seems to happen only when Tomcat is used as the container with Spring
> Boot. Undertow doesn't cause such an issue.-
> The real root cause is that when an exchange has an {{HttpMessage}} with
> {{null}} body as its out message, then the next time
> {{Exchange.getMessage()}} is invoked the {{HttpMessage}} is tricked by the
> {{null}} body and tries to create body again with the already closed request
> input stream.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13974) Many examples are missing camel component dependencies
[ https://issues.apache.org/jira/browse/CAMEL-13974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-13974. - Resolution: Fixed > Many examples are missing camel component dependencies > -- > > Key: CAMEL-13974 > URL: https://issues.apache.org/jira/browse/CAMEL-13974 > Project: Camel > Issue Type: Improvement > Components: examples >Affects Versions: 3.x >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 3.x, 3.0.0.RC2 > > > Quite a few of the examples are missing component dependencies. Mainly for > the timer and file components. > camel-example-fhir > camel-example-jdbc > camel-example-jooq > camel-example-management > camel-example-micrometer > camel-example-opentracing > camel-example-spring-xquery > camel-example-swagger-cdi > camel-example-widget-gadget-cdi > camel-example-zipkin -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work logged] (CAMEL-13968) AS2 component treats http headers case sensitive. According to RFC this should be case insensitive
[ https://issues.apache.org/jira/browse/CAMEL-13968?focusedWorklogId=311913&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-311913 ] ASF GitHub Bot logged work on CAMEL-13968: -- Author: ASF GitHub Bot Created on: 13/Sep/19 08:23 Start Date: 13/Sep/19 08:23 Worklog Time Spent: 10m Work Description: Maurice-Betzel commented on pull request #3169: CAMEL-13968: resolved HTTP header case sensitivity while parsing URL: https://github.com/apache/camel/pull/3169 PR against Master This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 311913) Remaining Estimate: 3h 40m (was: 3h 50m) Time Spent: 20m (was: 10m) > AS2 component treats http headers case sensitive. According to RFC this > should be case insensitive > -- > > Key: CAMEL-13968 > URL: https://issues.apache.org/jira/browse/CAMEL-13968 > Project: Camel > Issue Type: Bug > Components: camel-as2 >Affects Versions: 2.24.1, 3.0.0.RC1 >Reporter: Sjoerd Brauer >Priority: Major > Labels: as2, content-type, http-headers, patch > Attachments: EntityParser.java > > Original Estimate: 4h > Time Spent: 20m > Remaining Estimate: 3h 40m > > The AS2 component treats headers case-sensitive according to the switch case > enum's. According to the RFC this should be case-insensitive: > [https://tools.ietf.org/html/rfc7230#section-3.2] > Headers should be treated case insensitive. > This happens at: > package org.apache.camel.component.as2.api.entity.EntityParser; > in the method: parseMultipartSignedEntityBody > at line: 487. Specifically the following lines: > lines: 523,526 and in the switch block that follows > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (CAMEL-13818) News section design
[ https://issues.apache.org/jira/browse/CAMEL-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929042#comment-16929042 ] Zoran Regvart commented on CAMEL-13818: --- I think I'll rename the "News" section to "Blog" and add simple design with pagination as a first step. > News section design > --- > > Key: CAMEL-13818 > URL: https://issues.apache.org/jira/browse/CAMEL-13818 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Labels: help-wanted > > The news section of the site lacks design, currently it just shows the > default list table, we could make this look more like blog post list. > Individual news sections also lack design. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (CAMEL-13818) News section design
[ https://issues.apache.org/jira/browse/CAMEL-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-13818: - Assignee: Zoran Regvart > News section design > --- > > Key: CAMEL-13818 > URL: https://issues.apache.org/jira/browse/CAMEL-13818 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Labels: help-wanted > > The news section of the site lacks design, currently it just shows the > default list table, we could make this look more like blog post list. > Individual news sections also lack design. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Work started] (CAMEL-13818) News section design
[ https://issues.apache.org/jira/browse/CAMEL-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-13818 started by Zoran Regvart. - > News section design > --- > > Key: CAMEL-13818 > URL: https://issues.apache.org/jira/browse/CAMEL-13818 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Labels: help-wanted > > The news section of the site lacks design, currently it just shows the > default list table, we could make this look more like blog post list. > Individual news sections also lack design. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (CAMEL-7294) Simple Language - Accessing hashCode
[
https://issues.apache.org/jira/browse/CAMEL-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929026#comment-16929026
]
Omar Al-Safi edited comment on CAMEL-7294 at 9/13/19 7:35 AM:
--
Hey [~davsclaus], I was digging to know what is the motivation behind excluding
{{hashCode}} and {{equal}}? It could be the case that a component returns an
object with overriden hashCode and equal and you want to retrieve these through
Simple language as it is much simpler than invoking {{.process}} and set it
there.
was (Author: omarsmak):
Hey [~davsclaus], I was digging to know what is the motivation behind excluding
{{hashCode}} and {{equal}}? It could be the case that a component returns an
object with overriden hashCode and equal and you want to retrieve these through
Simple language as it is much simpler than invoking `.process` and set it there.
> Simple Language - Accessing hashCode
> -
>
> Key: CAMEL-7294
> URL: https://issues.apache.org/jira/browse/CAMEL-7294
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.12.3
>Reporter: Alan Foster
>Assignee: Willem Jiang
>Priority: Major
>
> With the following blueprint route
> {code:xml}
> xmlns="http://camel.apache.org/schema/blueprint";>
>
>
>
> Hello World
>
>
>
> ${body.hashCode}
>
>
>
>
> {code}
> The following exception occurs
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Hello World]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1379)
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:622)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:463)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:139)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:144)
> at camel.SimpleEqualsTest.testRoute(SimpleEqualsTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs
[jira] [Comment Edited] (CAMEL-7294) Simple Language - Accessing hashCode
[
https://issues.apache.org/jira/browse/CAMEL-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929026#comment-16929026
]
Omar Al-Safi edited comment on CAMEL-7294 at 9/13/19 7:34 AM:
--
Hey [~davsclaus], I was digging to know what is the motivation behind excluding
{{hashCode}} and {{equal}}? It could be the case that a component returns an
object with overriden hashCode and equal and you want to retrieve these through
Simple language as it is much simpler than invoking `.process` and set it there.
was (Author: omarsmak):
Hey [~davsclaus], I was digging to know what is the motivation behind excluding
`hashCode` and `equal`? It could be the case that a component returns an object
with overriden hashCode and equal and you want to retrieve these through Simple
language as it is much simpler than invoking `.process` and set it there.
> Simple Language - Accessing hashCode
> -
>
> Key: CAMEL-7294
> URL: https://issues.apache.org/jira/browse/CAMEL-7294
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.12.3
>Reporter: Alan Foster
>Assignee: Willem Jiang
>Priority: Major
>
> With the following blueprint route
> {code:xml}
> xmlns="http://camel.apache.org/schema/blueprint";>
>
>
>
> Hello World
>
>
>
> ${body.hashCode}
>
>
>
>
> {code}
> The following exception occurs
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Hello World]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1379)
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:622)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:463)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:139)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:144)
> at camel.SimpleEqualsTest.testRoute(SimpleEqualsTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4
[jira] [Commented] (CAMEL-7294) Simple Language - Accessing hashCode
[
https://issues.apache.org/jira/browse/CAMEL-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929026#comment-16929026
]
Omar Al-Safi commented on CAMEL-7294:
-
Hey [~davsclaus], I was digging to know what is the motivation behind excluding
`hashCode` and `equal`? It could be the case that a component returns an object
with overriden hashCode and equal and you want to retrieve these through Simple
language as it is much simpler than invoking `.process` and set it there.
> Simple Language - Accessing hashCode
> -
>
> Key: CAMEL-7294
> URL: https://issues.apache.org/jira/browse/CAMEL-7294
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.12.3
>Reporter: Alan Foster
>Assignee: Willem Jiang
>Priority: Major
>
> With the following blueprint route
> {code:xml}
> xmlns="http://camel.apache.org/schema/blueprint";>
>
>
>
> Hello World
>
>
>
> ${body.hashCode}
>
>
>
>
> {code}
> The following exception occurs
> {code}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[Message: Hello World]
> at
> org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1379)
> at
> org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:622)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:467)
> at
> org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:463)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:139)
> at
> org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:144)
> at camel.SimpleEqualsTest.testRoute(SimpleEqualsTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:202)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at com.int
