Problema com layout da página

4 respostas
joaosavio

Olá pessoal!

Se eu coloco a URL http://localhost:8084/Pattern/faces/index.xhtml a pagina inicial fica zuada (as figuras nao aparecem, o layout fica zuado), parece q nao esta com o css, contudo http://localhost:8084/Pattern/ fica certinho

Alguem tem alguma ideia???

No template do facelets, o css está referenciado da seguinte forma:

<head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
        <link href="./css/default.css" rel="stylesheet" type="text/css" />
        <link href="./css/tableLayout.css" rel="stylesheet" type="text/css" />
        <title>Facelets Template</title>
</head>

4 Respostas

Scoobydoo

Não deve ser este o problema mas
http://localhost:8084/Pattern/faces/index.xhtml
http://localhost:8084/Pattern/faces/index.html <-- é .html nao xhtml

De uma olhada para ver se seu Css está configurado corretamente e esta alocado na pasta certa
Use … para voltar para a pasta pai…

wbdsjunior

teste referenciar o css assim:

&lt;link href="../css/default.css" rel="stylesheet" type="text/css" /&gt; // dois pontos em vez de um

não tenho certeza, mas quando você coloca um ponto você referencia o diretório anterior (pai) e quando coloca dois pontos o diretório raiz.

Scoobydoo

o diretório Raiz seria o Pattern, que é aonde esta funcionando ^^

joaosavio

Teoricamente está certo a referencia ao css, pois a pasta css está no mesmo nível, entao “.” quer dizer pasta atual

Quando digito o caminho completo, aparecem alguns erros:

21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/css/default.css]
com.sun.facelets.FaceletException: Error Parsing /css/default.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/css/tableLayout.css]
com.sun.facelets.FaceletException: Error Parsing /css/tableLayout.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@bbaa16) threw exception
com.sun.facelets.FaceletException: Error Parsing /css/tableLayout.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 org.ajax4jsf.webapp.BaseXMLFilter doXmlFilter
SEVERE: Exception in the filter chain
javax.servlet.ServletException: Error Parsing /css/tableLayout.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
Caused by: com.sun.facelets.FaceletException: Error Parsing /css/tableLayout.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/imagens/header.jpg]
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
21/01/2010 12:18:24 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@dc64a2) threw exception
javax.faces.FacesException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
21/01/2010 12:18:24 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@1def3f5) threw exception
com.sun.facelets.FaceletException: Error Parsing /css/default.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 org.ajax4jsf.webapp.BaseXMLFilter doXmlFilter
SEVERE: Exception in the filter chain
javax.servlet.ServletException: Error Parsing /css/default.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
Caused by: com.sun.facelets.FaceletException: Error Parsing /css/default.css: Error Traced[line: 1] Content is not allowed in prolog.
        ...
21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/fotos/outra3.jpg]
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
21/01/2010 12:18:24 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@125d568) threw exception
javax.faces.FacesException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/fotos/outra1.jpg]
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
21/01/2010 12:18:25 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@8bf3ec) threw exception
javax.faces.FacesException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
       ...
21/01/2010 12:18:24 com.sun.facelets.FaceletViewHandler handleRenderException
SEVERE: Error Rendering View[/fotos/outra2.jpg]
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
       ...
21/01/2010 12:18:25 com.sun.faces.lifecycle.LifecycleImpl phase
WARNING: executePhase(RENDER_RESPONSE 6,com.sun.faces.context.FacesContextImpl@19d7af3) threw exception
javax.faces.FacesException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
        ...
Criado 21 de janeiro de 2010
Ultima resposta 21 de jan. de 2010
Respostas 4
Participantes 3