Layershift FTW.

scalatra/scalatra#728

In the JSON handling guide here: http://www.scalatra.org/2.4/guides/formats/json.html

The "Receiving JSON" example is erroneous and does not compile.

Instead of:
request.body.extract[Person]
it should read:
parsedBody.extract[Person]

because http://scalatra.org/index.html shows 2.4's one

We've run into problems with CORS after upgrading scalatra to any version newer than 2.5.0.

This bug was filed scalatra/scalatra#797 and eventually resolved with help of @takezoe.

I would like the CORS documentation page updated with:

1. Mixing in CorsSupport is not required, the documentation makes it looks like it is required.
2. Include this explanation into CORS documentation page:

In Scalatra 2.5.1, a security issue in CORSSupport has been fixed in scalatra/scalatra#635. As the result, the origin which is sent from a client must be declared in the init param org.scalatra.cors.allowedOrigins like:

context.initParameters("org.scalatra.cors.allowedOrigins") = "http://example.com:8080,http://foo.example.com"

The default of this init param is "*". In this case, you have to add following init param:

context.initParameters("org.scalatra.cors.allowCredentials") = "false"

The key to override it is explained at http://scalatra.org/2.2/guides/deployment/standalone.html. We should better explain its requirements:

• implements LifeCycle
• has public, no-arg constructor so it can be instantiated through reflection

I don't see how people are supposed to navigate to http://www.scalatra.org/faq.html

Basically, Heroku requires a standalone deployement+some extra features.
In the Heroku docs, there is some duplication of the standalone docs (e.g. the JettyLauncher).
ideally, all this standalone information should just be in the standalone docs.

For the heroku doc, my proposal is to make a reference to the standalone docs and then add just the heroku specific information. And this I plan to do in the 2.7 docs only

When I start jekyll on ubuntu 12.10 the code is not generated. I do not get any error messages

/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead.
Configuration from /home/ynh/Documents/Doc/scalatra-website/_config.yml
Auto-regenerating enabled: . -> ./_site
[2012-11-04 18:21:58] regeneration: 455 files changed
[2012-11-04 18:21:58] INFO  WEBrick 1.3.1
[2012-11-04 18:21:58] INFO  ruby 1.9.3 (2012-04-20) [x86_64-linux]
[2012-11-04 18:21:58] WARN  TCPServer Error: Address already in use - bind(2)
[2012-11-04 18:21:58] INFO  WEBrick::HTTPServer#start: pid=10509 port=9999

Should we create the 2.5 branch? or should we change the policy on branches?

The Heroku guide hadn't been updated for 2.2.x yet, so the instructions in the guide are somewhat confusing - they reference build.sbt, and don't correspond to the structure of a newly-generated Scalatra project.

I've updated the Heroku example application to use the 2.2.0 structure, and it builds alright. The one question I have is that the (old) docs say to put seq(com.typesafe.startscript.StartScriptPlugin.startScriptForClassesSettings: _*) into project/build.scala. If I put this line inside the build object, this setting is not detected by sbt, and the "stage" task doesn't work, causing Heroku deployment to fail.

I have been able to work around it for the moment by putting this seq by itself inside build.sbt - this way, it gets picked up and used, and everything works.

@casualjim or @rossabaker - is there a correct way that I can get this to work inside project/build.scala? Or should I change the docs to recommend putting this setting in built.sbt? This caught out somebody in the IRC channel today, so I'd like to get it fixed up.

That way the examples will never fall out of date, and they'll be checked nightly by the CI server.

Hi !

I am not able to reach the site since yesterday, I'm surprised that i don't see any one else complaining about it... Am I the only one experiencing this ?

See riak-example for a minimal and standalone project containing the example in this guide.
https://github.com/scalatra/scalatra-website-examples/tree/master/2.6/persistence/riak-example does not exist

There are a number of things we could document better in the Standalone Deployment page.

• merge strategies to avoid conflicts with about.html etc
• set the 'mainClass in assembly' config to JettyLauncher
• change the Jetty dependencies to "compile;container" from just "container"

