Hi, It sounds like you basically want to implement your own little web framework on top of akka-http?
In that case it is probably best to skip the high level server API and build on top of the low level server side API instead, you can find an overview here: http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0.1/java/http/server-side/low-level-server-side-api.html#request-response-cycle -- Johan Andrén Typesafe - Reactive apps on the JVM Twitter: @apnylle On Thursday, January 7, 2016 at 1:07:30 PM UTC+1, ash.ta wrote: > > hi hakkers, > > i'm working *JAVA* akka-http based app. > i was planning to create a generic handler that handles all common stuff > and only exposes a method for custom logic implementation. > my problem is that handlers that will derive from it in the future will > use different types of inputs. some will expect to receive json in a post > body, > others will look for specific params arriving in get and so on. > the only examples i find make use of RequestVals, which in its turn is > initialized in a "server class", out of handlers' scope. > this means that each time a new handler needs to be implemented i'll have > to edit that "server class". > > my question is if there is any way to access and manage httprequest > related data within handlers scope in a generic manner? > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
