Inconsistent loading of jpos.xml

Question

I have an applet that successfully loads jpos.xml in both WinXP and W2003SRV, both of which are JRE 6.045 and 7.025 (both old and outdated), but it works. However, the same code does not load jpos.xml in Win7Pro. Download here. JavaPOS appears, preventing explicit loading from banks or war. Can someone explain why inconsistency and decision?

JposEntryRegistry registry = JposServiceLoader.getManager(). getEntryRegistry(); registry.load(); 

UPDATE: I tried to download the file directly String location = this.getCodeBase.toString + "WEB-INF / classes / jpos.xml" registry.getRegPopulator.load (location); no results If I try to open an InputStream through a URL, I get: File not found. java.io.FileNotFoundException: http: // localhost: 8083 / 10sdaanyd / WEB-INF / classes / jpos.xml How can I manually populate the Jpos registry if it fails using the standard approach (which breaks the "write once to use everywhere "on Win7Pro. Does anyone know?

UPDATAE01 Following this , I put the parameters in the applet tag, still fails on Win7Pro, but works perversely on Win7Home (yes, anyway). Detection registry.getSize () == 0 I load the file the first time I see its cache and it does not populate the registry. I downloaded jpos113 and all the necessary banks. I am loading it from the root of the application context. Ideas for inconsistent deployment?

Actually below is an undisclosed trace

network: Download resource: http://10.0.0.50:8083/10sdaanyd/jpos.xml Content-length: 6,245 Content-Encoding: null network: wrote the URL http://10.0.0.50:8083/10sdaanyd/jpos.xml in file C: \ Users \ ExecAssist00 \ AppData \ LocalLow \ Sun \ Java \ Deployment \ cache \ 6.0 \ 58 \ 60dbe6ba-72fcf580-temp network: CleanupThread uses 1 us

779 [thread applet-javapos.appletPOS_00-3] DEBUG javapos.appletPOS_00 - start: in registry == 0: registry.getSize () = 0 near printpathpath. urls.length = 1 / C: / Program% 20Files% 20 (x86) / Java / jre6 / classes codebase: http://10.0.0.50:8083/10sdaanyd/ jpos.JposException: The service does not exist in the loaded JCL registry.