I have tried with the simplest of schemas and it still fails. One would also expect that any import issues would also be flagged when run from the main method.
The only thing I can imagine is some sort of classloader/class-path issue, where some of the EMF-files are running from within the server. But I have tried changig the class-loader schemes so it should be using the tuscany files supplied in the web application library, but nothing seems to help /Chr -----Original Message----- From: kelvin goodson [mailto:[EMAIL PROTECTED] Sent: 26. januar 2007 13:04 To: [email protected] Subject: Re: java.lang.IllegalArgumentException: resolve against non-hierarchical or relative base Christian, I don't know enough about the deployed environment, but I suspect it is to do with the imports that your schema makes. The second argument to XSDHelper.define is there to assist in resolving imports that are made by relative URI from the base schema location. Are the imported schemata available in the deployed environment at the correct relative location. Regards, Kelvin. On 25/01/07, Christian Landbo Frederiksen < [EMAIL PROTECTED]> wrote: > > I have some code that functions fine when run as simple java app with a > main method: > > URL url = > XsdDeconstructor.class.getClassLoader().getResource(xsdFile); > XSDHelper.INSTANCE.define(url.openStream(), url.toString()); > > But when I try to run it within a web app (on Websphere Test Environment > i Rational 7) I get the following: > > java.lang.IllegalArgumentException: resolve against non-hierarchical or > relative base > at org.eclipse.emf.common.util.URI.resolve(URI.java:1853) > > Any ideas? > > > /Christian > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
