Solucionado (ver solução)
Solucionado
(ver solução)
3
respostas

API nao faz requisicoes

Ola, minha API nao esta fazendo nenhuma requisicao pelo PostMan, todas elas respondem com erro 404 Utilizando o PostgreSQL + Flyway Está criando as tabelas normalmente no banco, e fazendo a validacao com o Flyway

Git: https://github.com/Nicolas-S-P/AluraCursos

Segue resultado do Run, nao apresentando nenhum erro e nenhum alerta ao fazer as consultas por qualquer metodo no PostMan:

2022-09-14 09:58:27.850  INFO 11192 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2022-09-14 09:58:28.095  INFO 11192 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
2022-09-14 09:58:28.110  INFO 11192 --- [  restartedMain] o.f.c.i.database.base.BaseDatabaseType   : Database: jdbc:postgresql://localhost:5432/extracao_db (PostgreSQL 10.22)
2022-09-14 09:58:28.144  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbValidate     : Successfully validated 4 migrations (execution time 00:00.015s)
2022-09-14 09:58:28.160  INFO 11192 --- [  restartedMain] o.f.c.i.s.JdbcTableSchemaHistory         : Creating Schema History table "public"."flyway_schema_history" ...
2022-09-14 09:58:28.245  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Current version of schema "public": << Empty Schema >>
2022-09-14 09:58:28.251  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Migrating schema "public" to version "1 - create table minerio"
2022-09-14 09:58:28.281  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Migrating schema "public" to version "2 - create table area"
2022-09-14 09:58:28.299  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Migrating schema "public" to version "3 - create table extracao"
2022-09-14 09:58:28.317  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Migrating schema "public" to version "4 - create table solicitacao"
2022-09-14 09:58:28.329  INFO 11192 --- [  restartedMain] o.f.core.internal.command.DbMigrate      : Successfully applied 4 migrations to schema "public", now at version v4 (execution time 00:00.092s)
2022-09-14 09:58:28.415  INFO 11192 --- [  restartedMain] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
2022-09-14 09:58:28.479  INFO 11192 --- [  restartedMain] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.6.10.Final
2022-09-14 09:58:28.649  INFO 11192 --- [  restartedMain] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
2022-09-14 09:58:28.743  INFO 11192 --- [  restartedMain] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
2022-09-14 09:58:28.948  INFO 11192 --- [  restartedMain] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2022-09-14 09:58:28.956  INFO 11192 --- [  restartedMain] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2022-09-14 09:58:28.999  WARN 11192 --- [  restartedMain] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2022-09-14 09:58:29.280  INFO 11192 --- [  restartedMain] o.s.b.d.a.OptionalLiveReloadServer       : LiveReload server is running on port 35729
2022-09-14 09:58:29.313  INFO 11192 --- [  restartedMain] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
2022-09-14 09:58:29.323  INFO 11192 --- [  restartedMain] com.example.demo.NewApplicationKt        : Started NewApplicationKt in 3.353 seconds (JVM running for 3.998)
2022-09-14 09:58:55.458  INFO 11192 --- [nio-8080-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2022-09-14 09:58:55.458  INFO 11192 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2022-09-14 09:58:55.459  INFO 11192 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Completed initialization in 1 ms
3 respostas

Oi Luciano,

O problema é por conta dos pacotes do seu projeto.

Pela estrutura de diretórios o pacote principal do projeto é: com.teste.extracao, mas as suas classes estão declarando os pacotes com outra estrutura:

package br.com.alura.forum.controller
package br.com.alura.forum.model
package br.com.alura.forum.service
etc...

Ajustes os pacotes nas classes que vai resolver o problema.

Realizei a chamada correta dos pacotes, porem ele esta apresentando erro Nos metodos ainda, esse é meu retorno no /extracao


    "content": [],
    "pageable": {
        "sort": {
            "empty": false,
            "sorted": true,
            "unsorted": false
        },
        "offset": 0,
        "pageSize": 5,
        "pageNumber": 0,
        "paged": true,
        "unpaged": false
    },
    "last": true,
    "totalPages": 0,
    "totalElements": 0,
    "size": 5,
    "number": 0,
    "sort": {
        "empty": false,
        "sorted": true,
        "unsorted": false
    },
    "first": true,
    "numberOfElements": 0,
    "empty": true
solução!

Esse retorno está ok. São os dados da paginação, e nessa consulta não trouxe nenhum registro do banco de dados.

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software