Non edited version of Shindig?
I have edited my gadgets.js file. No thing else.
I am getting the same error even if I use *mvn jetty:run-war*
On Feb 20, 2008 1:48 PM, Cassie <[EMAIL PROTECTED]> wrote:
> Neo -
>
> Are you getting this error when trying to just run a non-edited version of
> Shindig or are you trying to set some of your own stuff up? When in a
> clean
> svn client, running mvn jetty:run-war from within the java/gadgets
> directory
> works for me.
>
> - Cassie
>
>
> On Tue, Feb 19, 2008 at 11:07 PM, Neo Anderson <
> [EMAIL PROTECTED]> wrote:
>
> > Even when I use mvn clean, I got the same error.
> >
> > When I start jetty, I got this:
> >
> > Feb 20, 2008 12:34:53 PM
> > org.apache.shindig.gadgets.JsFeatureLoaderloadFeatures
> > INFO: Loading resources from: features/features.txt
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/analytics/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/caja/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/core.io/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/core/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/dynamic-height/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/flash/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/ifpc/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/minimessage/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in
> features/opensocial-reference/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in
> > features/opensocial-samplecontainer/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/rpc/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/setprefs/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/settitle/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/skins/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/tabs/feature.xml
> > Feb 20, 2008 12:34:53 PM org.apache.shindig.util.ResourceLoadergetContent
> > INFO: Looking for feature.xml in features/views/feature.xml
> > Feb 20, 2008 12:34:53 PM
> > org.apache.shindig.gadgets.GadgetFeatureRegistryregist
> > er
> > INFO: Registering feature: core.msgbundlesubst
> > Feb 20, 2008 12:34:53 PM
> > org.apache.shindig.gadgets.GadgetFeatureRegistryregist
> > er
> > INFO: Registering feature: core.bidisubst
> > Feb 20, 2008 12:34:53 PM
> > org.apache.shindig.gadgets.GadgetFeatureRegistryregist
> > er
> > INFO: Registering feature: core.modulesubst
> > Feb 20, 2008 12:34:53 PM
> > org.apache.shindig.gadgets.GadgetFeatureRegistryregist
> > er
> > INFO: Registering feature: core.prefsubst
> > Feb 20, 2008 12:35:36 PM
> > org.apache.shindig.gadgets.http.GadgetRenderingServlet
> > outputErrors
> >
> >
> > This means that features are loaded. Then why I'm getting this error?
> >
> > And I am getting this error when I use any one of dynamic-height,
> > settitle
> > features.
> > On Feb 19, 2008 11:03 PM, Kevin Brown <[EMAIL PROTECTED]> wrote:
> >
> > > the UNSUPPORTED_FEATURE error should only come up if your gadget
> server
> > > can't find a feature that a gadget requires, but that shouldn't be
> > > happening
> > > with setprefs.
> > >
> > > Try this:
> > >
> > > - run mvn clean
> > > - make sure you start the server with jetty:run-war (and not
> jetty:run)
> > if
> > > using the built in jetty container.
> > >
> > > Also, could you send me the gadget that you're getting this error
> with?
> > >
> > > On Feb 19, 2008 1:06 AM, Arun Kumar <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > > How to use rpc instead of ifpc_relay.html?
> > > > What I did is,
> > > > I changed
> > > > gadgets.container.setParentUrl('ifpc_relay.html') to
> > > > gadgets.container.setParentUrl('rpc_relay.html')
> > > > But still I'm getting Error 400 UNSUPPORTED_FEATURE setprefs
> > > >
> > > > UNSUPPORTED_FEATURE setprefs
> > > >
> > > > error.
> > > >
> > >
> > >
> > >
> > > --
> > > ~Kevin
> > >
> > > If you received this email by mistake, please delete it, cancel your
> > mail
> > > account, destroy your hard drive, silence any witnesses, and burn down
> > the
> > > building that you're in.
> > >
> >
>
