24 |
25 | {{ partial "footer.html" . }}
26 |
--------------------------------------------------------------------------------
/content/news/2019-02-15-scalatra-2-6-5-released.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Scalatra 2.6.5 is out"
3 | layout: news
4 | author: Magnolia.K
5 | twitter: magnolia_k_
6 | date: 2019-02-15
7 | ---
8 |
9 | The Scalatra team is pleased to announce the release of version 2.6.5 of the framework.
10 |
11 |
12 |
13 | Here's the full list of changes for version 2.6.5:
14 |
15 | ### Modules
16 |
17 | * Upgrade Json4s 3.6.3
18 | * Date & Time support for Swagger
19 |
20 | We have a plan to move [http4s](https://github.com/http4s/http4s) in Scalatra 3.0.0. We will continue to maintain Scalatra 2.x systems, but we will deprecate unnecessary functions for future Scalatra 3.0.0 in order to improve future maintainability.
21 |
22 | Thanks to all committers and contributors!
23 |
--------------------------------------------------------------------------------
/content/guides/2.5/resources/wro4j.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: wro4j
3 | layout: guides-2.5
4 | ---
5 |
6 | The [Web Resource Optimizer for Java (wro4j)][wro4j] is a Free and Open Source Java
7 | project which brings together almost all the modern web tools for
8 | compressing, building, and minifying your JavaScript and CSS assets: JsHint,
9 | CssLint, JsMin, Google Closure compressor, YUI Compressor, UglifyJs,
10 | Dojo Shrinksafe, Css Variables Support, JSON Compression, Less, Sass,
11 | CoffeeScript and much more.
12 |
13 | You can add wro4j to your Scalatra project by using the xsbt-wro4j plugin.
14 |
15 | See the [xsbt-wro4j-plugin][xsbt-wro4j] project documentation for details of
16 | how to do so.
17 |
18 | [wro4j]: http://code.google.com/p/wro4j/
19 | [xsbt-wro4j]: https://github.com/BowlingX/xsbt-wro4j-plugin/
20 |
--------------------------------------------------------------------------------
/layouts/section/news.html:
--------------------------------------------------------------------------------
1 | {{ partial "header.html" . }}
2 |
3 |
4 |
5 |
6 |
7 |
News
8 | {{ range .Data.Pages }}
9 |
10 |
11 | {{ .Title }}{{ if .Draft }} #Draft{{ end }}
12 |
13 |
27 |
28 | {{ partial "footer.html" . }}
29 |
--------------------------------------------------------------------------------
/content/guides/2.3/testing/scalatratest.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.3/guides/testing/scalatratest.html
4 | title: ScalatraTest
5 | layout: guides-2.3
6 | ---
7 |
8 | #### Dependency
9 |
10 | ```scala
11 | "org.scalatra" %% "scalatra-test" % "{{< 2-3-scalatra_version >}}" % "test"
12 | ```
13 |
14 | #### Usage guide
15 |
16 | Create an instance of `org.scalatra.test.ScalatraTests`. Be sure to call
17 | `start()` and `stop()` before and after your test suite.
18 |
19 |
20 |
21 | ### Testing FAQ
22 |
23 | #### How do I set a servlet init parameter?
24 |
25 | scalatra-test is built on an embedded Jetty server, so it
26 | does not read your `web.xml`. Most things you can do in a `web.xml` can be
27 | done from the context of the tester object.
28 | Call this in the constructor of your servlet:
29 |
30 | ```scala
31 | servletContextHandler.setInitParameter("db.username", "ross")
32 | ```
33 |
--------------------------------------------------------------------------------
/content/guides/2.4/testing/scalatratest.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.4/guides/testing/scalatratest.html
4 | title: ScalatraTest
5 | layout: guides-2.4
6 | ---
7 |
8 | #### Dependency
9 |
10 | ```scala
11 | "org.scalatra" %% "scalatra-test" % "{{< 2-4-scalatra_version >}}" % "test"
12 | ```
13 |
14 | #### Usage guide
15 |
16 | Create an instance of `org.scalatra.test.ScalatraTests`. Be sure to call
17 | `start()` and `stop()` before and after your test suite.
18 |
19 |
20 |
21 | ### Testing FAQ
22 |
23 | #### How do I set a servlet init parameter?
24 |
25 | scalatra-test is built on an embedded Jetty server, so it
26 | does not read your `web.xml`. Most things you can do in a `web.xml` can be
27 | done from the context of the tester object.
28 | Call this in the constructor of your servlet:
29 |
30 | ```scala
31 | servletContextHandler.setInitParameter("db.username", "ross")
32 | ```
33 |
--------------------------------------------------------------------------------
/content/guides/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Documentation
3 | ---
4 |
5 | ### Scalatra 3.0.x / 3.1.x
6 |
7 | - [Guides](/guides/3.0/)
8 | - [Scaladoc](http://javadoc.io/doc/org.scalatra/scalatra-unidoc_2.13/3.0.0)
9 |
10 | ### Scalatra 2.8.x
11 |
12 | - [Guides](/guides/2.8/)
13 | - [Scaladoc](http://javadoc.io/doc/org.scalatra/scalatra-unidoc_2.13/2.8.0)
14 |
15 |
16 | ### Scalatra 2.7.x
17 |
18 | - [Guides](/guides/2.7/)
19 | - [Scaladoc](http://javadoc.io/doc/org.scalatra/scalatra-unidoc_2.12/2.7.0)
20 |
21 |
22 | ### Scalatra 2.6.x
23 |
24 | - [Guides](/guides/2.6/)
25 | - [Scaladoc](http://javadoc.io/doc/org.scalatra/scalatra-unidoc_2.12/2.6.0)
26 |
27 | ### Scalatra 2.5.x
28 |
29 | - [Guides](/guides/2.5/)
30 | - [Scaladoc](/apidocs/2.5/)
31 |
32 | ### Scalatra 2.4.x
33 |
34 | - [Guides](/guides/2.4/)
35 | - [Scaladoc](/apidocs/2.4/)
36 |
37 | ### Scalatra 2.3.x
38 |
39 | - [Guides](/guides/2.3/)
40 | - [Scaladoc](/apidocs/2.3/)
41 |
--------------------------------------------------------------------------------
/content/news/2012-12-07-ivan-talks-scalatra-on-scalatypes-podcast.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Scalatypes Podcast
3 | layout: news
4 | author: Dave Hrycyszyn
5 | twitter: futurechimp
6 | date: 2012-12-07
7 | aliases:
8 | - /2012/12/07/ivan-talks-scalatra-on-scalatypes-podcast.html
9 | ---
10 |
11 | One of Scalatra's core developers,
12 | [Ivan Porto Carrero](http://twitter.com/casualjim), showed up on this week's
13 | [Scalatypes](http://scalatypes.com/episode-24-ivan-porto-carrero-on-scalatra-and-json4s) podcast, as the featured interviewee.
14 |
15 |
16 |
17 |
18 | In the hour-long podcast, Ivan is interviewed by [Yuvi Masory](http://twitter.com/ymasory). The conversation is a solid introduction to Scalatra:
19 | the philosophy behind the code, its current feature set, and a
20 | quick look at upcoming developments in Scalatra 2.3 and 3.0.
21 |
22 | A set of slides from the talk is also available
23 | [on Slideshare](http://www.slideshare.net/casualjim/scalatra-22).
24 |
--------------------------------------------------------------------------------
/content/news/2013-09-20-scalatra-in-action-routing-chapter-released.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: "Scalatra in Action: Routing chapter available"
3 | layout: news
4 | author: Dave Hrycyszyn
5 | twitter: futurechimp
6 | date: 2013-09-20
7 | aliases:
8 | - /2013/09/20/scalatra-in-action-routing-chapter-released.html
9 | ---
10 |
11 | Our book [Scalatra in Action](http://www.manning.com/carrero2/), available from
12 | Manning Publications, has been steadily ticking along over the summer.
13 | A new chapter, on RESTful application development using Scalatra's routing
14 | DSL, is now available.
15 |
16 |
17 |
18 |
19 | This chapter gives you an overview of both how to tie URLs to your Scalatra
20 | routes, and also *why* you'd want to structure your application routes to
21 | use HTTP to its best advantage, using RESTful conventions.
22 |
23 | Chapter 4, "Working with user input", is currently awaiting incorporation in
24 | the next MEAP update for the book and will be available soon.
25 |
--------------------------------------------------------------------------------
/content/guides/2.3/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.3/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.3
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 | Use solid base components. For instance, servlets aren't cool, but they are
19 | extremely stable and have a huge community behind them. At the same time, work
20 | to advance the state of web application development by using new techniques
21 | and approaches.
22 |
23 | ### 4. Love HTTP
24 |
25 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
26 |
--------------------------------------------------------------------------------
/content/guides/2.4/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.4/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.4
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/guides/2.5/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.5/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.5
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/guides/2.6/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.6/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.6
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/guides/2.7/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.7/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.7
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/guides/2.8/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.8/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-2.8
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/guides/3.0/scalatra-philosophy.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /3.0/guides/scalatra-philosophy.html
4 | title: Scalatra's philosophy
5 | layout: guides-3.0
6 | ---
7 |
8 | ### 1. Start small, build upwards
9 |
10 | Start with a small core, and have lots of easy integrations for common tasks.
11 |
12 | ### 2. Freedom
13 |
14 | Allow the user freedom to choose whatever structure and libraries make the most sense for the application being built.
15 |
16 | ### 3. Solid, but not stolid
17 |
18 |
19 | Use solid base components. For instance, servlets aren't cool, but they are
20 | extremely stable and have a huge community behind them. At the same time, work
21 | to advance the state of web application development by using new techniques
22 | and approaches.
23 |
24 | ### 4. Love HTTP
25 |
26 | Embrace HTTP and its stateless nature. People get into trouble when they fool themselves into thinking things which aren't true - fancy server-side tricks to give an illusion of statefulness aren't for us.
27 |
--------------------------------------------------------------------------------
/content/news/2012-09-13-new-tutorials.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: New tutorials available
3 | layout: news
4 | author: Dave Hrycyszyn
5 | twitter: futurechimp
6 | date: 2012-09-13
7 | aliases:
8 | - /2012/09/13/new-tutorials.html
9 | ---
10 |
11 | Many thanks to [Jos Dirksen](https://twitter.com/josdirksen) of
12 | [smartjava.org](http://smartjava.org), who has been working on a series of
13 | Scalatra tutorials. The [first part](http://www.smartjava.org/content/tutorial-getting-started-scala-and-scalatra-part-i)
14 | offers a very quick intro to Scalatra and some tips on Eclipse integration.
15 |
16 |
17 |
18 |
19 | The [second part](http://www.smartjava.org/content/tutorial-getting-started-scala-and-scalatra-part-ii) gives an overview of an embedded Jetty setup, and then moves
20 | into RESTful API construction techniques using case classes and JSON. The tutorial
21 | finishes off with an introduction to Scalatra testing using the Specs2 testing
22 | framework, including Eclipse configs for test runners.
23 |
--------------------------------------------------------------------------------
/content/guides/2.5/views/inline-html.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Inline HTML
3 | layout: guides-2.5
4 | ---
5 |
6 | The simplest method of rendering a view is by using inline HTML.
7 |
8 | Unlike frameworks in most other languages, Scalatra can use Scala's built-in
9 | XML literals to output XML directly as a return value from an action:
10 |
11 | ```scala
12 | def get("/") {
13 | contentType="text/html"
14 |
15 |
16 | Test
17 | Test Body for {uri("/")}
18 |
19 | }
20 | ```
21 |
22 | Note the use of the curly braces on the `{uri("/")}` part of the inlined view.
23 | This tells Scalatra to render Scala code.
24 |
25 | This would be a very poor way to structure complex views for a large application, but it might
26 | be useful if your templating needs are quite simple (or you're just cranking out a quick prototype).
27 |
28 | Normally you'll want more structure than inline HTML can provide, so that you can separate
29 | your views from your controller actions and routing.
30 |
--------------------------------------------------------------------------------
/content/guides/2.6/views/inline-html.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Inline HTML
3 | layout: guides-2.6
4 | ---
5 |
6 | The simplest method of rendering a view is by using inline HTML.
7 |
8 | Unlike frameworks in most other languages, Scalatra can use Scala's built-in
9 | XML literals to output XML directly as a return value from an action:
10 |
11 | ```scala
12 | def get("/") {
13 | contentType="text/html"
14 |
15 |
16 | Test
17 | Test Body for {uri("/")}
18 |
19 | }
20 | ```
21 |
22 | Note the use of the curly braces on the `{uri("/")}` part of the inlined view.
23 | This tells Scalatra to render Scala code.
24 |
25 | This would be a very poor way to structure complex views for a large application, but it might
26 | be useful if your templating needs are quite simple (or you're just cranking out a quick prototype).
27 |
28 | Normally you'll want more structure than inline HTML can provide, so that you can separate
29 | your views from your controller actions and routing.
30 |
--------------------------------------------------------------------------------
/content/guides/2.7/views/inline-html.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Inline HTML
3 | layout: guides-2.7
4 | ---
5 |
6 | The simplest method of rendering a view is by using inline HTML.
7 |
8 | Unlike frameworks in most other languages, Scalatra can use Scala's built-in
9 | XML literals to output XML directly as a return value from an action:
10 |
11 | ```scala
12 | def get("/") {
13 | contentType="text/html"
14 |
15 |
16 | Test
17 | Test Body for {uri("/")}
18 |
19 | }
20 | ```
21 |
22 | Note the use of the curly braces on the `{uri("/")}` part of the inlined view.
23 | This tells Scalatra to render Scala code.
24 |
25 | This would be a very poor way to structure complex views for a large application, but it might
26 | be useful if your templating needs are quite simple (or you're just cranking out a quick prototype).
27 |
28 | Normally you'll want more structure than inline HTML can provide, so that you can separate
29 | your views from your controller actions and routing.
30 |
--------------------------------------------------------------------------------
/content/guides/2.8/views/inline-html.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Inline HTML
3 | layout: guides-2.8
4 | ---
5 |
6 | The simplest method of rendering a view is by using inline HTML.
7 |
8 | Unlike frameworks in most other languages, Scalatra can use Scala's built-in
9 | XML literals to output XML directly as a return value from an action:
10 |
11 | ```scala
12 | def get("/") {
13 | contentType="text/html"
14 |
15 |
16 | Test
17 | Test Body for {uri("/")}
18 |
19 | }
20 | ```
21 |
22 | Note the use of the curly braces on the `{uri("/")}` part of the inlined view.
23 | This tells Scalatra to render Scala code.
24 |
25 | This would be a very poor way to structure complex views for a large application, but it might
26 | be useful if your templating needs are quite simple (or you're just cranking out a quick prototype).
27 |
28 | Normally you'll want more structure than inline HTML can provide, so that you can separate
29 | your views from your controller actions and routing.
30 |
--------------------------------------------------------------------------------
/content/guides/3.0/views/inline-html.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Inline HTML
3 | layout: guides-3.0
4 | ---
5 |
6 | The simplest method of rendering a view is by using inline HTML.
7 |
8 | Unlike frameworks in most other languages, Scalatra can use Scala's built-in
9 | XML literals to output XML directly as a return value from an action:
10 |
11 | ```scala
12 | def get("/") {
13 | contentType="text/html"
14 |
15 |
16 | Test
17 | Test Body for {uri("/")}
18 |
19 | }
20 | ```
21 |
22 | Note the use of the curly braces on the `{uri("/")}` part of the inlined view.
23 | This tells Scalatra to render Scala code.
24 |
25 | This would be a very poor way to structure complex views for a large application, but it might
26 | be useful if your templating needs are quite simple (or you're just cranking out a quick prototype).
27 |
28 | Normally you'll want more structure than inline HTML can provide, so that you can separate
29 | your views from your controller actions and routing.
30 |
--------------------------------------------------------------------------------
/themes/bootie-docs/layouts/partials/sidebar-list.html:
--------------------------------------------------------------------------------
1 | {{ $baseUrl := .Site.BaseURL }}
2 |
The first steps you take when learning something new are usually the
12 | most difficult. Our code generators and step-by-step instructions
13 | can help ease you into Scalatra development.
Understanding a Scalatra project isn't difficult, and it can save you
18 | a lot of time if you understand a bit about what's happening under the hood.
19 | Here are the basics.
15 |
16 | See
17 | scalatra-gzip
18 | for a minimal and standalone project containing the example in this guide.
19 |
20 |
21 | ---
22 |
23 | ## Example
24 |
25 | This servlet will reply with compressed content if and only if the client provides
26 | an `Accept-Header` indicating it understands gzip.
27 |
28 | ```scala
29 | class GZipApp extends ScalatraServlet with GZipSupport {
30 |
31 | get("/") {
32 |
33 |
34 |
39 |
40 |
41 | }
42 | }
43 | ```
44 |
--------------------------------------------------------------------------------
/content/guides/2.4/http/gzip.md:
--------------------------------------------------------------------------------
1 | ---
2 | aliases:
3 | - /2.4/guides/http/gzip.html
4 | title: Gzip
5 | layout: guides-2.4
6 | ---
7 |
8 | Bandwidth can be wasted when using verbose plaintext formats such as XML, leading
9 | to a poor user experience for your apps.
10 | Fortunately, many clients can accept compressed content and Scalatra lets you
11 | compress server responses without any change to your business logic.
12 | Just mix in `GZipSupport`.
13 |
14 |
15 |
16 | See
17 | scalatra-gzip
18 | for a minimal and standalone project containing the example in this guide.
19 |
20 |
21 | ---
22 |
23 | ## Example
24 |
25 | This servlet will reply with compressed content if and only if the client provides
26 | an `Accept-Header` indicating it understands gzip.
27 |
28 | ```scala
29 | class GZipApp extends ScalatraServlet with GZipSupport {
30 |
31 | get("/") {
32 |
33 |
34 |