Re: metadata call error

[John Hjelmstad <fa...@google.com>]

Yikes, just got this message -- somehow got mis-filed.

1. Are you still experiencing this issue?
2. Why did you remove schema ("http") from defaultShindigTestHost? Could you
add "//" as a prefix?

Unfortunately the opaque-URI error comes from Java's URI parser class. We're
just re-throwing it as a UriException.

-j

On Thu, Jun 17, 2010 at 7:51 AM, Javier H Pedemonte <pe...@us.ibm.com>wrote:

> It's a bit better now, thanks to a checkin yesterday that defined some of
> the missing values in config/container.js.
>
> Loading of http://localhost:8080/container/sample-metadata.html still
> fails, though (testing with Jetty server).  It tries to load URLs that start
> with "http://http//localhost:9003/gadgets/ifr...".
>
> I changed one line in container.js from  "defaultShindigTestHost": "
> http://localhost:9003"  to  "defaultShindigTestHost": "localhost:8080".
>  But then tests fail.
>
> Compiled without tests and reloaded sample-metadata.html.  Now the URLs
> look fine ("http://localhost:8080/gadgets/ifr..."), but the server errors
> out with:
>         org.apache.shindig.common.uri.Uri$UriException: No support for
> opaque Uris localhost:8080
>
> I assume that's because I removed the "http://" from the
> "defaultShindigTestHost" value.
>
> But I don't know this code well enough to attempt a fix.  Any help?
>
>
> Javier Pedemonte
>