cb8795755a
* Fixed formatting * Put cp back * Move agent to stage level * Added agents per stage * Added pipeline level agent declaration * Formatted agents * removed : * need steps in every stage * requires files on jenkins, using sonar without a container. 7/10 chance of working * using sonar container. 4/10 chance of working * specify network for sonar container * Use Ruby image * test container * Added selenium.rb with hello world * first headless test * fix quotes * fix quotes * added Headless dependecy * Fix dependency * Install Firefox driver * Attempt to fix missing firefox package * zzzz * corrected firefox * Added geckkodriver * add firefox * Removed extra quotes * Display page title * Comments and simplifying * Point to Petclinic * uncomment all the build stages * comment out steps * comment out steps * use correct port for tomcat * adding first test * adding dockerfile for selenium testing * Added minitest setup * Fix if * Fixed test invokation * Don’t use Petclinic class * Use instance variables * fix expectation * adding volume mounting * Added minitest * using new selenium docker image in test portion of pipeline * using assert for first test * removing dockerfile * one working test |
||
|---|---|---|
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .springBeans | ||
| Jenkinsfile | ||
| petclinic_spec.rb | ||
| pom.xml | ||
| readme.md | ||
| sonar-project.properties | ||
Spring PetClinic Sample Application
Understanding the Spring Petclinic application with a few diagrams
Running petclinic locally
git clone https://github.com/spring-projects/spring-petclinic.git
mvn tomcat7:run
You can then access petclinic here: http://localhost:9966/petclinic/
In case you find a bug/suggested improvement for Spring Petclinic
Our issue tracker is available here: https://github.com/spring-projects/spring-petclinic/issues
Database configuration
In its default configuration, Petclinic uses an in-memory database (HSQLDB) which gets populated at startup with data. A similar setup is provided for MySql in case a persistent database configuration is needed. Note that whenever the database type is changed, the data-access.properties file needs to be updated and the mysql-connector-java artifact from the pom.xml needs to be uncommented.
You may start a MySql database with docker:
docker run -e MYSQL_ROOT_PASSWORD=petclinic -e MYSQL_DATABASE=petclinic -p 3306:3306 mysql:5.7.8
Working with Petclinic in Eclipse/STS
prerequisites
The following items should be installed in your system:
- Maven 3 (http://www.sonatype.com/books/mvnref-book/reference/installation.html)
- git command line tool (https://help.github.com/articles/set-up-git)
- Eclipse with the m2e plugin (m2e is installed by default when using the STS (http://www.springsource.org/sts) distribution of Eclipse)
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://eclipse.org/m2e/download/
Steps:
- In the command line
git clone https://github.com/spring-projects/spring-petclinic.git
- Inside Eclipse
File -> Import -> Maven -> Existing Maven project
Looking for something in particular?
| 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. Thanks to Antoine Rey for his contribution. |
| 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 |
| webjars |
webjars declaration inside pom.xml Resource mapping in Spring configuration sample usage in JSP |
| Dandelion-datatables | ownersList.jsp vetList.jsp web.xml datatables.properties |
| Thymeleaf branch | See here |
| Branch using GemFire and Spring Data GemFire instead of ehcache (thanks Bijoy Choudhury) | See here |
| 'Service' and 'Repository' layers | Files |
|---|---|
| Transactions | business-config.xml ClinicServiceImpl.java |
| Cache | tools-config.xml ClinicServiceImpl.java |
| Bean Profiles | business-config.xml ClinicServiceJdbcTests.java web.xml |
| JdbcTemplate | business-config.xml jdbc folder |
| JPA | business-config.xml jpa folder |
| Spring Data JPA | business-config.xml springdatajpa folder |
| Others | Files |
|---|---|
| Gradle branch | See here |
Interaction with other open source projects
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 |
| Eclipse: validation bug when working with .tag/.tagx files (has only been fixed for Eclipse 4.3 (Kepler)). See here for more details. | STS-3294 |