Hide Forgot
Created attachment 819637 [details] EAP 6.1 configuration Description of problem: When trying to use Camel Bindy inside a SwitchYard component I get a NullPointerException. Version-Release number of selected component (if applicable): How reproducible: Always, both as a unit test and also during deployment in the container Steps to Reproduce: 1. Execute mvn test 2. 3. Actual results: File is not processed Expected results: File is processed Additional info: Attached you can find: - EAP 6.1 configuration (including modules) - The project source code - Log file with the exeception For in-container test drop the test.csv into the /tmp folder
Created attachment 819638 [details] Project using Camel Bindy
Created attachment 819639 [details] Log file
A special JBoss resolver should be added before Camel is started, i.e. either OOTB or by adding a possibility in SwitchYard to add it before the CamelContext is initialized by SwitchYard.
I have a fix for this and it will be in today.
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1830 to Resolved
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1830 pushed
Created attachment 823066 [details] updated app
Created attachment 823067 [details] camel bindy module
Once this is available in the product build, all you have to do is: 1) add the Camel bindy extension to your AS modules directory (see attached bindy-module.zip) 2) configure standalone.xml to use the org.apache.camel.bindy extension in the switchyard subsystem configuration: <subsystem xmlns="urn:jboss:domain:switchyard:1.0"> <!-- snip --> <extensions> <!-- snip --> <extension identifier="org.apache.camel.bindy"/> </extensions> 3) Deploy the revised application (updated-app.zip). Similar to the original example, but I removed some dependency definitions which are not required.
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1830 to Closed