You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
Glyn Normington
committed
Support Play 2.2
Refactor Play framework to encapsulate the application-specific pieces
in a "PlayApp" abstraction defined by the BasePlayApp class. This
class has two subclasses: PlayAppPost22 for Play 2.2 and upwards and
PlayAppPre22 for Play 2.1.x and earlier (actually no earlier than 2.0
since older versions are not supported).
PlayAppPre22 is further subclassed by PlayAppPre22Dist and
PlayAppPre22Staged to represent the differences between Play 2.0/2.1
dist and staged applications, respectively.
PlayAppFactory isolates the using code (the Play container and some
associated frameworks) from the concrete subclasses of BasePlayApp.
Play version parsing and the naming requirements for the Play JAR are
both tightened up.
Play 2.2 support consists of:
1. Looking for a different style of start script. The start script is
now present in the bin directory and named after the application.
2. Updating the classpath variable in the start script (for both dist
and staged apps, which are now identical in structure in Play 2.2).
3. Supporting Play 2.2 style Java options by pre-pending '-J' to each
Java option.
4. Avoiding incompatible minimum and maximum heap sizes. Play 2.2 sets
-Xms to a large value by default and when this exceeds our calculated
-Xmx the JVM fails to initialise. Since we do not normally specify
-Xms, we set this to a low value (currently 2M since 1M is
insufficient for the JVM to initialise), but note that we do this for
Play 2.2 only.
[#58432326]
Copy file name to clipboardExpand all lines: docs/container-play.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ The Play Container allows Play applications to be run.
3
3
4
4
<table>
5
5
<tr>
6
-
<td><strong>Detection Criteria</strong></td><td>The files <tt>start</tt> and <tt>lib/play.play_*.jar</tt> (or <tt>staged/play_*.jar</tt>) exist in the application
6
+
<td><strong>Detection Criteria</strong></td><td>The Play start script and the Play runtime JAR exist in the appropriate subdirectories of the application
7
7
directory or one of its immediate subdirectories (but not in both)</td>
Copy file name to clipboardExpand all lines: docs/util-other.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,9 @@
1
1
# Other Utiltities
2
2
The buildpack provides a number of other utilities that may help in implementing components.
3
3
4
-
5
4
## [`JavaBuildpack::Util::GroovyUtils`][]
6
5
The `GroovyUtils` class provides a set of methods for finding groovy files and determing if they are of any special kind (e.g. they have a main method, they are a pogo, etc.).
7
6
8
-
## [`JavaBuildpack::Util::PlayUtils`][]
9
-
The `PlayUtils` class provides a set of methods for determing information about a Play Framework application.
10
-
11
7
## [`JavaBuildpack::Util::Properties`][]
12
8
The `Properties` class provides a Ruby class that can read in a Java properties file and acts as a `Hash` with that data.
13
9
@@ -17,7 +13,6 @@ The `ResourceUtils` class provides an abstract around the `resources` directory
17
13
## [`JavaBuildpack::Util::ServiceUtils`][]
18
14
The `ServiceUtils` class provides a set of methods for finding a given service in the `VCAP_SERVICES` payload.
0 commit comments