This is mostly a reminder to myself to make this contribution, but I don't think the way I'm doing the first item on the list is the most sane way to do it, so if someone else wants to chime in with the best way to accomplish that, feel free :)

Hi guys,

When I attempt to use Scalatra 2.3.1+ with Swagger according to what's currently in the docs, I get the following error:

[info] Compiling 3 Scala sources to /Users/dave/workspace/foss/scalatra-website-examples/2.3/swagger-example/target/scala-2.11/classes...
[error] /Users/dave/workspace/foss/scalatra-website-examples/2.3/swagger-example/src/main/scala/org/scalatra/example/swagger/FlowersController.scala:14: class FlowersController needs to be abstract, since method render in trait JsonMethods of type (value: org.json4s.JValue)(implicit formats: org.json4s.Formats)scala.text.Document is not defined
[error] class FlowersController(implicit val swagger: Swagger) extends ScalatraServlet with NativeJsonSupport with SwaggerSupport  {
[error]       ^
[error] /Users/dave/workspace/foss/scalatra-website-examples/2.3/swagger-example/src/main/scala/org/scalatra/example/swagger/FlowersSwagger.scala:7: class ResourcesApp needs to be abstract, since method render in trait JsonMethods of type (value: org.json4s.JValue)(implicit formats: org.json4s.Formats)scala.text.Document is not defined
[error] class ResourcesApp(implicit val swagger: Swagger) extends ScalatraServlet with NativeSwaggerBase
[error]       ^
[error] two errors found

@rossabaker @casualjim @seratch any idea what fixes these? I'd like to document the fix, currently all our Swagger docs will fail for anyone who generates a project and tries to follow the docs.

hugo serve is not showing me anything when I click on the scalatra-website top links (master branch)?
hugo version: v0.62.2/extended darwin/amd64
v0.36.1, but it didn't work too

Hugo v19.0 is used for building the website on TravisCI: https://github.com/scalatra/scalatra-docbuild/blob/dcb75b67d83d1a4498c837c1242aa89dbef9ccf6/.travis.yml#L17
We might have to upgrade Hugo.

The description of this repository contains URL www.scalatra.org which seems unable to be resolved.

link for scala dispatch http-client has changed to https://dispatchhttp.org/Dispatch.html starting version 0.14.X - https://github.com/dispatch/reboot/tree/0.14.x

Earlier dispatch link does not exist anymore - https://dispatch.databinder.net/Dispatch.html

which means links for dispatch mentioned in async/akka.html need to be updated - http://scalatra.org/guides/2.6/async/akka.html

If you follow the current guide, the produced Swagger JSON can't be read by the swagger-ui interface. (The HTTP 'method', and perhaps other stuff, is empty in the produced swagger spec)

Pages like http and views should be auto-generated hierarchical tables of contents.

They shouldn't be versioned under /2.2/ and the like.

@casualjim we've got the older API docs up, but haven't generated the 2.3 docs and put them on the server. I've linked them from the main nav, but currently this will 404 until the docs are there.

https://gist.github.com/2894783

A user contributed a new Maven prototype. sbt is the direction most people will want to go, but this is a nice alternative that bears mentioning;

https://github.com/fancellu/scalatra-maven-prototype

On the http://scalatra.org/guides/ page, there's a link for scaladoc for 2.7.
Currently, it's set to:
http://javadoc.io/doc/org.scalatra/scalatra-unidoc_2.12/2.7.0
but I think it should be set to scalatra-unidoc_2.13

For easier navigation.

I recently committed some broken version of the website and it deployed and the site stopped wroking entirely. It would have been useful to get a notification about that and even rollback the deployment.

I've been working with 2.7.0-RC1 making a demo project that demoes all the features of scalatra.
I'd like to start a branch for 2.7.0 in which I can update a couple of things.
What's the best way to do that?

See scalatra-casbah-example for a minimal and standalone project containing the example in this guide.
https://github.com/scalatra/scalatra-website-examples/tree/master/2.6/persistence/scalatra-casbah-example does not exist

https schema URL is written in README.
However, it seems that https://scalatra.org has an issue about domain certification.

(Sorry, screenshot was taken in Japanese language)

We are working on creating Scalatra 2.6 guides on the scalatra-2.6 branch.
This issue shows progress of that work.

Outlook

• Philosophy

Development

HTTP

• Routes
• Actions
• Reverse Routes
• Requests & Responses
• GZip
• Flash
• Authentication
• CORS

Async

• Akka
• Atmosphere

Views

• Inline HTML
• Scalate
• Twirl

Resources

• Drop this category

Formats

• File Upload
• JSON
• Command (drop)
• Forms #154

Persistence

• Introduction
• MongoDB
• Riak
• Slick
• Squeryl

Internationalization

• i18n (not exist)

Testing

• ScalaTest
• Specs2

API Design & Documentation

• Swagger #153

After Development

Monitoring

• Logging
• Metrics

Deployment

• Configuration
• Servlet container
• Standalone
• Heroku
• CloudBees (drop)
• Google App Engine

starting server fails with this error. I noticed in the _config, and in the most recent commit of Dec-16, that this webstie documentation seems old. Is this still the current scalatra.org?

ch-nb-1614:scalatra-website$ jekyll --server --auto
/Users/jbrown/.gem/ruby/2.3.1/gems/liquid-2.5.0/lib/liquid/htmltags.rb:43: warning: key "index0" is duplicated and overwritten on line 46
Configuration from /Users/jbrown/Documents/Repos/scalatra-website/_config.yml
/Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `require': cannot load such file -- sass/script/node (LoadError)
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:127:in `rescue in require'
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:40:in `require'
	from /Users/jbrown/.gem/ruby/2.3.1/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches/browser_support.rb:1:in `<top (required)>'
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/jbrown/.gem/ruby/2.3.1/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:2:in `block in <top (required)>'
	from /Users/jbrown/.gem/ruby/2.3.1/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `each'
	from /Users/jbrown/.gem/ruby/2.3.1/gems/compass-0.12.2/lib/compass/sass_extensions/monkey_patches.rb:1:in `<top (required)>'
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/jbrown/.rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /Users/jbrown/.gem/ruby/2.3.1/gems/compass-0.12.2/lib/compass/sass_extensions.rb:9:in `<top (required)>'

http://www.scalatra.org/guides/formats/commands.html

Reported on IRC:

abstract class TodosCommand[S](implicit mf: Manifest[S]) extends ModelCommand[S]
extends ModelCommand is apparently deprecated

on the atmosphere doc page: http://scalatra.org/guides/2.6/async/atmosphere.html
there a dead link:
One AtmosphereClient is instantiated per connected user. It's worth taking a look at the [ScalaDocs](http://scalatra.org/2.6/api/#org.scalatra.atmosphere.AtmosphereClient)

I stumbled on some older documentation and it doesn't refer to the right command.

It seems g8 will always generate the latest template so the command needs to be updated for older versions as well.

A few more suggestions:

• API Docs should always show all versions and not only older than the currently being viewed.
• A banner could be shown to make it obvious that the reader is accessing an older version of the documentation

Currently the doc for handling json for 2.4 states to add the following dependencies:

  "org.scalatra" %% "scalatra-json" % "2.4.0.RC1",
  "org.json4s"   %% "json4s-jackson" % "3.3.0.RC1",

Doing so led to the following issue when following the rest of the tutorial though:

[error] /home/jjst/dev/turtlewar-scalatra/src/main/scala/com/github/jjst/turtlewar/FlowersController.scala:18: in class FlowersController, multiple overloaded alternatives of method parseOpt define default arguments.
[error] The members with defaults are defined in trait JsonMethods in package jackson and trait JsonMethods in package json4s.
[error] class FlowersController extends TurtlewarscalatraStack with JacksonJsonSupport {
[error]       ^
[error] one error found

Which I got fixed by using the stable versions instead:

  "org.scalatra" %% "scalatra-json" % "2.4.0",
  "org.json4s"   %% "json4s-jackson" % "3.3.0",

Wondering whether the version numbers from the doc should be bumped?