On Mon, Mar 9, 2009 at 7:04 AM, Jonathan O'Connor wrote:
> Although you can't use generics directly, I presume you can define a
> subclass that inherits from a given generic superclass.
The approach you're describing works very well. Tapestry CRUD
(http://www.arsmachina.com.br/project/tapestrycru
Although you can't use generics directly, I presume you can define a
subclass that inherits from a given generic superclass.
For instance,
class CrudPage {
// Stuff with T
}
class CustomerCrud extends CrudPage {
}
Would this work? I suppose if you used a generic service, then you would
hav
Which is why I'm anxious to release Tapestry 5.1 and demonstrate the
seriousness concerning backwards compatibility.
On Sun, Mar 8, 2009 at 7:58 PM, Thiago H. de Paula Figueiredo
wrote:
> Em Sun, 08 Mar 2009 23:46:41 -0300, Luther Baker
> escreveu:
>
>> "Further, the design of Tapestry 5 was cre
Em Sun, 08 Mar 2009 23:46:41 -0300, Luther Baker
escreveu:
"Further, the design of Tapestry 5 was created specifically to make it
possible to continue adding features without breaking backwards
compatibility going forward. There will not need to be a Tapestry 6."
There was a very annoying t
Ok, I'll bite :)
http://www.jroller.com/WarnerOnstine/entry/tapestry_future_adoption_redux
One shining point came from Howard himself --
"Further, the design of Tapestry 5 was created specifically to make it
possible to continue adding features without breaking backwards
compatibility going for
Em Sun, 08 Mar 2009 23:35:44 -0300, Luther Baker
escreveu:
Yes.
Maybe Tapestry 6 :)
"Tapestry 6" has a history of controversy and trolling. As it's already
23:38 PM here in Belo Horizonte, MG, Brazil and I'm lazy now, read this
list and search the web for "tapestry 6" to know what I'm
Yes.
Maybe Tapestry 6 :)
Given that the language keeps changing/moving forward, this seems like an
odd thing to simply leave the user with ... I would guess that Templates,
Components, Pages ... and the way we setup Services in AppModule would
eventually want to consider techniques that wish to l
Em Sun, 08 Mar 2009 15:46:19 -0300, Luther Baker
escreveu:
Is there anyway to use generics as pages, components or edit blocks?
No, because Tapestry uses the class name as URL.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com
Is there anyway to use generics as pages, components or edit blocks?
path/Edit
vs
path/Edit
I'd imagine not - you'd have had to encoded the Generic type in the class
and page names somehow and I've not seen anyone do that yet.
-Luther
