Mohammad Shamsi wrote:
but you can see some mechanism in JPA (Java Persistence API).
here you just Annotate a class with @Entity for using it as a Entity in
application.
i think number of entities in a application is not much less then number of
pages.but i have no performance problem in my apps using JPA.
You are missing a central point: the T5 IOC layer generates 'artificial'
classes at runtime, I mean raw JVM bytecode which extend from the
page/component/service classes you write. That's where injected
interfaces get their runtime values.
This process is quite cpu-intensive, so Tapestry chose to do it
on-demand, and by default just for classes beneath a specific package.
Doing it for all and any classes would mean that every class should be
inspected by the IOC enhancer on its first use.
You can contribute additional package names for the ioc to 'enhance',
but for a single application/library one package usually suffices.
If you have component/pages which are reused in more apps, or that you
want to package by themselves for better code organization, extract the
relevant pages/components source & templates and package them in a
different maven/Eclipse project which will then be used as a dependency
in your app.
Angelo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
