I have tried a few times using base classes and inheritance.
At the end I came to the conclusion that "the tapestry way" is using
components *instead* - if a page is a "container" with some
functionality, a component is also a container... so instead of
implementing things on the page scope, implement them on a component,
and drop the component on a page...
Cheers,
Ron
ציטוט Michael Engelhart:
Thanks but I'm using Java 1.4.x and Tapestry 3.0.
On 6/29/05, Nick Stuart <[EMAIL PROTECTED]> wrote:
You can with annotations fairly easiely, and you can even do it with
interfaces if you really want (Howard shows an example of this
somewhere).
Say you have an object you wanted injected into some
pages/components, write an interface like so:
public interface ObjectUser {
@InjectObject("service:someService";)
public SomeService getSomeService();
}
then, if you wanted a page/comp to be able to access this just
implement the interface and call the method. Really is that easy. I
thought this was pretty slick at least.
-Nick
On 6/29/05, Michael Engelhart <[EMAIL PROTECTED]> wrote:
Hi -
Is there a way to create a templateless abstract base page for a Tapestry app?
I currently have a base page class that extends BasePage but I want to
make that class be able to take advantage of a page specification to
limit the writing of code make clean up of persistent properties
easier.
Is there a way to do this?
THanks
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
