If you could write a quick unit test to demonstrate the broken behavior, it might help. Nathan just wrote a mapper and it was loaded automatically, so something must be different somewhere...
Note: The namespace must equal the fully qualified name of the CLASS, not the PACKAGE.... Clinton On Mon, Aug 17, 2009 at 9:26 AM, RichadB<richard.b...@aimhedge.com> wrote: > > Adding the explicit mapping seems to work (or at least it gets me to another > error of the sort I would expect to see). I don't think I'm doing anything > strange, so I'm not sure why it doesn't automatically load > > Thanks Clinton > > > Clinton Begin wrote: >> >> Strange, it should add it automatically if the namespace shares the >> name of a class. That said, you can add it manually... >> >> sqlSessionFactory.getConfiguration().addMapper(Your.class); >> >> I'll add this to the documentation. >> >> Clinton >> >> > -- > View this message in context: > http://www.nabble.com/not-known-to-the-MapperRegistry-with-iBatis-3.0-tp25007484p25008853.html > Sent from the iBATIS - User - Java mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org > For additional commands, e-mail: user-java-h...@ibatis.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org