Yep, doing something like that. Here is the package in the code that implements
the bridge:
https://github.com/bootique/bootique-tapestry/tree/master/src/main/java/io/bootique/tapestry/di
Comments, suggestions and pull requests are welcome.
Andrus
> On Dec 19, 2016, at 8:19 PM, Thiago H. de
John,
I thought I had more than this, but when I looked , all I had was
this module for this specific conversion for Lists (it does do the
job) . You can probably add this to your own module or use this module
and include it in your module.
object TapestryScalaModule {
def
Hi!
Maybe you could try contributing an ObjectProvider to MasterObjectProvider
if you haven't done so yet (I'm sorry, I'm curious to see your Guice to
Tapestry-IoC implementation, but I haven't had the time to do it yet).
On Fri, Dec 16, 2016 at 5:12 AM, Andrus Adamchik
Yep, as Alex said, you can solve this issue by contributing a coercion from
Scala collection/list/etc to the corresponding Java type. There's an
explanation with examples here:
https://tapestry.apache.org/type-coercion.html.
On Mon, Dec 19, 2016 at 11:59 AM, Alex Kotchnev
Hi,
is there a way to set the value of a mixin parameter in case of an
implementation mixin?
If the mixin is used as an instance mixin, I can bound its parameter value in
the template or using the attribute "parameters" of the @Component annotation.
However, let's supppose that a component
John - I've been running Tapestry and Scala for a few years now (e.g.
www.zadachite.com on AppEngine, and a few internal apps), and it's
been working pretty well. About the specific issue of the collection
conversions - it bugged me for a little while, and I'm pretty sure I
have a project