[jira] [Commented] (CAMEL-5483) Component for neo4j
[ https://issues.apache.org/jira/browse/CAMEL-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440092#comment-13440092 ] Claus Ibsen commented on CAMEL-5483: Stephen, have you created an account on the wiki? Read this page http://camel.apache.org/how-do-i-edit-the-website.html 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=13440173#comment-13440173 ] stephen samuel commented on CAMEL-5483: --- I sure have Full Name stephen samuel Email samspad...@gmail.com 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-5477) Camel component contribution for CouchDB
[ https://issues.apache.org/jira/browse/CAMEL-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440175#comment-13440175 ] stephen samuel commented on CAMEL-5477: --- I wondered if there are plans to include this in 2.11 or perhaps 2.12 ? Camel component contribution for CouchDB Key: CAMEL-5477 URL: https://issues.apache.org/jira/browse/CAMEL-5477 Project: Camel Issue Type: Improvement Reporter: stephen samuel Priority: Minor Fix For: 2.11.0 Attachments: camel-couchdb.patch Patch for my contribution for camel couchdb component. -- 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-5537) Mina2 Consumer doesn't reliably work with SSL
Andrew Lawrenson created CAMEL-5537: --- Summary: Mina2 Consumer doesn't reliably work with SSL Key: CAMEL-5537 URL: https://issues.apache.org/jira/browse/CAMEL-5537 Project: Camel Issue Type: Bug Components: camel-mina2 Affects Versions: 2.10.0 Reporter: Andrew Lawrenson I've been trying to write a service using Camel 2.10.0 which uses the mina2 component to expose a service, and which uses SSL, using an endpoint of: mina2:tcp://localhost:6500?sync=truefilters=#hl7SslFilterFactory,#hl7CodecFilterallowDefaultCodec=false however, what I found was that the SSL handshake was failing quite often for no apparent reason. Investigating further, it appeared that messages sent during the handshake were being processed out of order - specifically, when the client (which uses a standard java SSLSocket) sent a TLSv1 Change Cipher Spec followed by a TLSv1 Handshake, the TLSv1 Handshake was being processed before the TLSv1 Change Cipher Spec, breaking the process. This appears to have been caused because when the the Mina2Consumer configures MINA for tcp (in Mina2Consumer.setupSocketProtocol), it is using a UnorderedThreadPoolExecutor - which allows messages to be processed in any order. Switching this to use a OrderedThreadPoolExecutor instead has fixed the issue. May I request that the use of UnorderedThreadPoolExecutor vs OrderedThreadPoolExecutor be configurable via endpoint parameters? (or OrderedThreadPoolExecutor is used when SSL if configured). I'm assuming the reason for the use of UnorderedThreadPoolExecutor is simply for performance. -- 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-5538) Add skipFaultLogging option to disable the Fault logging in PhaseInterceptorChain
Willem Jiang created CAMEL-5538: --- Summary: Add skipFaultLogging option to disable the Fault logging in PhaseInterceptorChain Key: CAMEL-5538 URL: https://issues.apache.org/jira/browse/CAMEL-5538 Project: Camel Issue Type: New Feature Components: camel-cxf Environment: Its a valid use-case to have camel-cxf / CXF act as a web service server, and in case of errors etc, return back a Soap Fault. But its not good that CXF always logs a big stacktrace at WARN level. skipFaultLogging option can help user to disable the default fault logging. Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.11.0 -- 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-5535) Multiple restlet routes of the same restlet URI but different VERBs does not work in Apache Camel 2.10.0 , both routes work in Apache Camel 2.9.1.
[
https://issues.apache.org/jira/browse/CAMEL-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440576#comment-13440576
]
Amit Patel commented on CAMEL-5535:
---
I did the unit test with Camel 2.10.0 and Camel 2.9.1 and i got same exception,
but when I deploy same routes in spring XML DSL format into out application. It
works fine with Camel 2.9.1. Both routes started successfully. I went to
jconsole and collected dumpRouteAsXml. Below are the dumpRouteAsXml. Both
routes has different route id but same URL. This feature is very critical to
Restlet routes, so we can have different routes base on the restletMethods. Is
anyway could you support this feature in next release?
?xml version=1.0 encoding=UTF-8 standalone=yes?
route trace=true id=nimbus.hello.restlet.1.0
xmlns=http://camel.apache.org/schema/spring;
from uri=restlet:///nimbus/hello.restlet/1.0?restletMethods=post/
transform id=transform10
simpleHello Restlet Method: ${header.CamelHttpMethod}
ID:${header.id}/simple
/transform
/route
?xml version=1.0 encoding=UTF-8 standalone=yes?
route trace=true id=nimbus.hello.restletGet.1.0
xmlns=http://camel.apache.org/schema/spring;
from uri=restlet:///nimbus/hello.restlet/1.0?restletMethods=get/
transform id=transform9
simpleHello Restlet Method: ${header.CamelHttpMethod}
ID:${header.id}/simple
/transform
/route
Thanks,
Multiple restlet routes of the same restlet URI but different VERBs does not
work in Apache Camel 2.10.0 , both routes work in Apache Camel 2.9.1.
Key: CAMEL-5535
URL: https://issues.apache.org/jira/browse/CAMEL-5535
Project: Camel
Issue Type: Bug
Components: camel-restlet
Affects Versions: 2.10.0
Reporter: Amit Patel
Assignee: Willem Jiang
Multiple restlet routes of the same restlet URI but different VERBs does not
work in Apache Camel 2.10.0 , both routes work in Apache Camel 2.9.1.
Reproduce Steps:
-
1) Add a restlet route with a from uri of
restlet:///nimbus/hello.restlet/1.0?restletMethods=get
route xmlns=http://camel.apache.org/schema/spring; trace=true
from uri=restlet:///nimbus/hello.restlet/1.0?restletMethods=get/
transform
simpleHello Restlet Method: ${header.CamelHttpMethod}
ID:${header.id}/simple
/transform
/route
2) Add a restlet route with a from uri of
restlet:///nimbus/hello.restlet/1.0?restletMethods=post
route xmlns=http://camel.apache.org/schema/spring; trace=true
from uri=restlet:///nimbus/hello.restlet/1.0?restletMethods=post/
transform
simpleHello Restlet Method: ${header.CamelHttpMethod}
ID:${header.id}/simple
/transform
/route
3) route 1work fine, but #2 results in the following exception. both route
work fine in Camel 2.9.1.
Exception:
012-07-27 10:29:20,646-0400 ERROR grails.app.service.nimbus.ComputeService
localhost addRoute for hello.restletpost failed - Failed to start route
nimbus.hello.restletpost.1.0 because of Multiple consumers for the same
endpoint is not allowed: Endpoint[/nimbus/hello.restlet/1.0]
Caused by: org.apache.camel.FailedToStartRouteException: Failed to start
route nimbus.hello.restletpost.1.0 because of Multiple consumers for the same
endpoint is not allowed: Endpoint[/nimbus/hello.restlet/1.0]
at
org.apache.camel.impl.DefaultCamelContext(doStartOrResumeRouteConsumers:1993)
I've already posted on
http://camel.465427.n5.nabble.com/Apache-Camel-2-10-0-multiple-restlet-routes-of-the-same-restlet-URI-but-different-VERBs-does-not-work-td5716556.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
