Hi, I am also having a similar issue when using the Jetty with mvn -Prun. I issued mvn -Prun from trunk/ and attached the logs at the end. When I access, http://localhost:8080/gadgets/files/samplecontainer/samplecontainer.html, I'm getting HTTP 404 error.
I checked out the source code from trunk[1] ( maven build was successful) and my environment: Java: java version "1.6.0_20" Maven: Apache Maven 2.2.1 OS: Ubuntu 10.04 But when I deployed the war file in Apache Tomcat 6.0.26, I could access the sample container (with necessary changes to the access url). Any idea whether I'm missing something? [1] http://svn.apache.org/repos/asf/shindig/trunk Thanks, ~Umashanthi mvn -Prun [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Apache Shindig Project [INFO] task-segment: [jetty:run-war] [INFO] ------------------------------------------------------------------------ [INFO] Preparing jetty:run-war [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on => 'false'. [INFO] Setting property: resource.loader => 'classpath'. [INFO] Setting property: resource.manager.logwhenfound => 'false'. [INFO] [remote-resources:process {execution: default}] [WARNING] DEPRECATED [tasks]: Use target instead [INFO] [antrun:run {execution: create-work}] [WARNING] Parameter tasks is deprecated, use target instead [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [site:attach-descriptor {execution: default-attach-descriptor}] [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] [source:jar {execution: attach-sources}] [INFO] Preparing source:test-jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive invocation. [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] [source:test-jar {execution: attach-sources}] [INFO] [jetty:run-war {execution: default-cli}] [INFO] Configuring Jetty for project: Apache Shindig Project 2011-01-30 15:05:27.167:INFO::Logging to STDERR via org.mortbay.log.StdErrLog [INFO] Context path = / [INFO] Tmp directory = determined at runtime [INFO] Web defaults = org/mortbay/jetty/webapp/webdefault.xml [INFO] Web overrides = none [INFO] Starting jetty 6.1.26 ... 2011-01-30 15:05:27.242:INFO::jetty-6.1.26 2011-01-30 15:05:27.557:INFO::No Transaction manager found - if your webapp requires one, please configure one. Jan 30, 2011 3:05:30 PM org.apache.shindig.config.JsonContainerConfigLoader loadContainers INFO: Loading resources from containers/default/container.js. Jan 30, 2011 3:05:30 PM org.apache.shindig.config.JsonContainerConfigLoader loadResources INFO: Reading container config: containers/default/container.js. Jan 30, 2011 3:05:30 PM org.apache.shindig.gadgets.features.FeatureRegistry register INFO: Loading resources from res:features-extras/features.txt. Jan 30, 2011 3:05:30 PM org.apache.shindig.common.xml.XmlUtil static block INFO: Not using secure XML processing. Jan 30, 2011 3:05:30 PM org.apache.shindig.common.xml.XmlUtil static block INFO: Reusing document builders. Jan 30, 2011 3:05:32 PM org.apache.shindig.gadgets.features.FeatureRegistry register INFO: Loading resources from res:features/features.txt. Jan 30, 2011 3:05:33 PM org.apache.shindig.gadgets.servlet.CajaContentRewriter CajaContentRewriter INFO: Cajoled cache created Jan 30, 2011 3:05:33 PM org.apache.shindig.gadgets.servlet.CajaContentRewriter CajaContentRewriter INFO: Cajoled cache created Jan 30, 2011 3:05:33 PM org.apache.shindig.gadgets.oauth.OAuthModule$OAuthCrypterProvider <init> INFO: Using random key for OAuth client-side state encryption Jan 30, 2011 3:05:33 PM org.apache.shindig.gadgets.oauth.OAuthModule OAuthCrypterProvider constructor INFO: Using random key for OAuth client-side state encryption Jan 30, 2011 3:05:33 PM org.apache.shindig.gadgets.oauth.OAuthModule loadDefaultKey WARNING: Couldn't load OAuth signing key. To create a key, run: openssl req -newkey rsa:1024 -days 365 -nodes -x509 -keyout testkey.pem \ -out testkey.pem -subj /CN=mytestkey openssl pkcs8 -in testkey.pem -out oauthkey.pem -topk8 -nocrypt -outform PEM Then edit shindig.properties and add these lines: shindig.signing.key-file =<path-to-oauthkey.pem> shindig.signing.key-name =mykey Jan 30, 2011 3:05:33 PM org.apache.shiro.config.IniSecurityManagerFactory isAutoApplyRealms INFO: Realms have been explicitly set on the SecurityManager instance - auto-setting of realms will not occur. Jan 30, 2011 3:05:33 PM org.apache.shiro.realm.AuthorizingRealm getAuthorizationCacheLazy INFO: No cache or cacheManager properties have been set. Authorization cache cannot be obtained. 2011-01-30 15:05:34.022:INFO::Started [email protected]:8080 [INFO] Started Jetty Server 2011-01-30 15:05:58.395:WARN::/gadgets/files/samplecontainer/samplecontainer.html: java.io.IOException: Closed 2011-01-30 15:08:50.646:WARN::/gadgets/files/samplecontainer/samplecontainer.html: java.io.IOException: Closed 2011-01-30 15:08:55.248:WARN::/gadgets/files/samplecontainer/samplecontainer.html: java.io.IOException: Closed On Sun, Jan 30, 2011 at 1:09 PM, Gagandeep singh <[email protected]>wrote: > Paste the log of mvn -Prun, most likely some exception is being thrown. > > On Sat, Jan 29, 2011 at 9:14 PM, Xue-Feng Yang <[email protected]> > wrote: > > > > > I use Jetty. After build shindig, I copied and pasted > > > > shindig-server-3.0.0-SNAPSHOT.war > > > > to webapps directory. > > > > I move your test.html to webapps/root. http://localhost/test.html works > > fine. > > > > However, mvn -Prun was failed. > > > > Thanks. > > > > > > > > ----- Original Message ---- > > From: Wouter Charle <[email protected]> > > To: [email protected] > > Sent: Sat, January 29, 2011 11:25:39 PM > > Subject: Re: HTTP ERROR 404 > > > > Hi again. I'm not familiar with the Java version of Shindig, but (I > assume) > > independent from that: > > Make a test.html file (content: <html><head></head><body><p>Hello > > world!</p></body></html>) in your shindig directory on the webserver and > > then goto http://localhost/test.html > > If "Hello world!" is displayed, I wouldn't have a clue about how to solve > > your problem. If not, your localhost is just not pointing to where > Shindig > > is installed. In that case, consider creating a virtualhost called > shindig > > or something that points to your Shindig installation. > > Then goto http://shindig/gadgets/ifr?... and it should work. > > > > I hope this solves your problem :) > > > > On Sat, Jan 29, 2011 at 1:56 PM, Xue-Feng Yang <[email protected]> > > wrote: > > > > > Thanks Wouter. > > > > > > I tried by removing the port number. It's the same. > > > > > > I was testing in XP and Java 1.6.0_23. > > > > > > > > > > > > ----- Original Message ---- > > > From: Wouter Charle <[email protected]> > > > To: [email protected] > > > Sent: Sat, January 29, 2011 5:39:44 PM > > > Subject: Re: HTTP ERROR 404 > > > > > > Hi Yang, > > > Did you try to remove the port number from your url? > > > http://localhost/gadgets/ifr?... > > > Is localhost the virtualhost pointing to your Shindig folder? > > > What is your environment? > > > > > > On Fri, Jan 28, 2011 at 6:37 PM, Xue-Feng Yang <[email protected]> > > > wrote: > > > > > > > Hi All: > > > > > > > > I am new to shindig. Followed apache-shindig.pdf, I checked out > source > > > > code, > > > > built shindig and installed the built WAR to Jetty. I saw everything > > was > > > > fine > > > > but a few warning messages. > > > > > > > > However, when I opened > > > > > > > > > > > > > > http://localhost:8080/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml > > >l > > > >l > > > > > > > > I saw the following error message. > > > > > > > > Did I miss anything? > > > > > > > > > > > > HTTP ERROR 404 > > > > Problem accessing /gadgets/ifr. Reason: > > > > Not Found > > > > ________________________________ > > > > Powered by Jetty:// > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
