Looks like it's a missing configuration parameter in container.js from one of these two commits:
commit 5224ecc97e97fb53ff2997cd72bd7bc245fe0586 Author: John Hjelmstad <[email protected]> Date: Wed Feb 3 01:23:19 2010 +0000 1. Fix subtle NPE occurring when UriBuilder-generated Uri with null path is base in a relative resolution. 2. Catch Runtime DOMException in fragment parser API. git-svn-id: https://svn.apache.org/repos/asf/incubator/shindig/tr...@90585913f79535-47bb-0310-9956-ffa450edef68 commit 21a6a4d3f167938f9883e2a3694fbaeee0a96b4e Author: John Hjelmstad <[email protected]> Date: Wed Jan 6 23:05:29 2010 +0000 This patch implements a new set of URL(/I) generation interfaces designed to replace the current UrlGenerator and LockedDomainService interfaces. On Tue, Jun 15, 2010 at 2:45 PM, Javier H Pedemonte <[email protected]>wrote: > After updating the source today, code that makes a metadata call (to > "/gadgets/metadata") fails. You can see this by loading > http://localhost:8080/container/sample-metadata.html. The error is: > "Missing required container config param, key: > gadgets.uri.iframe.basePath, container: default" > > I tried to debug it, but I know very little about the Java server code. > Maybe related to https://issues.apache.org/jira/browse/SHINDIG-805? > > > Javier Pedemonte >
