shindig-features-1-SNAPSHOT.jar has made it into the WEB-INF/lib of the war file, but obviously something doesn't allow the server to load those resources in that manner. I'll bust them out of the jar file and create a war file with that jar file unrolled in the root of the war file and see what happens... could be jboss funkiness at play here.... maybe I can find a different way to load these files at runtime to avoid this.
On Thu, Jun 5, 2008 at 2:30 PM, Brad Defnall <[EMAIL PROTECTED]> wrote: > I've addressed the two issues listed in that Jira issue (by hardcoding my > new context path so it's not really a 'fix' as much as a workaround). > > If I can figure this one out, I'll definitely let everyone know. > > Brad > > > > On Thu, Jun 5, 2008 at 2:26 PM, Christian Schalk <[EMAIL PROTECTED]> > wrote: > >> There are definitely issues when deploying to Java EE containers. For >> example to get Shindig runningi with Tomcat, you have to do some specific >> steps to get Gadgets to render at all. This is because of some hard coded >> paths which assumed that /gadgets/.. would be available... but since you >> need a context root when deploying to an actual Java container, this >> brakes. >> >> check out the issue I logged awhile back. >> >> https://issues.apache.org/jira/browse/SHINDIG-272 >> >> Feel free to add comments on JBoss.. >> >> -Chris >> >> On Thu, Jun 5, 2008 at 11:22 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: >> >> > On Thu, Jun 5, 2008 at 11:12 AM, Brad Defnall <[EMAIL PROTECTED]> >> wrote: >> > >> > > I'm trying to deploy on jboss... >> > > >> > > I get the following errors: >> > > >> > > 2008-06-05 14:03:50,828 ERROR [STDERR] Jun 5, 2008 2:03:50 PM >> > > org.apache.shindig.gadgets.JsLibrary loadResource >> > > WARNING: Could not find resource: features/caja/html4-defs.opt.js >> > > 2008-06-05 14:03:50,828 ERROR [STDERR] Jun 5, 2008 2:03:50 PM >> > > org.apache.shindig.gadgets.JsLibrary loadData >> > > INFO: Loading js from: features/caja/html4-defs.js type: RESOURCE >> > > >> > > I'm pretty sure this is a context problem, but I can't figure out a >> few >> > > things. >> > > >> > > 1) How do these feature files get added to the war file, if at all? >> > >> > >> > features are bundled into a jar (for the java build, anyway), which the >> war >> > depends on. The artifact is produced by trunk/features/pom.xml (NOT in >> the >> > java directory because client code is shared between server >> > implementations). >> > >> > >> > > 2) If they aren't automatically added to the war file during the build >> > > process, what do I need to do to get these deployed properly? >> > >> > >> > They should be. This is the first I've heard of this issue. >> > >> > >> > > >> > > >> > > 3) If it's a context issue, how do I resolve it? >> > > >> > > I've been working on just this practically all day. Any ideas? >> > >> > >> > Does the war layout look correct to you? Is there a features/ directory >> in >> > it? >> > >> > I'm not familiar with jboss at all -- perhaps someone who is can provide >> > more help. >> > >> > >> > > >> > > thanks, >> > > brad >> > > >> > >> >> >> >> -- >> Chris Schalk, Google Developer Advocate >> > >
