Approved by the Spring team, this repo is a fork of the spring-projects/spring-petclinic. It allows the Spring community to maintain a Petclinic version with a plain old Spring Framework configuration and with a 3-layer architecture (i.e. presentation --> service --> repository). The "canonical" implementation is now based on Spring Boot, Thymeleaf and aggregate-oriented domain.
See the presentation here (2017 update)
git clone https://github.com/spring-petclinic/spring-framework-petclinic.git
cd spring-framework-petclinic
./mvnw jetty:run-war
You can then access petclinic here: http://localhost:8080/
Our issue tracker is available here: https://github.com/spring-petclinic/spring-framework-petclinic/issues
In its default configuration, Petclinic uses an in-memory database (HSQLDB) which gets populated at startup with data. A similar setups is provided for MySql and PostgreSQL in case a persistent database configuration is needed. To run petclinic locally using persistent database, it is needed to run with profile defined in main pom.xml file.
For MySQL database, it is needed to run with 'MySQL' profile defined in main pom.xml file.
./mvnw jetty:run-war -P MySQL
Before do this, would be good to check properties defined in MySQL profile inside pom.xml file.
<properties>
<jpa.database>MYSQL</jpa.database>
<jdbc.driverClassName>com.mysql.cj.jdbc.Driver</jdbc.driverClassName>
<jdbc.url>jdbc:mysql://localhost:3306/petclinic?useUnicode=true</jdbc.url>
<jdbc.username>root</jdbc.username>
<jdbc.password>petclinic</jdbc.password>
</properties>
You could start MySql locally with whatever installer works for your OS, or with docker:
docker run --name mysql-petclinic -e MYSQL_ROOT_PASSWORD=petclinic -e MYSQL_DATABASE=petclinic -p 3306:3306 mysql:5.7.8
For PostgreSQL database, it is needed to run with 'PostgreSQL' profile defined in main pom.xml file.
./mvnw jetty:run-war -P PostgreSQL
Before do this, would be good to check properties defined in PostgreSQL profile inside pom.xml file.
<properties>
<jpa.database>POSTGRESQL</jpa.database>
<jdbc.driverClassName>org.postgresql.Driver</jdbc.driverClassName>
<jdbc.url>jdbc:postgresql://localhost:5432/petclinic</jdbc.url>
<jdbc.username>postgres</jdbc.username>
<jdbc.password>petclinic</jdbc.password>
</properties>
You could alos start PostgreSQL locally with whatever installer works for your OS, or with docker:
docker run --name postgres-petclinic -e POSTGRES_PASSWORD=petclinic -e POSTGRES_DB=petclinic -p 5432:5432 -d postgres:9.6.0
The following items should be installed in your system:
- Java 8 (waiting the wro4j JDK 9 compatibility fix for Java 9, 10 and 11 support)
- Maven 3.3+ (http://maven.apache.org/install.html)
- git command line tool (https://help.github.com/articles/set-up-git)
- Jetty 9.4+ or Tomcat 9+
- Your prefered IDE
- Eclipse with the m2e plugin. Note: when m2e is available, there is an m2 icon in Help -> About dialog. If m2e is not there, just follow the install process here: http://www.eclipse.org/m2e/
- Spring Tools Suite (STS)
- IntelliJ IDEA
- On the command line
git clone https://github.com/spring-petclinic/spring-framework-petclinic.git
- Inside Eclipse or STS
File -> Import -> Maven -> Existing Maven project
Then either build on the command line ./mvnw generate-resources or using the Eclipse launcher (right click on project and Run As -> Maven install) to generate the CSS.
Configure a Jetty or a Tomcat web container then deploy the spring-petclinic.war file.
- Inside IntelliJ IDEA
In the main menu, select File > Open and select the Petclinic pom.xml. Click on the Open button.
CSS files are generated from the Maven build. You can either build them on the command line ./mvnw generate-resources
or right click on the spring-petclinic project then Maven -> Generates sources and Update Folders.
Go to the Run -> Edit Configuration then configure a Tomcat or a Jetty web container. Deploy the spring-petclinic.war file.
Run the application by clicking on the Run icon.
- Navigate to Petclinic
Visit http://localhost:8080 in your browser.
The following items should be installed in your system:
| Java Config | |
|---|---|
| Java config branch | Petclinic uses XML configuration by default. In case you'd like to use Java Config instead, there is a Java Config branch available here |
| Inside the 'Web' layer | Files |
|---|---|
| Spring MVC - XML integration | mvc-view-config.xml |
| Spring MVC - ContentNegotiatingViewResolver | mvc-view-config.xml |
| JSP custom tags | WEB-INF/tags, createOrUpdateOwnerForm.jsp |
| JavaScript dependencies | JavaScript libraries are declared as webjars in the pom.xml |
| Static resources config | Resource mapping in Spring configuration |
| Static resources usage | htmlHeader.tag, footer.tag |
| Thymeleaf | In the late 2016, the original Spring Petclinic has moved from JSP to Thymeleaf. |
| 'Service' and 'Repository' layers | Files |
|---|---|
| Transactions | business-config.xml, ClinicServiceImpl.java |
| Cache | tools-config.xml, ClinicServiceImpl.java |
| Bean Profiles | business-config.xml, ClinicServiceJdbcTests.java, PetclinicInitializer.java |
| JDBC | business-config.xml, jdbc folder |
| JPA | business-config.xml, jpa folder |
| Spring Data JPA | business-config.xml, springdatajpa folder |
The Spring Petclinic master branch in the main spring-projects GitHub org is the "canonical" implementation, currently based on Spring Boot and Thymeleaf.
This spring-framework-petclinic project is one of the several forks hosted in a special GitHub org: spring-petclinic. If you have a special interest in a different technology stack that could be used to implement the Pet Clinic then please join the community there.
One of the best parts about working on the Spring Petclinic application is that we have the opportunity to work in direct contact with many Open Source projects. We found some bugs/suggested improvements on various topics such as Spring, Spring Data, Bean Validation and even Eclipse! In many cases, they've been fixed/implemented in just a few days. Here is a list of them:
| Name | Issue |
|---|---|
| Spring JDBC: simplify usage of NamedParameterJdbcTemplate | SPR-10256 and SPR-10257 |
| Bean Validation / Hibernate Validator: simplify Maven dependencies and backward compatibility | HV-790 and HV-792 |
| Spring Data: provide more flexibility when working with JPQL queries | DATAJPA-292 |
| Dandelion: improves the DandelionFilter for Jetty support | 113 |
The issue tracker is the preferred channel for bug reports, features requests and submitting pull requests.
For pull requests, editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at http://editorconfig.org.