[jira] [Commented] (CAMEL-5483) Component for neo4j
[ https://issues.apache.org/jira/browse/CAMEL-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433931#comment-13433931 ] stephen samuel commented on CAMEL-5483: --- I signed up for Confluence but don't have privileges to create a new page. Component for neo4j --- Key: CAMEL-5483 URL: https://issues.apache.org/jira/browse/CAMEL-5483 Project: Camel Issue Type: Improvement Reporter: stephen samuel Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 Attachments: camel-neo4j.patch, remove-int-tests.patch I have created a component for neo4j. It is a producer only and it allows you to create / remove nodes and relationships. -- read me -- camel-neo4j The camel-neo4j component allows you to treat Neo4j as a camel producer endpoint. This means you can use this component in to() calls but not from() calls. This component is backed by the Spring Data Neo4j Library. * As a producer, can create or remove nodes, and create or remove relationships. * Can support as many endpoints as required, eg for multiple databases across multiple instances. * Headers set for node id (for created nodes), relationship id (for created relationships) How to Use == You can use neo4j as an endpoint with the following URI. `neo4j:http://hostname[:port]/database` Then you need to set a header on each message, one of the following enum types ` CREATE_NODE, REMOVE_NODE, CREATE_RELATIONSHIP, REMOVE_RELATIONSHIP` Eg, `exchange.getIn().setHeader(Neo4jEndpoint.HEADER_OPERATION, Neo4jOperation.CREATE_NODE);` The body of the message is used to determine the node or relationship to manipulate. The following body types are supported: For CREATE_NODE: * null body - create default node * Map body - create node with the properties set from the map For REMOVE_NODE: * Long or Integer - remove node using the body as the id * neo4j Node instance - remove the node specified by that instance For CREATE_RELATIONSHIP: * SpringDataRelationship - create relationship specified by any @NodeEntity annoted Spring entities. * BasicRelationship - create relationship specified by the neo4j node types For REMOVE_RELATIONSHIP: * Long or Integer - remove relationship using the body as the id * SpringDataRelationship - remove relationship specified by the @NodeEntity annoted Spring entities. * BasicRelationship - remove relationship specified by the neo4j node types Tests = camel-neo4j has a complete set of unit tests. In addition there are some integration tests that require you to run a local instance of neo4j. By default the tests will look at localhost:7474 on http://localhost:7474/db/data/ - Initial contribution by Stephen Samuel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5483) Component for neo4j
[ https://issues.apache.org/jira/browse/CAMEL-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433943#comment-13433943 ] Willem Jiang commented on CAMEL-5483: - @Stephen, you can send a mail to the dev with your Confluence id. I think you will be grant with the right shortly. Component for neo4j --- Key: CAMEL-5483 URL: https://issues.apache.org/jira/browse/CAMEL-5483 Project: Camel Issue Type: Improvement Reporter: stephen samuel Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 Attachments: camel-neo4j.patch, remove-int-tests.patch I have created a component for neo4j. It is a producer only and it allows you to create / remove nodes and relationships. -- read me -- camel-neo4j The camel-neo4j component allows you to treat Neo4j as a camel producer endpoint. This means you can use this component in to() calls but not from() calls. This component is backed by the Spring Data Neo4j Library. * As a producer, can create or remove nodes, and create or remove relationships. * Can support as many endpoints as required, eg for multiple databases across multiple instances. * Headers set for node id (for created nodes), relationship id (for created relationships) How to Use == You can use neo4j as an endpoint with the following URI. `neo4j:http://hostname[:port]/database` Then you need to set a header on each message, one of the following enum types ` CREATE_NODE, REMOVE_NODE, CREATE_RELATIONSHIP, REMOVE_RELATIONSHIP` Eg, `exchange.getIn().setHeader(Neo4jEndpoint.HEADER_OPERATION, Neo4jOperation.CREATE_NODE);` The body of the message is used to determine the node or relationship to manipulate. The following body types are supported: For CREATE_NODE: * null body - create default node * Map body - create node with the properties set from the map For REMOVE_NODE: * Long or Integer - remove node using the body as the id * neo4j Node instance - remove the node specified by that instance For CREATE_RELATIONSHIP: * SpringDataRelationship - create relationship specified by any @NodeEntity annoted Spring entities. * BasicRelationship - create relationship specified by the neo4j node types For REMOVE_RELATIONSHIP: * Long or Integer - remove relationship using the body as the id * SpringDataRelationship - remove relationship specified by the @NodeEntity annoted Spring entities. * BasicRelationship - remove relationship specified by the neo4j node types Tests = camel-neo4j has a complete set of unit tests. In addition there are some integration tests that require you to run a local instance of neo4j. By default the tests will look at localhost:7474 on http://localhost:7474/db/data/ - Initial contribution by Stephen Samuel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5471) Exception: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
[ https://issues.apache.org/jira/browse/CAMEL-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433971#comment-13433971 ] Elena Tatarintseva commented on CAMEL-5471: --- Only strange that the same example works ok on Camel 2.9.2 and Camel 2.10.0. And only on Camel 2.9.3-SNAPSHOT we receive this exception. But ok, I will try to make this changes. Exception: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE Key: CAMEL-5471 URL: https://issues.apache.org/jira/browse/CAMEL-5471 Project: Camel Issue Type: Bug Components: camel-blueprint Affects Versions: 2.9.3 Environment: Windows 7 Reporter: Elena Tatarintseva Assignee: Christian Müller Priority: Minor Attachments: camel-example-cxf-blueprint-2.9.2.jar, camel-example-cxf-blueprint-2.9.3-SNAPSHOT.jar, error.log.txt, example.xml Install apache-karaf-2.2.8. Start karaf container features:addurl mvn:org.apache.camel.karaf/apache-camel/2.9.3-SNAPSHOT/xml/features features:install cxf features:install camel-cxf features:install camel-blueprint features:install camel-stream Copy to deploy folder camel-example-cxf-blueprint-2.9.2.jar and example.xml. In SoapUI : http://localhost:8182/cxf/camel-example-cxf-blueprint/webservices/incident soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Header / soap:Body ns2:inputReportIncident xmlns:ns2=http://reportincident.example.camel.apache.org; incidentId111/incidentId incidentDate2011-03-05/incidentDate givenNameChristian/givenName familyNameMueller/familyName summaryBla/summary detailsBla bla/details emailcmuel...@apache.org/email phone0049 69 1234567/phone /ns2:inputReportIncident /soap:Body /soap:Envelope Response is: soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringCurrent state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE/faultstring /soap:Fault /soap:Body /soap:Envelope And the exception in karaf console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-5471) Exception: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
[ https://issues.apache.org/jira/browse/CAMEL-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433971#comment-13433971 ] Elena Tatarintseva edited comment on CAMEL-5471 at 8/14/12 7:24 PM: camelContext xmlns=http://camel.apache.org/schema/blueprint; route from uri=routerEndpointFrom/ convertBodyTo type=java.lang.String / multicast to uri=log:proxyLog?level=INFO/ to uri=routerEndpointTo/ /multicast /route /camelContext works ok. Thank you. Will discuss to our team do we need to change codegeneration of our example. was (Author: etatarintseva): Only strange that the same example works ok on Camel 2.9.2 and Camel 2.10.0. And only on Camel 2.9.3-SNAPSHOT we receive this exception. But ok, I will try to make this changes. Exception: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE Key: CAMEL-5471 URL: https://issues.apache.org/jira/browse/CAMEL-5471 Project: Camel Issue Type: Bug Components: camel-blueprint Affects Versions: 2.9.3 Environment: Windows 7 Reporter: Elena Tatarintseva Assignee: Christian Müller Priority: Minor Attachments: camel-example-cxf-blueprint-2.9.2.jar, camel-example-cxf-blueprint-2.9.3-SNAPSHOT.jar, error.log.txt, example.xml Install apache-karaf-2.2.8. Start karaf container features:addurl mvn:org.apache.camel.karaf/apache-camel/2.9.3-SNAPSHOT/xml/features features:install cxf features:install camel-cxf features:install camel-blueprint features:install camel-stream Copy to deploy folder camel-example-cxf-blueprint-2.9.2.jar and example.xml. In SoapUI : http://localhost:8182/cxf/camel-example-cxf-blueprint/webservices/incident soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Header / soap:Body ns2:inputReportIncident xmlns:ns2=http://reportincident.example.camel.apache.org; incidentId111/incidentId incidentDate2011-03-05/incidentDate givenNameChristian/givenName familyNameMueller/familyName summaryBla/summary detailsBla bla/details emailcmuel...@apache.org/email phone0049 69 1234567/phone /ns2:inputReportIncident /soap:Body /soap:Envelope Response is: soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringCurrent state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE/faultstring /soap:Fault /soap:Body /soap:Envelope And the exception in karaf console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5491) Cannot access blueprint property placeholder values from velocity
[ https://issues.apache.org/jira/browse/CAMEL-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433999#comment-13433999 ] Claus Ibsen commented on CAMEL-5491: Yeah notice that properties on Exchange and the properties placeholder is not the same thing. I assume you want access to the latter from the templates, eg to use values from a .properties file etc. And for that you need to use the API from CamelContext such as the resolvePropertyPlaceholders method, that is possible the easiest. You would then need to fund a hook into velocity, so you can call the resolvePropertyPlaceholders with the value, and return the result to velocity. Cannot access blueprint property placeholder values from velocity - Key: CAMEL-5491 URL: https://issues.apache.org/jira/browse/CAMEL-5491 Project: Camel Issue Type: New Feature Components: camel-blueprint, camel-freemarker, camel-velocity Affects Versions: 2.10.0 Reporter: Alan Foster Priority: Minor Fix For: 2.11.0, Future There isn't a way within velocity to access properties set within the blueprint property-placeholder. Currently you can only access the exchange's properties according to the documentation at http://camel.apache.org/velocity.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5503) Expanding Bean Binding annotations to define explicitly what to apply it to
[
https://issues.apache.org/jira/browse/CAMEL-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434017#comment-13434017
]
Claus Ibsen commented on CAMEL-5503:
The embedded @Header annotation seems not ideally as its confusing, and people
would mistake that for a regular @Header annotation.
Is your use-case to execute a xpath on a header?
Instead maybe we could add an attribute on the annotations to refer to a header
instead of using the body as by default
{code}
@XPath(//baz/text(), header = someHeader) String someValue
{code}
Expanding Bean Binding annotations to define explicitly what to apply it to
---
Key: CAMEL-5503
URL: https://issues.apache.org/jira/browse/CAMEL-5503
Project: Camel
Issue Type: Improvement
Reporter: Alan Foster
Priority: Trivial
Currently the bean binding annotations are applied to the body like so :
public void doSomething(@XPath(//foo/bar/text()) String someValue) {
}
It would be nice if you could specify what you want to apply it to; for
instance you could specify to apply it to headers/properties etc
In terms of annotations it may look something like:
public void doSomething(@XPath(//foo/bar/text(), @Header(someHeader))
String someValue) {
}
For backwards compatability it would of course still apply to the body by
default, but we can still offer the ability to use it apply it explicitly ie
@XPath(//baz/text(), @Body) String someOtherValue
I feel like this would be a useful addition to camel's bean binding.
If anyone feels this is a good idea, I am offering to try it out and see how
it goes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5504) Bridging http endpoints with spaces in content path causes problem when forwarding request
Claus Ibsen created CAMEL-5504:
--
Summary: Bridging http endpoints with spaces in content path
causes problem when forwarding request
Key: CAMEL-5504
URL: https://issues.apache.org/jira/browse/CAMEL-5504
Project: Camel
Issue Type: Bug
Components: camel-http, camel-jetty
Affects Versions: 2.10.0, 2.9.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.9.3, 2.10.1, 2.11.0
Having spaces in the content path in the from jetty endpoint that is being
bridged causes problem when request is forwarded.
{code}
Caused by: org.apache.camel.RuntimeExchangeException: Cannot analyze the
Exchange.HTTP_PATH header, due to: cannot find the right HTTP_BASE_URI on the
exchange: Exchange[Message: [Body is instance of org.apache.camel.StreamCache]]
at
org.apache.camel.component.http.helper.HttpHelper.createURL(HttpHelper.java:195)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5504) Bridging http endpoints with spaces in content path causes problem when forwarding request
[
https://issues.apache.org/jira/browse/CAMEL-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-5504.
Resolution: Fixed
Bridging http endpoints with spaces in content path causes problem when
forwarding request
--
Key: CAMEL-5504
URL: https://issues.apache.org/jira/browse/CAMEL-5504
Project: Camel
Issue Type: Bug
Components: camel-ahc, camel-http, camel-jetty
Affects Versions: 2.9.2, 2.10.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.9.3, 2.10.1, 2.11.0
Having spaces in the content path in the from jetty endpoint that is being
bridged causes problem when request is forwarded.
{code}
Caused by: org.apache.camel.RuntimeExchangeException: Cannot analyze the
Exchange.HTTP_PATH header, due to: cannot find the right HTTP_BASE_URI on the
exchange: Exchange[Message: [Body is instance of
org.apache.camel.StreamCache]]
at
org.apache.camel.component.http.helper.HttpHelper.createURL(HttpHelper.java:195)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5504) Bridging http endpoints with spaces in content path causes problem when forwarding request
[
https://issues.apache.org/jira/browse/CAMEL-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-5504:
---
Component/s: camel-ahc
Bridging http endpoints with spaces in content path causes problem when
forwarding request
--
Key: CAMEL-5504
URL: https://issues.apache.org/jira/browse/CAMEL-5504
Project: Camel
Issue Type: Bug
Components: camel-ahc, camel-http, camel-jetty
Affects Versions: 2.9.2, 2.10.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.9.3, 2.10.1, 2.11.0
Having spaces in the content path in the from jetty endpoint that is being
bridged causes problem when request is forwarded.
{code}
Caused by: org.apache.camel.RuntimeExchangeException: Cannot analyze the
Exchange.HTTP_PATH header, due to: cannot find the right HTTP_BASE_URI on the
exchange: Exchange[Message: [Body is instance of
org.apache.camel.StreamCache]]
at
org.apache.camel.component.http.helper.HttpHelper.createURL(HttpHelper.java:195)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5505) Unable to customize URIResolver in xslt component
Alexander Titov created CAMEL-5505: -- Summary: Unable to customize URIResolver in xslt component Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Priority: Minor In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Titov updated CAMEL-5505: --- Attachment: camel-core-xslt-CustomURIResolver.patch Test case with fix. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5503) Expanding Bean Binding annotations to define explicitly what to apply it to
[
https://issues.apache.org/jira/browse/CAMEL-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434151#comment-13434151
]
Claus Ibsen commented on CAMEL-5503:
We should strive to keep things simple and cover common uses-cases. To execute
xpaths on exchange properties and attachments is not common.
Also we should try to keep the annotations simple. The idea of the annotations
is to map to the message data, and that is 99,9% the message body and headers.
You do not so often have XML in headers, and thus why the @XPath so far covers
the message body.
We have to be careful not adding features to Camel, we end up with too much.
Expanding Bean Binding annotations to define explicitly what to apply it to
---
Key: CAMEL-5503
URL: https://issues.apache.org/jira/browse/CAMEL-5503
Project: Camel
Issue Type: Improvement
Reporter: Alan Foster
Priority: Trivial
Currently the bean binding annotations are applied to the body like so :
public void doSomething(@XPath(//foo/bar/text()) String someValue) {
}
It would be nice if you could specify what you want to apply it to; for
instance you could specify to apply it to headers/properties etc
In terms of annotations it may look something like:
public void doSomething(@XPath(//foo/bar/text(), @Header(someHeader))
String someValue) {
}
For backwards compatability it would of course still apply to the body by
default, but we can still offer the ability to use it apply it explicitly ie
@XPath(//baz/text(), @Body) String someOtherValue
I feel like this would be a useful addition to camel's bean binding.
If anyone feels this is a good idea, I am offering to try it out and see how
it goes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434152#comment-13434152 ] Hadrian Zbarcea commented on CAMEL-5505: I am looking at your patch. A quick comment, the '#' should not be there. While it's used in some context to mean a reference, in a [URI|http://www.ietf.org/rfc/rfc2396.txt] that would indicate a fragment, so I would take it out. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea reassigned CAMEL-5505: -- Assignee: Hadrian Zbarcea Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5458) Jetty/HTTP Pathless Consumer matchOnUriPrefix=true Breaks Producer bridgeEndpoint=true
[
https://issues.apache.org/jira/browse/CAMEL-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434153#comment-13434153
]
Claus Ibsen commented on CAMEL-5458:
Just thinking out loud. Maybe we need some simple way of doing light-weight
mod_rewrite. Some way of specifying url mapping ruls.
And then you can refer to that in the url configuration
.to(jetty?...mappingRules=#myMappingRules)
Jetty/HTTP Pathless Consumer matchOnUriPrefix=true Breaks Producer
bridgeEndpoint=true
--
Key: CAMEL-5458
URL: https://issues.apache.org/jira/browse/CAMEL-5458
Project: Camel
Issue Type: Bug
Components: camel-http, camel-jetty
Affects Versions: 2.10.0
Reporter: Scott England-Sullivan
Assignee: Willem Jiang
Attachments: CAMEL-5458.patch, CAMEL-5458-v2.patch,
CAMEL-5458-willem.patch, JettyMatchOnUriPrefixBridgedRouteTest.java
When a Jetty/HTTP endpoint that has the matchOnUriPrefix=true option set and
is configured to match any URI (no path is specified) the HttpHelper
concatenates the consumer path to the producer endpoint creating an
HttpOperationUnsupportedException.
For example the following will process as expected and the HttpHelper class
will create the http://localhost:10021/proxy/ping consumer URI:
{code}
from(jetty:http://localhost:10020/ping?matchOnUriPrefix=true;)
.to(jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true;);
{code}
While this code will create http://localhost:10021/proxy/ping/ping and create
the exception (the only difference is there isn't a path on the consumer):
{code}
from(jetty:http://localhost:10020?matchOnUriPrefix=true;)
.to(jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true;);
{code}
Test case and patch will be uploaded shortly.
Thanks,
Scott ES
http://fusesource.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434156#comment-13434156 ] Claus Ibsen commented on CAMEL-5505: The # is to denote a reference lookup in Camel, and is supported by any options in the URI. So Alexander is correct in his patch. For example with the file component to use a custom filter, example on web page at http://camel.apache.org/file2 Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434161#comment-13434161 ] Hadrian Zbarcea commented on CAMEL-5505: @claus, two wrongs don't make a right! I strongly encourage you to try understanding the spec. In this particular case we have an opportunity to fix things as the [xslt component|http://camel.apache.org/xslt.html] doesn't document a requirement to use the '#'. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434169#comment-13434169 ] Claus Ibsen commented on CAMEL-5505: All the components support the # reference lookup. Its to make it easy to configure endpoints! It has been link this 4+ years. Any option can use that, even types that are String etc. The # dont need to be documented in all options, as its a general idiom in Camel. There is logic in camel-core that handles this! Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434285#comment-13434285 ] Alexander Titov commented on CAMEL-5505: Hadrian, thanks for advice. Can you share some documentation or other reference about that? I agree, that there is no documentation about '#' in xslt component. I studied souce code of camel-core, particularly EndpointHelper.resolveReferenceParameter and i see that in this version of camel all # signs replased with empty string. In samples from Camel in action book beans with # called reference beans. Maybe this book is old, or this information is outdated, or somthing like that. Despite this, proplem is in createEndpoint implementation of xslt component. Currently, after parameter is set in configureXslt, it is removed from parameters Map. URIResolver resolver = resolveAndRemoveReferenceParameter(parameters, uriResolver, URIResolver.class) will allways return null, after configureXslt is called, and resolver will be always initialized to new XsltUriResolver. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5506) HBase component does not extract that table name in all cases and HBase runtime version issues.
Claudio Corsi created CAMEL-5506: Summary: HBase component does not extract that table name in all cases and HBase runtime version issues. Key: CAMEL-5506 URL: https://issues.apache.org/jira/browse/CAMEL-5506 Project: Camel Issue Type: Bug Affects Versions: 2.10.0 Environment: Any Reporter: Claudio Corsi Fix For: 2.10.1, 2.11.0 The current hbase component uses the URI getHost method to retrieve the table name but this method returns null if the host name does not conform to the requirements of this method. For instance, it should include a '.' in the name, or is a ipv4 or ipv6 valid address string. If the table name is a simple name then the getHost method will return null instead of the name of the table. This will in turn cause a NPE exception. The other issue is that if you are using 0.92.x or greater with the current implementation of the camel-hbase component. An IllegalArgumentException is generated because of an incompatible host:port pair. This is caused by the fact that the current hbase integration uses 0.90.5 and this will conflict with those versions. I have a patch that solves both issues but in the second case. It will require that the user define the specific hbase client version that they need to use. btw, the camel-hbase component is not available as an option for the Component/s drop down list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5506) HBase component does not extract that table name in all cases and HBase runtime version issues.
[ https://issues.apache.org/jira/browse/CAMEL-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claudio Corsi updated CAMEL-5506: - Attachment: hbase.diffs This is the patch that contains the fixes required for this issue. HBase component does not extract that table name in all cases and HBase runtime version issues. --- Key: CAMEL-5506 URL: https://issues.apache.org/jira/browse/CAMEL-5506 Project: Camel Issue Type: Bug Affects Versions: 2.10.0 Environment: Any Reporter: Claudio Corsi Labels: camel-hbase Fix For: 2.10.1, 2.11.0 Attachments: hbase.diffs The current hbase component uses the URI getHost method to retrieve the table name but this method returns null if the host name does not conform to the requirements of this method. For instance, it should include a '.' in the name, or is a ipv4 or ipv6 valid address string. If the table name is a simple name then the getHost method will return null instead of the name of the table. This will in turn cause a NPE exception. The other issue is that if you are using 0.92.x or greater with the current implementation of the camel-hbase component. An IllegalArgumentException is generated because of an incompatible host:port pair. This is caused by the fact that the current hbase integration uses 0.90.5 and this will conflict with those versions. I have a patch that solves both issues but in the second case. It will require that the user define the specific hbase client version that they need to use. btw, the camel-hbase component is not available as an option for the Component/s drop down list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5506) HBase component does not extract that table name in all cases and HBase runtime version issues.
[
https://issues.apache.org/jira/browse/CAMEL-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434410#comment-13434410
]
Claudio Corsi commented on CAMEL-5506:
--
BTW: This issue has the following workaround.
The table name should include at the very least a '.' in the name.
If using hbase 0.92.x or greater than they need to add the following to their
pom file.
{noformat}
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-hbase/artifactId
exclusions
exclusion
groupIdorg.apache.hbase/groupId
artifactIdhbase/artifactId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.apache.hbase/groupId
artifactIdhbase/artifactId
version${hbase-version}/version
/dependency
{noformat}
Where base.version is defined.
Note that the patch that I have attached forces the users to define the
required hbase client version.
This might not be necessary in this case since the package will not include the
hbase client and the users will need to include the runtime. Come to think
about it, you can just ignore that part of the patch and apply the rest.
Instead, state on the web site that trying to use the default hbase client with
0.92.x or greater will cause an exception.
HBase component does not extract that table name in all cases and HBase
runtime version issues.
---
Key: CAMEL-5506
URL: https://issues.apache.org/jira/browse/CAMEL-5506
Project: Camel
Issue Type: Bug
Affects Versions: 2.10.0
Environment: Any
Reporter: Claudio Corsi
Labels: camel-hbase
Fix For: 2.10.1, 2.11.0
Attachments: hbase.diffs
The current hbase component uses the URI getHost method to retrieve the table
name but this method returns null if the host name does not conform to the
requirements of this method. For instance, it should include a '.' in the
name, or is a ipv4 or ipv6 valid address string. If the table name is a
simple name then the getHost method will return null instead of the name of
the table. This will in turn cause a NPE exception.
The other issue is that if you are using 0.92.x or greater with the current
implementation of the camel-hbase component. An IllegalArgumentException is
generated because of an incompatible host:port pair. This is caused by the
fact that the current hbase integration uses 0.90.5 and this will conflict
with those versions.
I have a patch that solves both issues but in the second case. It will
require that the user define the specific hbase client version that they need
to use.
btw, the camel-hbase component is not available as an option for the
Component/s drop down list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5507) CamelBlueprintTestSupport Cannot correctly delete target\bundles\routetest.jar
Alan Foster created CAMEL-5507:
--
Summary: CamelBlueprintTestSupport Cannot correctly delete
target\bundles\routetest.jar
Key: CAMEL-5507
URL: https://issues.apache.org/jira/browse/CAMEL-5507
Project: Camel
Issue Type: Bug
Environment: Windows 7, Fuse IDE
Reporter: Alan Foster
When creating a new fuse project using the camel-blueprint archetype and
having multiple test methods it has problems deleting
'target\bundles\routetest.jar' in the setUp method of CamelBlueprintTestSupport
Reproduction steps:
- Create new fuse project from camel-blueprint archetype
- Open the RouteTest.java in
(src/test/java/com/mycompany/camel/blueprint/RouteTest.java)
- Copy the 'testRoute()' method a couple of times and give it a different
method name to best see this problem.
- Run the maven tests
The console will say this after the first test runs:
{code}
Thread-7] BlueprintCamelContext INFO Apache Camel
2.9.0.fuse-7-061 (CamelContext: blueprintContext) is shutdown in 0.005 seconds.
Uptime 0.085 seconds.
[ main] TestSupportWARN Deletion
of file:
C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles\routetest.jar
failed
[ main] TestSupportWARN Deletion
of file: C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles
failed
[ main] TestSupportWARN Deletion
of file:
C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles\routetest.jar
failed
[ main] TestSupportWARN Deletion
of file: C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles
failed
[ main] TestSupportWARN Deletion
of file:
C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles\routetest.jar
failed
[ main] TestSupportWARN Deletion
of file: C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles
failed
[ main] TestSupportWARN Deletion
of file:
C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles\routetest.jar
failed
[ main] TestSupportWARN Deletion
of file: C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles
failed
[ main] TestSupportWARN Deletion
of file:
C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles\routetest.jar
failed
[ main] TestSupportWARN Deletion
of file: C:\FuseIDEEnterprise-2.1.462\workspace\camel-blueprint\target\bundles
failed
[ main] CamelBlueprintHelper INFO Using
Blueprint XML file:
/C:/FuseIDEEnterprise-2.1.462/workspace/camel-blueprint/target/classes/OSGI-INF/blueprint/blueprint.xml
{code}
You can also also get PojoSR class loader issues when running the exact same
project as JUnit tests, rather than maven tests. But these errors may be
related so I won't raise a ticket for that.
I will however give the stack trace for this, in case it _isn't_ related
{code}
org.osgi.framework.BundleException: Unable to start bundle
at
de.kalpatec.pojosr.framework.PojoSRBundle.start(PojoSRBundle.java:144)
at de.kalpatec.pojosr.framework.PojoSR.startBundles(PojoSR.java:405)
at de.kalpatec.pojosr.framework.PojoSR.init(PojoSR.java:322)
at
de.kalpatec.pojosr.framework.PojoServiceRegistryFactoryImpl.newPojoServiceRegistry(PojoServiceRegistryFactoryImpl.java:51)
at
org.apache.camel.test.blueprint.CamelBlueprintHelper.createBundleContext(CamelBlueprintHelper.java:111)
at
org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at
[jira] [Work started] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-5505 started by Hadrian Zbarcea. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434502#comment-13434502 ] Hadrian Zbarcea commented on CAMEL-5505: Alexander, I understand what you wanted to do and why. From one point of view Claus is somewhat right in his statement that you are correct in this patch in the sense that you followed the same pattern in use in Camel today. My statement was that the logic in camel-core is flawed and not using '#' means one less place to clean up in the future. As you point out, the 'logic' in camel-core is kinda random, replacing chars with other chars, thus creating undocumented and even unknown to us edge cases that pop up a lot lately. There are other flaws, like adding the extra '//' thus not allowing for urns at all, and others. The fact that it stayed like this for 4+ years is imho not an assurance that it's correct. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434750#comment-13434750 ] Hadrian Zbarcea commented on CAMEL-5505: Patch applied. Will see tomorrow if I can improve the '#' usage. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5458) Jetty/HTTP Pathless Consumer matchOnUriPrefix=true Breaks Producer bridgeEndpoint=true
[
https://issues.apache.org/jira/browse/CAMEL-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434786#comment-13434786
]
Scott England-Sullivan commented on CAMEL-5458:
---
I was trying to accomplish the same effect without changing the component using
a distribution list. I think your suggestion is cleaner though.
I will take a look at it next week when I get back in town. At a customer site
this week.
Jetty/HTTP Pathless Consumer matchOnUriPrefix=true Breaks Producer
bridgeEndpoint=true
--
Key: CAMEL-5458
URL: https://issues.apache.org/jira/browse/CAMEL-5458
Project: Camel
Issue Type: Bug
Components: camel-http, camel-jetty
Affects Versions: 2.10.0
Reporter: Scott England-Sullivan
Assignee: Willem Jiang
Attachments: CAMEL-5458.patch, CAMEL-5458-v2.patch,
CAMEL-5458-willem.patch, JettyMatchOnUriPrefixBridgedRouteTest.java
When a Jetty/HTTP endpoint that has the matchOnUriPrefix=true option set and
is configured to match any URI (no path is specified) the HttpHelper
concatenates the consumer path to the producer endpoint creating an
HttpOperationUnsupportedException.
For example the following will process as expected and the HttpHelper class
will create the http://localhost:10021/proxy/ping consumer URI:
{code}
from(jetty:http://localhost:10020/ping?matchOnUriPrefix=true;)
.to(jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true;);
{code}
While this code will create http://localhost:10021/proxy/ping/ping and create
the exception (the only difference is there isn't a path on the consumer):
{code}
from(jetty:http://localhost:10020?matchOnUriPrefix=true;)
.to(jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true;);
{code}
Test case and patch will be uploaded shortly.
Thanks,
Scott ES
http://fusesource.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5505) Unable to customize URIResolver in xslt component
[ https://issues.apache.org/jira/browse/CAMEL-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434814#comment-13434814 ] Alexander Titov commented on CAMEL-5505: Ahh, i got it. But how can we today set reference property (lookup in registry) in URI? Without # i got exception: org.apache.camel.FailedToCreateRouteException .. Caused by: java.lang.IllegalArgumentException: Could not find a suitable setter for property: uriResolver as there isn't a setter method with same type: java.lang.String nor type conversion possible: No type converter available to convert from type: java.lang.String to the required type: javax.xml.transform.URIResolver with value uriResolver at org.apache.camel.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:347) at org.apache.camel.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:367) at org.apache.camel.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:297) at org.apache.camel.util.EndpointHelper.setProperties(EndpointHelper.java:249) at org.apache.camel.impl.DefaultComponent.setProperties(DefaultComponent.java:222) at org.apache.camel.component.xslt.XsltComponent.configureXslt(XsltComponent.java:145) at org.apache.camel.component.xslt.XsltComponent.createEndpoint(XsltComponent.java:124) at org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:91) at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:450) ... 33 more I will look in other components to see, how i can lookup beans in registry. Thanks for help. Unable to customize URIResolver in xslt component - Key: CAMEL-5505 URL: https://issues.apache.org/jira/browse/CAMEL-5505 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.0, 2.11.0 Reporter: Alexander Titov Assignee: Hadrian Zbarcea Priority: Minor Labels: camel-core,, test, xslt Attachments: camel-core-xslt-CustomURIResolver.patch In xslt component we can't customize uriResolver For instance in route with uri xslt:org/apache/camel/component/xslt/include_not_existing_resource.xsl?uriResolver=#customURIResolver camel still uses default XsltUriResolver. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
