camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Doyle <markjohndo...@gmail.com>
Subject Re: Period character issue with camel-mongo.
Date Wed, 03 Oct 2012 21:23:50 GMT
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
at
org.apache.camel.impl.DefaultCamelContext.addComponent(DefaultCamelContext.java:291)
at
org.apache.camel.component.mongodb.MongoDbOperationsTest$1.configure(MongoDbOperationsTest.java:227)
at
org.apache.camel.builder.RouteBuilder.checkInitialized(RouteBuilder.java:322)
at
org.apache.camel.builder.RouteBuilder.configureRoutes(RouteBuilder.java:276)
at
org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:262)
at
org.apache.camel.impl.DefaultCamelContext.addRoutes(DefaultCamelContext.java:633)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:293)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

java.lang.NullPointerException
at
org.apache.camel.component.mongodb.AbstractMongoDbTest.cleanup(AbstractMongoDbTest.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)


On 2 October 2012 21:26, Mark Doyle <markjohndoyle@gmail.com> wrote:

> 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
>
> Which I assume triggers the fromAnyObjectToDBObject method in the
> MongoDbBasicConverters class? The qualified name field always contains
> periods.
>
>
> On 2 October 2012 20:11, Raul Kripalani <raul@evosent.com> wrote:
>
>> 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 I know this component inside out because I created it ;)
>>
>> There are a number of type converters that MongoDB provides... What's the
>> original payload type before it hits the MongoDB endpoint? (Object,
>> HashMap, etc.). I assume it's an Object but please confirm.
>>
>> Thanks,
>>
>> --
>> *Raúl Kripalani*
>> Apache Camel Committer
>> Enterprise Architect, Program Manager, Open Source Integration specialist
>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>> http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>
>>
>>
>> On Tue, Oct 2, 2012 at 4:22 PM, Mark Doyle <markjohndoyle@gmail.com>
>> wrote:
>>
>> > I have a problem where a String field contains a period. This causes the
>> > following exception:
>> >
>> > Caused by: java.lang.IllegalArgumentException: fields stored in the db
>> > can't have . in them. (Bad Key: 'Stock6.tm.Azimuth')
>> >
>> > which I believe stems from restrictions in the depths of the mongo!
>> >
>> > The solution seems to be to convert the character to something else
>> (e.g. a
>> > comma) before inserting and back again after finding. Does this seem
>> like
>> > something the camel-mongo component should offer as an option, or even
>> > silently deal with by default? Could it be a change in the type
>> converters?
>> > I think that uses Jackson to build the DB object and therefore could
>> filter
>> > out and replace periods. I suppose a user could run into problems if
>> they
>> > overrode the converters with their own.
>> >
>> > I don't know how camel works under the covers so this might not work,
>> > especially if the converters aren't used to create a real object from
>> > the DBObject returned by Mongo.
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message