I have created https://issues.apache.org/jira/browse/ACE-40 and committed a fix. Could you verify it?
Angelo On 1 Oct 2009, at 20:18, Angelo van der Sijpt wrote: > Hi Filippo, > > You are right, the ISE does not cause any bad behavior in the client, > its and exception that bubbles up from the server side. Its not that > bad, but I'll create an issue to fix this. > > You're right, the 'No local version available' exception in the server > log has nothing to do with this. That exception happens because the > target polls the server for a new version, but there is no data at all > in the server repositories. > > Angelo > > > On 1 Oct 2009, at 17:57, Filippo Diotalevi wrote: > >> Hi, >> I've played a bit with the Apache Ace WebUI in the past few days, >> but since this morning I'm experiencing a persistent error preventing >> me to use it :-| >> >> I'm starting with an empty server and an empty dev-gateway, taking >> the >> zip files from the deploy/releases folder. >> >> Both starts up correctly, and the gateway shows up correctly in the >> web page. However, every time I click on the gateway checkbox, an >> error popup appears displaying the error: >> "Error updating highlights: java.lang.IllegalStateException: This >> StatefulGatewayObject is not backed by a GatewayObject." >> >> The gateway log does not report any exception, but the server log >> shows this exception (not related to the click in the user interface >> apparently): >> >> java.io.IOException: No local version available of >> FilebasedBackupRepository[/var/folders/3z/3zTkKpeEHhStUApFf5lG+U++ >> +TI/-Tmp-/currentrepository6558773143957890412.tmp,/var/folders/3z/ >> 3zTkKpeEHhStUApFf5lG+U+++TI/-Tmp-/ >> backuprepository2323126334925948555.tmp], >> remote RemoteRepository[http://localhost:8080/ >> repository,apache,deployment,null] >> at org.apache.ace.repository.impl.CachedRepositoryImpl.getLocal >> (CachedRepositoryImpl.java:136) >> at >> org.apache.ace.deployment.provider.repositorybased.RepositoryBasedProvider.getRepositoryStream >> (RepositoryBasedProvider.java:563) >> at >> org.apache.ace.deployment.provider.repositorybased.RepositoryBasedProvider.getVersions >> (RepositoryBasedProvider.java:157) >> at org.apache.ace.deployment.servlet.DeploymentServlet.doGet >> (DeploymentServlet.java:84) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) >> at org.mortbay.jetty.servlet.ServletHolder.handle >> (ServletHolder.java:502) >> at org.mortbay.jetty.servlet.ServletHandler.handle >> (ServletHandler.java:389) >> at >> org.ops4j.pax.web.service.internal.HttpServiceServletHandler.handle >> (HttpServiceServletHandler.java:64) >> at org.mortbay.jetty.servlet.SessionHandler.handle >> (SessionHandler.java:181) >> at org.mortbay.jetty.handler.ContextHandler.handle >> (ContextHandler.java:765) >> at org.ops4j.pax.web.service.internal.HttpServiceContext.handle >> (HttpServiceContext.java:111) >> at >> org.ops4j.pax.web.service.internal.JettyServerHandlerCollection.handle >> (JettyServerHandlerCollection.java:64) >> at org.mortbay.jetty.handler.HandlerWrapper.handle >> (HandlerWrapper.java:152) >> at org.mortbay.jetty.Server.handle(Server.java:324) >> >> >> Any idea? >> >> >> Thanks, >> -- >> Filippo Diotalevi >
