I am having trouble with the Play! framework’s mapping function. I have suspicion that it may not be able to support the amount of parameters I am passing in as it worked when I limited to just one mapping, but did not find much in the documentation: http://www.playframework.org/documentation/api/2.0.2/scala/index.html#play.api.data.Form
Here is the form:
val paymentForm: Form[PaymentValues] = Form(
// Define a mapping that will handle User values
mapping(
"message" -> text,
"x_card_num" -> text,
"x_exp_date" -> text,
"exp_year" -> text,
"exp_month" -> text,
"x_card_code" -> text,
"x_first_name" -> text,
"x_last_name" -> text,
"x_address" -> text,
"x_city" -> text,
"x_state" -> text,
"x_zip" -> text,
"save_account" -> text,
"product_array" -> text,
"x_amount" -> text,
"products_json" -> text,
"auth_net_customer_profile_id" -> text,
"auth_net_payment_profile_id" -> text,
"customer_id" -> text,
"saved_payments_object" -> text )(PaymentValues.apply)(PaymentValues.unapply))
Any suggestions on breaking up the mapping in some way? Thanks in advance.
This is the error:
! Internal server error, for request [GET /] ->
sbt.PlayExceptions$CompilationException: Compilation error [Overloaded method value [mapping] cannot be applied to ((java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]), (java.lang.String, play.api.data.Mapping[String]))]
at sbt.PlayReloader$$anon$2$$anonfun$reload$3$$anonfun$2$$anonfun$apply$11$$anonfun$apply$12.apply(PlayReloader.scala:224) ~[na:na]
at sbt.PlayReloader$$anon$2$$anonfun$reload$3$$anonfun$2$$anonfun$apply$11$$anonfun$apply$12.apply(PlayReloader.scala:224) ~[na:na]
at scala.Option.map(Option.scala:133) ~[scala-library.jar:0.11.2]
at sbt.PlayReloader$$anon$2$$anonfun$reload$3$$anonfun$2$$anonfun$apply$11.apply(PlayReloader.scala:224) ~[na:na]
at sbt.PlayReloader$$anon$2$$anonfun$reload$3$$anonfun$2$$anonfun$apply$11.apply(PlayReloader.scala:221) ~[na:na]
at scala.Option.map(Option.scala:133) ~[scala-library.jar:0.11.2]
Here is PaymentValues:
package models
// definition of PaymentValues
case class PaymentValues(
message: String,
x_card_num: String,
x_exp_date: String,
exp_year: String,
exp_month: String,
x_card_code: String,
x_first_name: String,
x_last_name: String,
x_address: String,
x_city: String,
x_state: String,
x_zip: String,
save_account: String,
product_array: String,
x_amount: String,
products_json: String,
auth_net_customer_profile_id: String,
auth_net_payment_profile_id: String,
customer_id: String,
saved_payments_object: String)
Looking deeper and deeper in the data API, the limitation comes both from Scala and Play.
Actually, internally, Play will use a case class
ObjectMappingto represent a mapping and to define the data binding.This
ObjectMappingcase class will take the target’s apply and unapply methods, the domain object (for unapply) and all the 20 parameters as constructor arguments. Count: 23 arguments.Scala has a limit at 22 (see here) for such Product Abstract Types (tuples, functions, case classes, …).
That’s why a mapping for 20 parameters is not provided by Play… (actually it stops at 18 as said in the great comments to this post)
EDIT
If you don’t believe me… try this ^^