I am using the IBM JDK 1.3.1 on a W2k system. This is the JDK from the WebSphere Application Server V5.0 and WSAD 5.1.x. I think I can run the tests on an AIX system, too. (It is essential to use the right XML parser version. I had some difficulties with the tests of the extra binding stuff - I suspect that the default XML parser does not support namespaces, which results in an ArrayIndexOutOfBoundsException.)
Kai On Friday 04 June 2004 20:39, Dennis Sosnoski wrote: > I'm a little concerned about the invalid URL issue, but aside from that > the changes sound good. I'd definitely like to preserve compatibility > with not only 1.3, but also 1.2 - I've just been sloppy about checking > for added API methods. What system have you run and tested your changes on? > > - Dennis > > Kai Peter Nacke wrote: > > >Hi! > > > >I am using WSAD 5.1.2, which is still JDK 1.3.1 based. There are some > >issues when running the binding compiler/ > >binding runtime inside WSAD: > > > >- org.jibx.runtime.Utility.serializeCharString(char) (line 917) > > This methods calls Character.toString(char), which does not exist in > >JDK 1.3. This can be replaced whith a > > call to String.valueOf(char). > > > >- org.jibx.binding.Compile.handleOutput(String[]) (line 167) > > org.jibx.extras.TestRoundtrip.runTest(String,String,String) (line > >67) > > This methods call File(...).toURI(), which again does not exist in > >JDK 1.3. In both cases, the construct > > new File(...).toURI().toURL() ist used to construct a correct escaped > >URL, which is then passed to a > > classloader. If you use new File(...).toURL(), then a URL is > >constructed, which may have illegal characters > > (e.g. a space instead of %20). In the common case this is fatal (e.g. > >a http:// url containing spaces). But in > > the special case of a file:// url, it works nevertheless. (In fact, > >correct escaped urls don't work in JDK 1.2.2, > > because they are not unescaped before the filename is used....) > > > >With these 3 changes, I can run the binding compiler in WSAD (using > >Ant) whithout any problems. Is it > >possible/desirable to incorporate these changes in the source? > > > >Kai > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by the new InstallShield X. > >From Windows to Linux, servers to mobile, InstallShield X is the one > >installation-authoring solution that does it all. Learn more and > >evaluate today! http://www.installshield.com/Dev2Dev/0504 > >_______________________________________________ > >jibx-users mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/jibx-users > > > > > > > > > ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
