On Fri, Oct 31, 2014 at 1:38 PM, Gonzalo Aguilar Delgado < [email protected]> wrote:
> Hi Martin, > > Well, that's good news. Unfortunately we cannot upgrade server now. Can > you try it in 7.1.1 because I think something wrong is happening since no > one .js from wicket is loading. > Open org.apache.wicket.core.util.resource.ClassPathResourceFinder#find(Class, String) and see what happens. > > From your comment below do you mean that it will not work on Jboss7? > I am not aware of other complains about such problem on JBoss 7.x so far, so I guess it is something on your side... > > Thank you in advance. > And again - if it works everywhere else but at one specific web container then I'd ask this container's experts for help. Before that I'll try to debug it myself, prepare a demo application, explain all steps to reproduce, etc. > > > El 31/10/14 a las 12:34, Martin Grigorov escribió: > > Hi, >> >> It works well here with JBoss 8 (WildFly 8.1). >> >> On Fri, Oct 31, 2014 at 1:22 PM, Gonzalo Aguilar Delgado < >> [email protected]> wrote: >> >> Hi, >>> >>> We built an application that depends on JQuery because we show graphs >>> with >>> morris and raphael. And we discovered that >>> >>> @Override >>> public void renderHead(IHeaderResponse response) { >>> super.renderHead(response); >>> >>> >>> response.render(JavaScriptHeaderItem >>> .forReference(JQueryResourceReference.get())); >>> } >>> >>> is working well on tomcat but when deployed on jboss it fails. The >>> references that went to wicket are not rendering. The ones we have in our >>> own packages are working. >>> >>> We can see some: >>> 12:17:42,844 WARN [org.apache.wicket.resource. >>> bundles.ConcatBundleResource] >>> (http-localhost-127.0.0.1-8880-3) Bundled resource: Unable to find >>> resource (status=404) >>> 12:17:42,845 WARN [org.apache.wicket.resource. >>> bundles.ConcatBundleResource] >>> (http-localhost-127.0.0.1-8880-2) Bundled resource: Unable to find >>> resource (status=404) >>> >>> Maybe has something to do , maybe not but the fact is that it works with >>> tomcat 6 and not with jboss 7. >>> >>> Any help will be appreciated. Should I open a bug? Can someone confirm >>> this, please? >>> >>> You mean a bug at JBoss JIRA, I guess ? >> JBoss uses "modules" (an abstraction over a jar) and virtual file system >> (an abstraction over classpath?!), so many weird things could happen >> there. >> >> Wicket uses Class#getResourceAsStream("someName.js") to load a file from >> the classpath. Pretty standard. >> >> >> Best regards, >>> >>> >
