Possible Data inconsistency problem between JMManager and URLMapper

Hi,

I think there may be a data inconsistency problem between JMManager and
URLMapper.

In NetBeans 5.0 and on, URLMapper is used to map the URL of the file
into FileObject. This allows the flexible mapping of the physical file
and the FileObject in memory.=20

However, JMManager caches FileObjects into the HashMap (extents).  So if
the mapping of File and FileObject changes, the JMManager does not work
properly.

Also, there is no way to reset the MD repository per project. When the
project closes, I believe that the MD repository related data
structures, especially JMManager, needs to be reset. But I see old
cached FileObjects in JMManager's data structure. Using
javax.jmi.reflect.RefPackage.refDelete generates many "no longer
exists..." exceptions.

This is a problem for us because we are incorporating an FTP file system
into the existing J2SE project.  When the J2SE project gets closed and
reopened, the FTP file system gets created, and takes over the mapping
of a file and FileObject using our custom URLMapper. This works great,
except when it comes to Java MD  repository.=20

What do you think about this problem?  Is there a way we can work around
this issue?

Thanks

Isao Yanagimachi
HP