Exception in newInstance in windows NT (CORBA persistent server)

Question

I have used this code for CORBA persistent server....its working fine
in Solaris OS ,but getting exception in newInstance call in the
following code.Code fragment and Exception are given below,....pls help
private org.omg.PortableServer.Servant loadModuleImpl(String
p_stImplName,String p_stModulePath)
throws Exception{
try
// load class corresponding to p_stInterfaceName
Class l_theIntfClass = null;
System.out.println("p_stModulePath = " + p_stModulePath+ "
p_stImplName = " +p_stImplName);
l_theIntfClass = Class.forName(p_stModulePath+ "."+ p_stImplName);
org.omg.PortableServer.Servant l_theImpl=null;
l_theImpl=(org.omg.PortableServer.Servant)l_theIntfClass.newInstance();
System.out.println("Loaded " + p_stModulePath+ "."+ p_stImplName);
System.out.println();
return l_theImpl;
catch(Exception p_theE)
p_theE.printStackTrace();
throw new MException("Unable to load - " + p_stModulePath
+ "."
+ p_stImplName);
OUTPUT
======
[Thu Apr 13 16:35:02 IST 2006] Server started
Initialized ORB....
Created root POA....
[Thu Apr 13 16:35:04 IST 2006] Install starting
[Thu Apr 13 16:35:04 IST 2006] Install completed
Resolved central NS....
Into node /Pegasus....
Into node /Pegasus/Framework....
Into node /Pegasus/Framework/AlrMgr....
Resolved Configurator....
Configuration Handler initialized....
Default Policy: Child POA not created....
p_stModulePath = Handlers.Common.AppManager p_stImplName =
MCallbackImpl
Loaded Handlers.Common.AppManager.MCallbackImpl
Publishing Interface....
Name: ICallback_0
POA: RootPOA
Created Child POA: AlrMgr_POA_{1, 3, 8}
p_stModulePath = MainModules.AlrMgr p_stImplName = MAlrMgrImpl
[Thu Apr 13 16:35:08 IST 2006] FATAL: application error: Exception:
null
ERROR
=====
[Thu Apr 13 16:35:08 IST 2006] FATAL: application error: Exception:
null

Answer 1

I think that's a problem with the Finder, and much worse in 10.4 than previous releases. Even Locally saved files may not show up until they want to! Even when you know exactly where they are.
There's a 3rd party utility that fixes this, or at least forces an update, but I can't remember what it's called!
I don't think this is the one I was thinking about, but this should work...
http://www.versiontracker.com/dyn/moreinfo/macosx/18736