Micheal,

Thanks for the help! I missed these and that's what was causing my problems. As an aside, I had a strange problem when I copy pasted these lines in from the Changelog.txt file. Seems there is an unrecognized character which looks like a " in the VS editor, but throws an error when parsed! I fixed it my copying them from VS into notepad, where the appeared as blocks, and replacing them with ". Works fine now.

B

Michael Schall wrote:

I just did this last night and ran into some problems as well...

My issue was that my old config, map, and provider files did not give
the xml namespace which in now seems to be required.  Examples below.

Hope this helps.
Mike

SqlMaps.config –
<sqlMapConfig xmlns="http://ibatis.apache.org/dataMapper";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

Vsp files –
<sqlMap namespace="LocksVsp" xmlns="http://ibatis.apache.org/mapping"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

Provider files –
<providers xmlns="http://ibatis.apache.org/providers";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>



On 1/12/06, Brian Kierstead <[EMAIL PROTECTED]> wrote:
I'm trying to upgrade my project to the latest versions of ibatis (both
1.3 beta of the mapper and 1.7 beta of the mapper) using the source code
found on the site (Source Revision 356824).  Has anyone done this already?

I just replaced the my older versions directly, recompiled and ran it.
I don't get any errors in the compiliation, but when I try to retrieve
a  DaoManager using this routine in the DataAccess code, it returns null:

public static DaoManager GetInstance(string contextName)
{
   return (DaoManager) DaoContextMap[contextName];
}

I'm using the same config files that I had before and this routine is
being called with same name.  The DaoContextMap collection appears to be
empty at run-time though, so something is not being loaded for whatever
reason.

I've looked around for a 'to updgrade do this' type of document but
can't find anything.  I hope I'm just missing a simple change to the
configuration.

Thanks,
Brian






Reply via email to