[ http://issues.apache.org/jira/browse/IBATIS-322?page=comments#action_12420447 ]
Jeff Butler commented on IBATIS-322: ------------------------------------ After I wrote my previous comment, I got to wondering - "why isn't iBATIS totally consistent about creating objects? Turns out we're only using Class.forName() in a handful of situations, and there is no reason to do it that way. I'll make the change so that we consistently use the methods in the Resources class. By the way - the default behavior for that class is to do exactly what's described - so it might solve the issue completely. > Classloader problems in some environments. > ------------------------------------------ > > Key: IBATIS-322 > URL: http://issues.apache.org/jira/browse/IBATIS-322 > Project: iBatis for Java > Type: Improvement > Components: SQL Maps, DAO > Environment: netbeans platform > Reporter: Andrey > Assignee: Jeff Butler > > iBatis uses Class.forName to find classes. > In netbeans platform here is problem when iBatis used as module, because > netbeans restricts loading classes, not declared as dependency for calling > module. This lead to circular dependencies, because calling module contains > dao implementation classes and ibatis should depend on them to be able to > load them and in main module should depend on ibatis to be able to use ibatis > classes. > Netbeans allow to load with slightly different way: > ClassLoader l = Thread.currentThread().getContextClassLoader(); > Class c = l.loadClass("some.module.Class"); > Is it possible to allow developer to specify classloader wrapper via > sqlmap.xml, daomap.xml etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
