hub / github.com/cloudfoundry/java-test-applications

github.com/cloudfoundry/java-test-applications @play-2.1.4

Chat with this repo

repository ↗ · DeepWiki ↗ · release play-2.1.4 ↗ · + Follow

69 symbols 189 edges 8 files 1 documented · 1%

What it actually does AI analysis from the code graph — generated when you open this

loading…

README

Java Test Applications

A collection of applications used for testing the Java buildpack.

Applications

Name	Output Destination	Description
`grails-application`	HTTP Response	A Grails application created by issuing `grails create-app`
`groovy-application`	`System.out`	An application started with `groovy`. Since this application does not service web requests, you can select `none` for its subdomain and domain when you deploy it to Cloud Foundry.
`java-application`	`System.out`	An application started with `java -jar`. Since this application does not service web requests, you can select `none` for its subdomain and domain when you deploy it to Cloud Foundry.
`play-application`	HTTP Response	A Play application created by issuing `play new play-application`
`spring-boot-application`	HTTP Response	A Spring Boot CLI web application
`web-application`	HTTP Response	A web application that uses Spring MVC and Servlet 3

Output Content

All applications output the following content:

java.lang:type=Runtime/ClassPath
System.getenv()
java.lang:type=Runtime/InputArguments
System.getProperties()

All web application output the following additional content:

All request headers

Building

This project is built with Gradle. To build the artifacts, install Play and Grails and then run:

./gradlew

Deploying to Cloud Foundry

Each test application contains a manifest.yml file which allows the built application to be deployed to Cloud Foundry by simply issuing:

cf push

To avoid clashing with the URLs of other applications, you should specify your own subdomain for the application (unless the test application does not need a subdomain).

Failure Testing

Failure testing is supported for each of the above applications by setting a suitable environment variable.

If the environment variable FAIL_INIT is set, the application will fail to initialize:

cf set-env <application name> FAIL_INIT true

If the environment variable FAIL_OOM is set, the application will repeatedly exhaust the heap until the JVM is killed:

cf set-env <application name> FAIL_OOM true

Running Tests

To run the tests, do the following:

./gradlew

Contributing

Pull requests are welcome; see the contributor guidelines for details.

License

The Tomcat Builder is released under version 2.0 of the Apache License.

Core symbols most depended-on inside this repo

getInputArguments

called by 4

play-application/app/util/Probe.java

getClassPath

called by 4

play-application/app/util/Probe.java

index

called by 3

play-application/app/controllers/Application.java

Probe

called by 0

play-application/app/util/Probe.java

Shape

Function 47

Method 15

Class 7

Languages

TypeScript68%

Java32%

Modules by API surface

play-application/public/javascripts/jquery-1.9.0.min.js47 symbols

java-application/src/main/java/com/gopivotal/test/Application.java9 symbols

web-application/src/main/java/com/gopivotal/test/TestController.java4 symbols

play-application/app/util/Probe.java4 symbols

web-application/src/main/java/com/gopivotal/test/ApplicationInitializer.java2 symbols

play-application/app/controllers/Application.java2 symbols

web-application/src/main/java/com/gopivotal/test/WebConfiguration.java1 symbols

For agents

$ claude mcp add java-test-applications \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact