Muralidhar Y. wrote:
Hi if that is the case how does tapestry recognise which abstract methods
have to be implemented at runtime and which should not be. For an instance I
had 2 abstract methods which should not be implemented by tapestry and 2
abstract methods which I want tapestry to be implemented. Of course all the
4 methods are getter methods( I assume we are not saying anywhere in
tapestry that 2 methods are properties and 2 methods are not properties even
though they are getter methods like we are declaring properties in .page
file in 3.0.3)
Perhaps I misunderstand you but at runtime no methods can be abstract.
It is impossible to create an instance of a class that is abstract, if
you do not provide an implementation of a method tapestry must do so.
http://java.sun.com/docs/books/jls/third_edition/html/classes.html#8.1.1.1
Muralidhar Y
Software Engineer,
Adastrum technologies-Nikai groups,
EmiratesGroup-I.T Division,
Dubai, UAE.
Mobile : 00971-50-2256149.
http://www.adastrumtech.com
http://www.mercator.aero
(Keep Smiling. Be happy All The Time.)
-----Original Message-----
From: Tomáš Drencák [mailto:[EMAIL PROTECTED]
Sent: 17 September 2005 23:22
To: Tapestry users
Subject: Re: jwc files and annotations
Yes, you could have just abstract getter (+ setter) for each property in
Tapestry 4
2005/9/17, Muralidhar Y. <[EMAIL PROTECTED]>:
Hi in tapestry 3.0.3 if we have to declare or use abstract methods we
have to declare them as properties in .page file. Without that we
cannot directly declare or use abstract methods in java file. Is it
different in tapestry 4.
[snip]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
