Re: How to get properties working in camelTest and spring

I finally got my JUnit-Tests working and the properties are correctly injected now. I did it with a lot of annotations: @RunWith(CamelSpringJUnit4ClassRunner.class) @SpringApplicationConfiguration(classes = MyServiceTests.class) @ActiveProfiles("test") @EnableAutoConfiguration @ComponentScan

How to get properties working in camelTest and spring

I have a problem with the property-mechanism in JUnit-Tests. In my application I just have to annotade my config-class to use property placeholders. @Configuration @PropertySource("classpath:my.properties") public class MyServiceConfigurator extends WsConfigurerAdapter { ... } Afterwards I can

Re: Spring Boot WS - After receiving request, camel throws NullPointerException

Thanks a lot, Claus. Will this fix be i the new camel version, or where do I get the fix then? -- View this message in context: http://camel.465427.n5.nabble.com/Spring-Boot-WS-After-receiving-request-camel-throws-NullPointerException-tp5772930p5772936.html Sent from the Camel - Users mailing

Spring Boot WS - After receiving request, camel throws NullPointerException

Hi guys, recently I try to expose a SOAP-WS with Spring-Boot and Camel, on Glassfish-4.0. I send my requests via SOAP-UI and they'll be received sucessfully by the WS. I can see the messages in the log-files but then camel throws a NullPointerException. More specific, the

Re: Bean invocation .class vs new

No ideas? Anyone? -- View this message in context: http://camel.465427.n5.nabble.com/Bean-invocation-class-vs-new-tp5764039p5765004.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Bean invocation .class vs new

I have to ask further questions, because the caching process is still unclear. We use camel to realize a servlet request-response scenario. It is multithreaded, therefore we are a little worried about following situation: There are several incoming requests at the same time and all of them use

Re: Bean invocation .class vs new

Hey Claus, thank you I got it now. -- View this message in context: http://camel.465427.n5.nabble.com/Bean-invocation-class-vs-new-tp5764039p5764217.html Sent from the Camel - Users mailing list archive at Nabble.com.

Bean invocation .class vs new

Hi Guys, according to the camel documentation I have two different options to invoke a method of a bean. /// Explicit selection of bean method to be invoked. from(direct:start).bean(new ExampleBean(), methodName); // Camel will create the instance of bean and cache it for you.

Re: Bean invocation .class vs new

Hi Claus, thank you for your answer. What if I do the following: .bean(new MyBeanA(), doMyBeanA) .bean(MyBeanB.class, doMyBeanB) .bean(new MyBeanA(), doMyBeanA2) Do I get two instances of MyBeanA? If not, how is the syntax if I want to reuse MyBeanA in the third line? You say the bean

Re: CamelContextLifecycle causes ClassNotFoundException when compiled with java 1.7

Hi Willem, thanks for your reply. I use maven to define my source and target, and both are 1.7. According to the link it read that camel supports Java 1.7 since version 2.10, and it is required from 2.14 onwards. We are going to use camel 2.14 soon, so i guess i just wait and use Java 1.6 until

CamelContextLifecycle causes ClassNotFoundException when compiled with java 1.7

Hi, I'm using camel 2.13.0 and WebLogicServer 10.3.6 for my application. Also I use the CamelContextLifecycle and there is where the exception occurs. Everything works well if I compile with Java 1.6, but if I use Java 1.7 this Exception occurs during the startup process of the ManagedServer:

Re: CXF Endpoint accepts invalid SOAP-Envelope in POJO-Mode

Hi Aki, we were also astonished first. It took some time to realize that it's just the element-name. Thank you for your help. We will try it again when the issue is fixed. Regards -- View this message in context:

CXF Endpoint accepts invalid SOAP-Envelope in POJO-Mode

Hello, we developed a webservice with cxf and camel. Everything works fine, except the fact that the cxf-endpoint accepts invalid SOAP-Messages. For example we have a SOAP-Message: SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Header ...

create SOAP-Fault with exception message included

Hi, in my camel-route i want to send a soap-fault as response in case of exception. My Problem is i don't know how to create a SOAP-Fault using the SOAPJaxbDataFormat. Currently i use this code: private class ExceptionResponse implements Processor { @Override public void

Re: Validator in camel route shows strange error message

Hi, I'm running this route in a web-container on glassfish 4.0. I'm also using the CamelContextLifeCycle for initialization purposes. When i use a processor in the camel route, with schemaFactory and validator from the java api in the process method, it works. -- View this message in context:

Re: Validator in camel route shows strange error message

I tested it with another schema file, and the test successfully passed. The original schema file has many includes and the included files also have many includes, consequently there are lots of references to resolve. Could it be a streaming issue or similar? -- View this message in context:

Validator in camel route shows strange error message

Hi, I'm using the java DSL to configure a camel route. After getting XML via servlet i want to validate the message against a schema, using the validator component. Everything works fine, except the validation process. My route configuration: from(servlet:///foo?servletName=bar)