-
2. Re: SLF4J
I'm aware this is not the SLF4J bashing forum; moreover since the introduction of SLF4J
into ActiveMQ and subsequently Camel, I can say with certainty "UGH!"
Ill delete this message in a day or so, I won't bore you with the details; most of them are in JIRA and exposed/reported in all forward and reverse compatibility reports.
Least to say, sometimes incompatibility, other times no logging at all and most of the time (I really like the informative message below which imo\means) "there is a problem somewhere, but this new fancy facade pattern has decided to eat it".
""Caused by: java.lang.NullPointerException
at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.checkOverrideProperties(Unknown Source)"
"
Take care, again thanks for the great work on Camel!
-
3. Re: SLF4J
Turns out to be a bug w/Spring 3.0.X which ships w/Camel 3.9. Removing the camel/spring .jars and replacing w/spring 3.1 corrects the problem.
Inconsistently the main() would produce below:
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource
Sorry to have trash talked SLF4J. Although the forward/backward version comparability is still a problem. Great work w/camel,spring,amq integration, really enjoy the new IDE too!
-
5. Re: SLF4J
Good to hear you got it sorted.
Yeah you can be in the dark if the log kit doesn't startup properly and exceptions is not logged in the usual log files.
In terms of the cards, then I am sure we hand them out at the upcoming Fuse Community days in London or Paris. And other events to come.
If you want a card send, then you can try to use the contact us and get in touch with us.
Or keep an eye on the website, or blogs, as maybe something is in the works