You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Michael Schall (JIRA)" <ib...@incubator.apache.org> on 2007/02/28 22:42:51 UTC

[jira] Created: (IBATISNET-213) ConfigureAndWatch only "watches" the last mapper created using ConfigureAndWatch

ConfigureAndWatch only "watches" the last mapper created using ConfigureAndWatch
--------------------------------------------------------------------------------

                 Key: IBATISNET-213
                 URL: https://issues.apache.org/jira/browse/IBATISNET-213
             Project: iBatis for .NET
          Issue Type: Bug
          Components: DataMapper
    Affects Versions: DataMapper 1.6.1
         Environment: Win2k, WinXP, Win2003 with .Net 2.0
            Reporter: Michael Schall


If you are configuring more than one mapper and use ConfigureAndWatch, only the mapper created in last call to ConfigureAndWatch is "Watched".  

I believe this is due to the fact that the ConfigWatcherHandler has a static list _filesToWatch that is cleared each time ConfigureAndWatch is called.  The SqlMapper instance really needs to store an instance of a ConfigWatcherHandler so it can watch the files and call the correct delegate at the right time.

Also, it would be nice if the ConfigureHandler delegate would be passed something (maybe SqlMap itself?) that could tell me which SqlMap needs to be rebuilt.  I currently have a dictionary of SqlMaps keyed by string.  If the delegate was passed the SqlMap I could loop through my dictionary to find the correct one to rebuild.

Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.