JSF problem. XML file does not appear to have any style information associated with it [duplicate] [Solved] (Java in General forum at Coderanch)

Ranch Hand

Posts: 219

2

posted 5 days ago

I'm initiating in java jsf, I created an xhtml simple to show table in localhost but I am receiving this error "This XML file does not appear to have any style information associated with it. The document tree is shown below." I don't have any idea of to solve this.
My project is very simple is only to display a jsf table with records of mysql table.
Below is my project.
Especialidade:

EspecialidadesDAO:

package itc.itcsystems.beans;

import java.io.Serializable;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.ArrayList;
import java.util.List;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;

/**
 *
 * @author Cezar Apulchro
 */

@ManagedBean
@SessionScoped
public class EspecialidadesDAO implements Serializable
{
    public Connection conectar;
    public Connection conectardb;
    
    private static final long serialVersionUID = 1L;
    
    public EspecialidadesDAO()
    {
        conectar = new Conectar_Banco_W00().getConnection();
        
    }
    
    public List<Especialidade> getEspecialidade()
    {
        String LISTHemog = "SELECT Especialidade "
                + "FROM Tabela_Especialidades_Medicas";
       
        Connection conexao = null;
        PreparedStatement pstm = null;
        ResultSet rs = null;
        ArrayList<Especialidade> medico = new ArrayList<Especialidade>();
        
        try
        {            
            conexao = new Conectar_Banco_W00().getConnection();
            pstm = conexao.prepareStatement(LISTHemog);
            
            rs = pstm.executeQuery();
            
            while (rs.next())                
            {
                Especialidade especialidade = new Especialidade();
                especialidade.setEspecialidade(rs.getString("Especialidade"));
                
                medico.add(especialidade);
            }
            Conectar_Banco_W00.fecharConexao(conexao, pstm, rs);
        }
        catch(SQLException e)
        {
            e.printStackTrace();
        }
        return medico;
    }
    
}

JSF to display table:

Dependencies:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" 
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
                             http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

<groupId>itc.itcsystems</groupId>
    <artifactId>ITC_Systems_ClientesMedicos</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>war</packaging>

<name>ITC_Systems_ClientesMedicos</name>

<properties>
        <endorsed.dir>${project.build.directory}/endorsed</endorsed.dir>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    </properties>
    
    <dependencies>
        <dependency>
            <groupId>com.sun.faces</groupId>
            <artifactId>jsf-api</artifactId>
            <version>2.2.20</version>
        </dependency>
        
        <dependency>
            <groupId>com.sun.faces</groupId>
            <artifactId>jsf-impl</artifactId>
            <version>2.2.20</version>
        </dependency>
        
        <dependency>
            <groupId>javax.servlet.jsp.jstl</groupId>
            <artifactId>jstl</artifactId>
            <version>1.2</version>
        </dependency>

<dependency>
            <groupId>javax</groupId>
            <artifactId>javaee-web-api</artifactId>
            <version>7.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

<build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.1</version>
                <configuration>
                    <source>1.7</source>
                    <target>1.7</target>
                    <compilerArguments>
                        <endorseddirs>${endorsed.dir}</endorseddirs>
                    </compilerArguments>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-war-plugin</artifactId>
                <version>2.3</version>
                <configuration>
                    <failOnMissingWebXml>false</failOnMissingWebXml>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <version>2.6</version>
                <executions>
                    <execution>
                        <phase>validate</phase>
                        <goals>
                            <goal>copy</goal>
                        </goals>
                        <configuration>
                            <outputDirectory>${endorsed.dir}</outputDirectory>
                            <silent>true</silent>
                            <artifactItems>
                                <artifactItem>
                                    <groupId>javax</groupId>
                                    <artifactId>javaee-endorsed-api</artifactId>
                                    <version>7.0</version>
                                    <type>jar</type>
                                </artifactItem>
                            </artifactItems>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

</project>

Result of the execution:

Thanks in advance.

Cezar Apulchro

Ranch Hand

Posts: 219

2

posted 4 days ago

After update web.xml the problem still the same.
My web.xml:

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.1" xmlns="http://xmlns.jcp.org/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
                             http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd">
    <context-param>
        <param-name>javax.faces.PROJECT_STAGE</param-name>
        <param-value>Development</param-value>
    </context-param>
    <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>/faces/*</url-pattern>
    </servlet-mapping>
    
       <servlet-mapping>
               <servlet-name>Faces Servlet</servlet-name>
               <url-pattern>*.jsf</url-pattern>
       </servlet-mapping>
    <session-config>
        <session-timeout>
            30
        </session-timeout>
    </session-config>
    <welcome-file-list>
        <welcome-file>faces/index.xhtml</welcome-file>
    </welcome-file-list>
</web-app>

Thnks.

Cezar Apulchro

Ranch Hand

Posts: 219

2

posted 4 days ago

URL:
http://localhost:8081/ITC_Systems_ClientesMedicos/TabelaEspecialidade.xhtml

Tim Holloway

Saloon Keeper

Posts: 22989

156

I like...

posted 4 days ago

Cezar Apulchro wrote:Sorry:
http://localhost:8081/ITC_Systems_ClientesMedicos/TabelaEspecialidade.jsf

Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.

Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.

And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.

Tim Holloway

Saloon Keeper

Posts: 22989

156

I like...

posted 3 days ago

Cezar Apulchro wrote:Now is HTTP Status 404 after change to:
http://localhost:8081/ITC_Systems_ClientesMedicos/TabelaEspecialidade.jsf

Your WAR is named ITC_Systems_ClientesMedicos?

Your view template file is located in the root of the WAR and named TabelaEspecialidade.xhtml?

Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.

Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.

And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.

Tim Holloway

Saloon Keeper

Posts: 22989

156

I like...

posted 3 days ago

Cezar Apulchro wrote:Yes, how to confirm for you?

I trust you. Although it is very strange if you get a 404 error from TabelaEspecialidade.jsf but a display from TabelaEspecialidade.xhtml. You should be seeing either both or neither.

Perhaps you could take a screen capture of the "404" page for me.

Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.

Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.

And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.

Cezar Apulchro

Ranch Hand

Posts: 219

2

posted 2 days ago

How to send image?

Cezar Apulchro

Ranch Hand

Posts: 219

2

posted 2 days ago

HTTP Status 404 – Não Encontrado
Type Status Report

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Apache Tomcat/9.0.14

Tim Holloway

Saloon Keeper

Posts: 22989

156

I like...

posted 2 days ago

OK. The mystery continues. Can your provide me with a directory tree listing of the TOMCAT_HOME/webapps directory? In linux, you'd use the "tree" utility. I think that DOS has an option like DIR /T.

Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.

Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.

And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.

Tim Holloway

Saloon Keeper

Posts: 22989

156

I like...

posted 2 days ago

Here's some Maven snippets. They're old, but should still work: Or at least indicate what you might need if you upgrade them.

Note that the core JEE jars are "provided", not "compile" scope. Using compile scope would put copies of those JARs into the WAR and cause problems because they'd hide the copies that are build into Tomcat (in the TOMCAT_HOME/lib directory).

Tomcat is not full-stack JEE compliant, which is why in Tomcat the jsf-impl JAR is "compile" scope. For full-stack servers like Wildfly and Websphere, jsf-impl would be "provided" as well, since JSF is built into them.

Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.

Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.

And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.

Cezar Apulchro

Ranch Hand

Posts: 219

2

posted 1 day ago

The correct is, after download jstl-api 1.2 and install manually the problem was solved.
Thanks and best regards.