Hi,
I’ve got a Camel project which is to be deployed into servicemix as an
OSGi-bundle where I’ve embedded a couple of third-party jars in the bundle.
This works nicely.
However, the class path to these bundles is set in MANIFEST.MF which is not
generated until *after* tests are run if I do a
tp://camel.465427.n5.nabble.com/Camel-Testing-JTA-java-sql-SQLSyntaxErrorException-ORA-02049-timeout-distributed-transaction-waitingk-tp5756981p5756985.html
Sent from the Camel - Users mailing list archive at Nabble.com.
please?
Thanks in advance!
Matt'M
-
Thanks
Matt G. Madhavan
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Testing-JTA-java-sql-SQLSyntaxErrorException-ORA-02049-timeout-distributed-transaction-waitingk-tp5756981.html
Sent from the Camel - Users mailing
Thinking more about this, I've just realised what the obvious thing I'm missing
here is: my project uses source code from the package, which is tested with its
tests - duh!
Blindingly obvious to myself now why I'm getting the compile error.
Sorry about that,
Carl.
I've noticed that the package camel-scala contains the abstract class
ScalaTestSupport under its test directory. As such, I'm wondering if it's
possible to use this class within my own Apache Camel tests?
I'm using Scala 2.10 and Apache Camel 2.11 and code is maintained/managed using
SBT versio
Thanks a lot!
Vlad
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-testing-tp5736444p5736579.html
Sent from the Camel - Users mailing list archive at Nabble.com.
mockEndpoints();
> }
> });
>
>
> String sendbody = "";
> String expectedBody = "";
>
> MockEndpoint mockEndpoint =
> getMockEndpoint("mock:jms:queue:msb.2761100008.invoice");
> mockEndpoint.expectedBodiesReceived(expectedBody);
&
}
@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new MyRouteBuilder();
}
}
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-testing-tp5736444p5736480.html
Sent from the Camel - Users mailing list archive at Nabble.com.
t: Dienstag, 30. Juli 2013 05:10
> An: users@camel.apache.org
> Betreff: Re: Camel testing
>
> So keep in mind that the "endpoints" to a route are just
> java.lang.String... So you can do:
>
> String startRoute = "jms:incoming";
> String endRoute = "jms:outgoin
e put a message into the input queue of the router with
> another test Router (from file to queue)
>- i've taken the message from output queue of the router
> with
> a test router (From message to file)
>- compare the file with an expected one.
of the router with
a test router (From message to file)
- compare the file with an expected one.
But this is bad as concept for unit tests (let s say Junits), i think.
4. Do you a link, or something to a generic test example of a camel route?
PS: Sorry if the are stupid quest
de my doStart() method, to
avoid calling getProcessor().process(exchange) before the services had been
started.
Hope this helps someone in a similar situation.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Testing-Framework-tp4631765p4635585.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Can you show us the full version of Camel route configure?
There is no any mock endpoint which is named with "mock://static" in the
route.
I can't tell what is wrong base on your description :(
On 7/26/11 1:57 AM, Kaul, Prerna wrote:
Hi,
I am trying to use the Camel Spring Junit test framew
Hi,
I am trying to use the Camel Spring Junit test framework. I have defined a
route which has a polling consumer(not "direct:start" but
"myComponent:parameters") and a mock processor endpoint ("mock:result"), using
Spring DSL.
When I start the Junit test, I receive the er
Hi
Yeah you should be able to use the Spring Test framework with Camel.
Just do as you normally do with Spring testing.
Then you can use Spring IoC to inject ProducerTemplate and Endpoint so you
can use those Camel concepts from the unit test class.
See more here:
http://camel.apache.org/spring-
Hi all:
I'm familiar with a common practice in Spring to create a unit test
sub-classing AbstractTransactionalJUnit4SpringContextTests. Then in your
@Before's, you setup the data in the database for your unit test. And in
your @Test's you can test your code that expects the data in the databa
16 matches
Mail list logo