Re: Camel with embedded ActiveMQ / Web-Console

2017-05-10 Thread burner
I get it now to work, but only when I make "mvn camel:run". But I want "mvn package". Knows anyone, what I must do? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-with-embedded-ActiveMQ-Web-Console-tp5798586p5799238.html Sent from the Camel - Users mailing list

Camel with embedded ActiveMQ / Web-Console

2017-05-03 Thread burner
wish to work? Thank you for any Ideas, or links. Burner -- View this message in context: http://camel.465427.n5.nabble.com/Camel-with-embedded-ActiveMQ-Web-Console-tp5798586.html Sent from the Camel - Users mailing list archive at Nabble.com.

Add my own Filter on http4?

2015-12-16 Thread burner
Hello together, i want to use a own headerFilterStrategy on my own Component extends from http4. So I create this class: public class DefaultHeaderFilterStrategy extends HttpHeaderFilterStrategy { public DefaultHeaderFilterStrategy() { super();

Re: Add my own Filter on http4?

2015-12-16 Thread burner
I found the Error! All cases must be lower! so this work: getOutFilter().add("messagehistory"); This don't work: getOutFilter().add("MessageHistory"); -- View this message in context: http://camel.465427.n5.nabble.com/Add-my-own-Filter-on-http4-tp5775147p5775152.html Sent from the Camel -

Re: Dynamic datasource with Camel 2.15.x

2015-10-13 Thread burner
Thank you for your help. But I don't get it to run. I think this is also a too complex way. I solve my problem now with subclassing the JDBC Component and insert there my Code. Now my Component creates the DataSource on basis of Parameters. -- View this message in context:

Re: Dynamic datasource with Camel 2.15.x

2015-10-06 Thread burner
Hello Joakim, yes, I am use Spring. your Idea look good. But how can I use parameters in your solution? @Configuration public class InfrastructureConfig { String username = ""; String password = ""; String url = ""; @Bean public DataSource dataSource() { String

Dynamic datasource with Camel 2.15.x

2015-10-02 Thread burner
Hello Together, i want to create dynamic datasources on runtime. I found some examples to do this. But this code: PropertyPlaceholderDelegateRegistry registry = (PropertyPlaceholderDelegateRegistry) getContext().getRegistry(); JndiRegistry jndiRegistry = (JndiRegistry ) registry.getRegistry();

Re: Own Component with optional Parameters

2015-09-24 Thread burner
I add this to *CsvToXmlEndpoint.java:* public CsvToXmlEndpoint(String endpointUriString, Component component) { super(endpointUriString, new CsvToXmlComponent()); try { this.setPropertiesToProcessor(); }

Own Component with optional Parameters

2015-09-24 Thread burner
Hello Together, I wrote a custom component for Camel 2.15.3. This component extends from DefaultComponent and work if I put parameters in the URI, but without Parameters I get following Error Message: org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method invocations

Re: Own Component with optional Parameters

2015-09-24 Thread burner
*CsvToXmlComponent.java:* public final class CsvToXmlComponent extends DefaultComponent { private static final Logger LOG = LoggerFactory.getLogger(CsvToXmlComponent.class); @Override protected CsvToXmlEndpoint createEndpoint(String uri, String remaining,

Re: Own Component with optional Parameters

2015-09-24 Thread burner
Still the same Error: Ambiguous method invocations possible: [public org.apache.camel.EndpointConfiguration org.apache.camel.impl.DefaultComponent.createConfiguration(java.lang.String) throws java.lang.Exception, public org.apache.camel.Endpoint

Re: Own Component with optional Parameters

2015-09-24 Thread burner
Why? If the Component don't need parameters, so why I must insert someone? -- View this message in context: http://camel.465427.n5.nabble.com/Own-Component-with-optional-Parameters-tp5771889p5771915.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Own Component with optional Parameters

2015-09-24 Thread burner
still the same error. I don't think this is a problem in my Component. I think this is a problem in the defaultComponent or in a other camel core component. The Error tells, java cannot decide which of the Method createConfiguration to use in org.apache.camel.EndpointConfiguration or in