[GORA-95] Catch incorrect mapping configurations and implement sufficient logging.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.2
• Fix Version/s: 0.3
• Component/s: gora-cassandra, testing
• Assignee: Unassigned
• Reporter: Lewis John McGibbney
• Created: 18/Feb/12 22:15
• Updated: 01/Jul/13 05:05
• Resolved: 18/May/12 11:40

Description

Whilst (pulling my hair out) writing the cassandra test suite, after many failing tests and some debugging I noticed that, under many InvocationTargetException's, CassandraMapping#loadConfiguration() throws the following

Caused by: java.lang.NullPointerException
at org.apache.gora.cassandra.store.CassandraMapping.loadConfiguration(CassandraMapping.java:100)
at org.apache.gora.cassandra.store.CassandraClient.init(CassandraClient.java:66)
at org.apache.gora.cassandra.store.CassandraStore.<init>(CassandraStore.java:72)
... 43 more

when it cannot load the correct configuration from gora.properties. I know it is not great practice to put the while method in a try catch block so would be good to work towards a better solution.