-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
56 lines (33 loc) · 1.66 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
Why?
====
While play is an excellent framework, I had to do a lot of digging and only learned a little-bit each time. I wanted to help others if I could and get a "full-stack" application going that had no setup cost, but still provided a full-stack template including a working SQL as well as NOSQL database persistence. I hope this helps the community.
Play Scala application for tracking painters and their work.
===========================================================
This application is derived from the "play-scala" template.
Many of the components are not yet used in the application, however this will change as time goes on and I get a chance to polish it further.
Controllers
===========
- PainterController.scala:
Returns single "Painter" record.
- HomeController.scala: - NOT Used yet
Shows how to handle simple HTTP requests.
- AsyncController.scala: - NOT Used yet
Shows how to do asynchronous programming when handling a request.
- CountController.scala: - NOT Used yet
Shows how to inject a component into a controller and use the component when
handling requests.
Components
==========
- Module.scala:
Shows how to use Guice to bind all the components needed by your application.
- Counter.scala: - NOT Used yet
An example of a component that contains state, in this case a simple counter.
- ApplicationTimer.scala: - NOT Used yet
An example of a component that starts when the application starts and stops
when the application stops.
Filters
=======
- Filters.scala: - NOT Used yet
Creates the list of HTTP filters used by your application.
- ExampleFilter.scala - NOT Used yet
A simple filter that adds a header to every response.