• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • Integration Modules
  • hhuynh
  • Reporter: amiller
  • April 02, 2008
  • 0
  • Watchers: 0
  • October 02, 2008
  • April 02, 2008

Description

I think this may only be possible when specifying a module programmatically as the config schema should require it, but the resolver blindly assumes the version is not null which then results in this:

2008-04-01 16:05:12,258 [Thread-17] ERROR com.tc.plugins.ModulesLoader - Exception thrown java.lang.NullPointerException at com.tc.bundles.Resolver.findJars(Resolver.java:148) at com.tc.bundles.Resolver.resolveLocation(Resolver.java:234) at com.tc.bundles.Resolver.resolve(Resolver.java:108) at com.tc.bundles.Resolver.resolve(Resolver.java:126) at com.tc.plugins.ModulesLoader.initModules(ModulesLoader.java:145) at com.tc.plugins.ModulesLoader.initModules(ModulesLoader.java:95) at com.tc.object.bytecode.hook.impl.DSOContextImpl.(DSOContextImpl.java:88) at com.tc.object.bytecode.hook.impl.DSOContextImpl.createContext(DSOContextImpl.java:72) at com.tc.object.loaders.IsolationClassLoader.init(IsolationClassLoader.java:63) at com.tc.simulator.app.DSOApplicationBuilder.initializeClassLoader(DSOApplicationBuilder.java:90) at com.tc.simulator.app.DSOApplicationBuilder.newApplication(DSOApplicationBuilder.java:70) at com.tc.simulator.container.Container.newExecutionInstance(Container.java:198) at com.tc.simulator.container.Container.startInstances(Container.java:212) at com.tc.simulator.container.Container.run(Container.java:98) at java.lang.Thread.run(Thread.java:613)

I’ve repro’ed in a unit test. Fix coming soon.

Comments

Alex Miller 2008-04-02

Fixed to throw useful message if name or version of module spec is null.