Yeah, that works fine.
I've created a test that reproduces the problem. I think it can only occur
when an Object has a Map as a field. This is the only way we can get a
period into something Mongo uses as a key (I'm guesstimating here) since
fields names themselves obviously can't use a period.
I
Yes, I read about the cloud idea on the dev mailing list :)
It looks like you were correct. I changed the camel-test-spring dependency
to 2.10.0 as follows:
org.apache.camel
camel-test-spring
2.10.0
test
The tests now work. It looks like the change happened in the move
Hi Mark,
I just committed a fix for the tests in r1394865. It turns out that the
PropertiesComponent was being added too late in the route lifecycle, which
worked before r1373402, but not after.
You should now be able to run the tests locally simply by starting MongoDB.
The tests are prepared to
Apologies for not being able to look at this yesterday. Thanks for all the
feedback from your side.
Unfortunately the unit tests of this component are disabled on our Jenkins
because MongoDB is not embeddable and our unit tests are really
"integration tests" from the purist point of view, because
I have a little more info.
The properties issue is evident on both the command line (mvn install) and
running the junit test directly in elipse.
I tried the spring 3.1 profile on the command line (mvn clean install -P
spring3.1) and got the same problem.
What is weird is it suddenly stopped find
Strange, will check this evening and will send you a direct email with my
findings.
Thanks for your collaboration ;)
Regards,
*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/i
Hi Raul,
I'm getting the trace below when I try to run the unit tests. Looks like a
problem adding the Properties component (using mongdb.test.properties) to
the camel spring context. Any ideas?
java.lang.IllegalArgumentException: Cannot add component as its already
previously added: properties
a
Indeed I would; first job is to figure out how to create a JIRA...
as for your question, yes, you assume correctly. It's the following simple
model object:
https://github.com/JohannesKlug/hbird/blob/master/src/core/commons/src/main/java/org/hbird/core/commons/tmtcgroups/HummingbirdParameter.java
Hi Mark,
Correct. Mongo doesn't accept dot characters in field naming because it
serves as a separator for nested fields, so it's reserved.
It seems like a great idea. Please feel free to create a JIRA. Would you be
happy to work on a patch? If you want I can provide you with some guidance
since
