Hi George, I believe you use exactly string "classpath:META-INF/assets/fonts/fontawesome-webfont.eot" in Java code. You should use "fonts/fontawesome-webfont.eot" instead - Tapestry 5.4 knows that it needs to prepend "META-INF/assets".
However, as others said, for Font Awesome you need rather import its CSS file in Tapestry, not EOT file (of course the EOT file should still be in your META-INF/assets/fonts). Best regards, Cezary On Fri, Dec 19, 2014 at 9:58 AM, George Christman <[email protected]> wrote: > > hmm, I'm using 5.4. We no longer have assets in the webapp directory. I > wonder if that makes a difference. > > On Fri, Dec 19, 2014 at 3:01 AM, Daniel Jue <[email protected]> wrote: > > > > Forgot to mention, I am using T5.3.7 > > > > On Fri, Dec 19, 2014 at 2:59 AM, Daniel Jue <[email protected]> wrote: > > > > > > Hi George, I'm not really sure what the .eot file does. > > > > > > My assets are under src/main/webapp in my maven module: > > > > > > i.e. > > > > > > > > > https://github.com/Sotera/graphene/tree/master/graphene-parent/graphene-web/src/main/webapp/core/fonts > > > > > > > > > https://github.com/Sotera/graphene/tree/master/graphene-parent/graphene-web/src/main/webapp/core/css > > > > > > My layout component loads the files used by FA and other parts of the > > > templates I use: > > > > > > > > > > > > https://github.com/Sotera/graphene/blob/master/graphene-parent/graphene-web/src/main/java/graphene/web/components/Layout.java > > > > > > > > > > > > On Fri, Dec 19, 2014 at 1:50 AM, George Christman < > > [email protected] > > > > wrote: > > >> > > >> Hi Daniel, how do you have your assets setup? > > >> > > >> I added font-awesome-min.css to my META-INF/assets/css > > >> > > >> I'm then importing it. > > >> > > >> @Import(stylesheet = {"css/font-awesome.min.css"} > > >> > > >> I added a directory called fonts to assets like so > > >> META-INF/assets/fonts/.. > > >> all the font files example fontawesome-webfont.eot > > >> > > >> Within font-awesome.min.css I see this url > > >> '../fonts/fontawesome-webfont.eot?v=4.2.0' > > >> > > >> I am seeing fonts added correctly in the app container. > > >> > > >> Any thoughts in comparison to your setup what I may be missing? > > >> > > >> On Fri, Dec 19, 2014 at 1:21 AM, Daniel Jue <[email protected]> > wrote: > > >> > > > >> > Just to be sure, are you seeing the file correctly in the deployment > > >> > directory of your application container? > > >> > > > >> > I am using fontawesome as well in my T5 app, and, well, it's > awesome! > > >> > Never ran into issues with that file though. > > >> > > > >> > Dan > > >> > > > >> > On Fri, Dec 19, 2014 at 12:52 AM, George Christman < > > >> > [email protected]> > > >> > wrote: > > >> > > > > >> > > Hi guys, I'm trying to use font-awesome with tapestry. I'm getting > > the > > >> > > following error, > > >> > > > > >> > > Unable to locate asset > > >> > > 'classpath:META-INF/assets/fonts/fontawesome-webfont.eot' (the > file > > >> does > > >> > > not exist). > > >> > > > > >> > > I have placed the fonts in the fonts directory within assets, any > > >> > thoughts > > >> > > on how to get this to work? > > >> > > > > >> > > -- > > >> > > George Christman > > >> > > CEO > > >> > > www.CarDaddy.com > > >> > > P.O. Box 735 > > >> > > Johnstown, New York > > >> > > > > >> > > > >> > > >> > > >> -- > > >> George Christman > > >> CEO > > >> www.CarDaddy.com > > >> P.O. Box 735 > > >> Johnstown, New York > > >> > > > > > > > > -- > George Christman > CEO > www.CarDaddy.com > P.O. Box 735 > Johnstown, New York >
