/singleton-quarkus-config-relatorio

Primary LanguageHTML

code-with-quarkus project

This project uses Quarkus, the Supersonic Subatomic Java Framework.

If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .

Running the application in dev mode

You can run your application in dev mode that enables live coding using:

./mvnw quarkus:dev

Packaging and running the application

The application can be packaged using ./mvnw package. It produces the code-with-quarkus-1.0.0-SNAPSHOT-runner.jar file in the /target directory. Be aware that it’s not an über-jar as the dependencies are copied into the target/lib directory.

The application is now runnable using java -jar target/code-with-quarkus-1.0.0-SNAPSHOT-runner.jar.

Creating a native executable

You can create a native executable using: ./mvnw package -Pnative.

Or, if you don't have GraalVM installed, you can run the native executable build in a container using: ./mvnw package -Pnative -Dquarkus.native.container-build=true.

You can then execute your native executable with: ./target/code-with-quarkus-1.0.0-SNAPSHOT-runner

If you want to learn more about building native executables, please consult https://quarkus.io/guides/building-native-image.

Relato sobre a mudança no projeto ao padrao 'Singleton'

Ao modificar os endpoints referentes ao metodo PUT tanto de '/config' quanto de '/relatorio', nos descaracterizamos a instancia unica do padrao, ja que atribuimos diretamente novos dados ao objeto. Modificando os dados utilizando o caminho '/config', estamos modificando os dados de nosso objeto config, e apos a alteração feita na aplicação, os dados modificados em outros caminhos irao criar um novo objeto, ao contrario do que diz o padrao singleton que discrimina apenas 1 objeto por aplicação.