spray/spray

A suite of scala libraries for building and consuming RESTful web services on top of Akka: lightweight, asynchronous, non-blocking, actor-based, testable

spoofer

@TopSpoofer

object RetStatus extends Enumeration {
  type RetStatus = Value
  val Success = Value(1)
  val Fail = Value(0)
  val Exception = Value(-1)
}

case class FileServerRet(status: RetStatus, msg: String, fileAbsName: String) {

}

Shikha Madaan

@smadaan2

I want to modify spray generated response header i.e Date but not able to modify and its creating new Date response header so I am getting duplicate Date response header.

 responseHeader(`Date`, new DateTime()) {
  complete()
}

vito-c

@vito-c

should we be using akka http for making http requests?

vito-c

@vito-c

This my error:

could not find implicit value for parameter m: akka.http.scaladsl.marshalling.Marshaller[v2d2.actions.generic.protocol.Foo,akka.http.scaladsl.model.RequestEntity]

This is my protocol:

case class Foo(thing1:String, thing2:Seq[String], thing3:String)
trait FooJsonProtocol extends DefaultJsonProtocol {
  implicit val sendFooFormat = jsonFormat3(Foo.apply)
}
object FooJsonProtocol extends FooJsonProtocol

This my http client side request

class Blah(muc: MultiUserChat) extends Actor with ActorLogging with FooJsonProtocol {

  import system.dispatcher
  implicit val system = ActorSystem()
  implicit val materializer = ActorMaterializer()
  implicit val timeout = Timeout(25.seconds)

  def receive: Receive = {
    case bar:Bar =>
        val foo = Foo(bar.a, bar.b, bar.c)
        val content = for {
          request <- Marshal(foo).to[RequestEntity]
          response <- Http().singleRequest(
            HttpRequest(
              method = HttpMethods.POST, 
              "https://blah.com"),
              entity = request))
          entity <- Unmarshal(response.entity).to[String]
        } yield entity
        content onComplete {
          case Success(s) => self ! s
          case Failure(t) =>
            context.parent ! "An error has occured: " + t.getMessage
        }
}

Conner Bryan

@cab

is this the right place to ask questions about spray-json?

This message was deleted

Conner Bryan

@cab

is it possible to use a wildcard / existential type for spray-json? e.g.

sealed trait PetKind

sealed trait CatKind extends PetKind
sealed trait DogKind extends PetKind

sealed trait Pet[Kind <: PetKind]

final case class Cat(favoriteFish: String) extends Pet[CatKind]
final case class Dog(favoriteBone: String) extends Pet[DogKind]

final case class Pets(animals: Seq[Pet[_])

This message was deleted

Conner Bryan

@cab

currently working around it by doing

sealed trait PetKind

sealed trait CatKind
sealed trait DogKind

sealed trait Pet {
  type Kind <: PetKind
}

final case class Cat(favoriteFish: String) extends Pet {
  type Kind = CatKind
}

final case class Dog(favoriteBone: String) extends Pet {
  type Kind = DogKind 
}

final case class Pets(animals: Seq[Pet])

Conor

@somethingconcon

Does anyone know how to supply a formater for request parse exceptions? I’m testing a request URI that’s too large resulting in the response body (asString) "URI length exceeds the configured limit of"

Konrad `ktoso` Malawski

@ktoso

Spray is end of life since quite a long time, you won’t get too much active feedback; I’d recommend upgrading to Akka HTTP (very similar API, should be simple)

the concept you want to read up about is rejections in general and rejection handlers

my above comment still stands though ;)

Conor

@somethingconcon

@ktoso :D thanks for the info! Planning on upgrading within the month as part of our next milestone. I have my rejection handler setup correctly (I think) but in the code I can’t find how to deal with it. Any suggestions would be very helpful.

