> I have no idea what's going on with it. It really ticks me off as > that's the kind of feature you should have to enable in a parser not > disable.
Is it? I thought the engine should first check if the necessary scheme is present locally and only try download if no local copy is present. Isnt't it true? Shouldn't we reopen OPENEJB-700 anyway? > If you have some time to debug, the > JaxbJavaee.NamespaceFilter.resolveEntity(...) method should be the one > stopping things from downloading. Ok, I'll check that, thanks. Vasily On Sun, Mar 2, 2008 at 12:56 AM, David Blevins <[EMAIL PROTECTED]> wrote: > > On Feb 29, 2008, at 8:36 AM, Vasily Zakharov wrote: > > > Hi, all, > > > > I'm once again trying to couple SPECjAppServer2004 with Geronimo, now > > version 2.1, and one of the problems I observe is: > > > > Issue OPENEJB-700 that is now closed as it was fixed in OpenEJB v3.0b2 > > that is used in G2.1, seems to be still actual for some reason. On > > G2.1 I still can't deploy SjAS unless the internet connection is > > present and proxy properly configured. The following error is shown by > > the Deployer: > > > > Error: Unable to distribute SPECjAppServer.ear: > > org.apache.openejb.OpenEJBException: Cannot read the ejb-jar.xml file: > > jar:file:/C:/Temp/geronimo-deploymentUtil48973.jar!/META-INF/ejb- > > jar.xml: > > Connection timed out: connect > > > > General Geronimo/SjAS configuration used is described in detail at > > [1]. > > The particular deployment plan causing a problem is [2]. > > > > Can anyone suppose if this is indeed a not-completely-fixed > > OPENEJB-700 or something else? > > I have no idea what's going on with it. It really ticks me off as > that's the kind of feature you should have to enable in a parser not > disable. > > If you have some time to debug, the > JaxbJavaee.NamespaceFilter.resolveEntity(...) method should be the one > stopping things from downloading. > > -David > >
