I'm seeing a class cast exception in GeneratedPackageDescriptorImpl.getEPackage() on the line: ePackage = (EPackage) eInstance.get(null);
The reason I've concluded is that many of the EMF jars are needed in TC's common\lib and they also seem to be in the samples war's WEB-INF\lib and resulting in some classes being loaded by TC's StandardClassLoader and instances also loaded by TC's webapp classloader. But then they're not the same class and results in a classcast exception. Locally I've eliminated the ones in the sample's war and the exception went away. I guess this can work now as a solution if maven can be coerced not to package them. But in the long run I think webapps need to be able to have their version's of these jars. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