codedef rejection(implicit logging: LoggingContext) =
RejectionHandler {
case Nil => ctx =>
respondToBadRequest(ctx, "The requested resource could not be found.")

  case MalformedQueryParamRejection(param, message, error) :: _ => ctx =>
    respondToBadRequest(ctx, s"Malformed params: $param")

  case MissingQueryParamRejection(param) :: _ => ctx =>
    respondToBadRequest(ctx, s"Missing params: $param")

  case MissingFormFieldRejection(field) :: _ => ctx =>
    respondToBadRequest(ctx, s"Missing field $field")

  case MalformedFormFieldRejection(field, error, cause) :: _ => ctx =>
    respondToBadRequest(ctx, s"Malformed field $field. Error: $error")

  case MalformedRequestContentRejection(message, cause) :: _ => ctx =>
    respondToBadRequest(ctx, message)

  case RequestEntityExpectedRejection :: _ => ctx => {
    val message =
      s"""Request entity expected but not supplied.
          | Target: ${ctx.request.unmatchedPath}
          | Entity: ${ctx.request.entity.asString}
      """

    respondToBadRequest(ctx, message)
  }

  case SchemeRejection(message) :: _  => ctx =>
    respondToBadRequest(ctx, s"Schema rejection. Error: $message")

  case MethodRejection(message) :: _ => ctx =>
    respondToRejection(ctx, s"Method not allowed on this resource. Error $message", MethodNotAllowed)

  case UnsupportedRequestContentTypeRejection(error) :: _ => ctx =>
    respondToBadRequest(ctx, error)

  case ValidationRejection(message, cause) :: _ => ctx =>
    respondToBadRequest(ctx, s"Validation rejection: $message")
}

oh, poo

Konrad `ktoso` Malawski

@ktoso

sorry too much code for me go to over now, getting late here

Conor

@somethingconcon

now worries, cheers :D

s/now/no

Konrad `ktoso` Malawski

@ktoso

basically handle the rejection, and return exactly what you want

we have docs for this in akka http

google things around “akka http rejection handler json"

Conor

@somethingconcon

@ktoso oh one more question. Is akka-http planning on adopting play-json in the near future or is spray-json here to stay?

Konrad `ktoso` Malawski

@ktoso

there’s no need to “adopt”; it just works ™ with play-json

https://github.com/hseeberger/akka-http-json

Conor

@somethingconcon

noice!

:D :D :D

Konrad `ktoso` Malawski

@ktoso

noice indeed ;)

lemonxah

@lemonxah

hi guys

Error:(52, 15) Cannot find JsonWriter or JsonFormat type class for List[com.konga.order.models.Order]

it does this for all list types

and i do have

import com.konga.order.models.OrderJsonSupport._
import DefaultJsonProtocol._

Arnout Engelen

@raboof

@lemonxah have you verified it works for com.konga.order.models.Order when it's not in a List?

lemonxah

@lemonxah

nvm found the issue .. the OrderJsonSupport extended DefaultJsonProtocol as well removed that and it works

Arnout Engelen

@raboof

ah yes if you have multiple matching implicits the compiler sometimes makes it look like none matched, very confusing indeed

lemonxah

@lemonxah

normally i would have ambigious implicit

but now .. nothing matched .. that was very confusing

Abhiraj Padhye

@A4Abhiraj

Hey everyone! This issue is still open. Can anyone help ?
spray/spray-json#159

Andrey Ivanov

@a-nigredo

Hi all, I am busy with migration from spray to akka-http and don't understand what happens with such a code:

def route = path(Segment) {
 actorReffactory.actorOf("")
}

What will be in a response then?

How spray process actorRef as a response?

Konrad `ktoso` Malawski

@ktoso

this won’t compile

please ask on gitter.im/akka/akka btw :)

it won’t compile, exactly because the question you ask can’t be answered statically — akka http enforces these things

Andrey Ivanov

@a-nigredo

@ktoso I know that it is not compiled in akka-http but in spray. My question is what convertion spray uses to handle such case?

Jameel Al-Aziz

@jalaziz

Curious if this is a known thing before I open up a ticket. RouteTest in the testkit appears to eagerly create and start the actor system. While this normally wouldn't be an issue, we use ScalaTest's tagging to include/exclude tests. The eager loading slows things down considerably as the actor system will be initialized even though no tests are actually run.

Konrad `ktoso` Malawski

@ktoso

Spray has been end of life since a few years, please migrate do akka-http (migration is usually rather simple), and ask there then

Jameel Al-Aziz

@jalaziz

ahh, good point, forgot about that, we actually do use akka-http for newer things

thanks!

Where communities thrive

People

Repo info

Activity