FYI:
https://github.com/anjlab/anjlab-tapestry-commons/wiki/Publisher-API
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
On Thu, 11 Oct 2012 11:35:12 -0300, Ken in Nashua
wrote:
Folks,
Hi!
I am trying to nail down the concept (or at least inspired concept) of
page and components and how they should be modeled with parameters and
properties.
Here is my semantic concept issue... if you can add to it t
Hi Ken,
Maybe I can help you out:
1. I would not :)
Pages and Components both have Properties. It's nothing special really. Think
Bean Properties with automatic getter/setters.
Components have Parameters, Pages have PageActivationContext. Both can be
Properties as well (because a pro
Pages and components are generally the same for me.
Pages are just top-level components.
They both have parameters: for pages they came from GET/POST/... HTTP
requests, source of component parameters are pages and other components.
Properties are just their state, the state that pages/components
Hey,
I'm not a tapestry expert but here is what I think about pages, components,
properties and parameters:
Parameters (annotated with @Parameter) can only be used in components as
parameters for the component (pages don't have parameters).
Properties (annotated with @Property) are private attrib
Folks,
I am trying to nail down the concept (or at least inspired concept) of page and
components and how they should be modeled with parameters and properties.
Here is my semantic concept issue... if you can add to it that would be helpful.
PAGES HAVE PROPERTIES, COMPONENTS HAVE PARAMETERS (
Hi Kai,
> > How would I test a page or a component when a @Parameter is not
accessible
> > because of its need to be a private variable?
As well as tests directly on the page/component object that you can do
with Tapestry's TestBase class, you can also write tests that run a page
through one o
not accessible
> because of its need to be a private variable?
>
> I want to test my pages and components with unit tests as I do with my
> service classes.
>
> Regards, Kai
>
> -
> To unsub
Em Mon, 22 Jun 2009 19:19:27 -0300, Kai Weber
escreveu:
How would I test a page or a component when a @Parameter is not
accessible because of its need to be a private variable?
If the component is written by you, add a getter and a setter, probably
with package visibility.
--
Thiago H.
How would I test a page or a component when a @Parameter is not
accessible because of its need to be a private variable?
I want to test my pages and components with unit tests as I do with my
service classes.
Regards, Kai
Em Mon, 23 Mar 2009 15:39:16 -0300, fccarmo
escreveu:
Hi Thiago!
Thank you for helping me.
You're always welcome. :)
So I'll keep them this way.
I just would like to put all my package names in Portuguese :D
You can still have all the other package names in Portuguese. :)
--
Thiago H.
ram (like "tapestry.app-package") where I
>> can change "Pages" and "Components" package names?
>
> Hi, Fernanda!
> No, you can't do that without diving deep in the Tapestry internal
> services.
> By the way, why do you want to do that?
>
&
Em Mon, 23 Mar 2009 14:09:51 -0300, fccarmo
escreveu:
Is there any kind of context-param (like "tapestry.app-package") where I
can change "Pages" and "Components" package names?
Hi, Fernanda!
No, you can't do that without diving deep in the Tapestry in
Is there any kind of context-param (like "tapestry.app-package") where I can
change "Pages" and "Components" package names?
Thanks!
--
View this message in context:
http://www.nabble.com/Tapestry-5---%22Pages%22-and-%22Components%22-package-names-tp22663890p226638
An idea:
I belive it has many pitfalls :(, but might be useful an idea,
tapestry could for example extend such enum (persist worker might trigger
it)
and add serialization code to it. Then when reloading it could force
serializing enum values, plus if the value gets serialized outside tapestry
it
Yeah, I haven't thought of that. I'll give it a shot, it just may work for us :)
On Tue, Mar 25, 2008 at 5:03 PM, Davor Hrg <[EMAIL PROTECTED]> wrote:
> This is most likely due to serialization of the enum in the session,
>
> I use a workarround that does not affect the code too much,
> and I ca
That makes totally perfect sense, and yes, I am storing an enum value
in session. So I had enum defined internally in the page, and then
@Persist on its value... I understand the limitation, and I can only
image what cool things could be accomplished if Tapestry was budnled
with embedded Jetty
This is most likely due to serialization of the enum in the session,
I use a workarround that does not affect the code too much,
and I can track references to the enum.
I persist a string variable, but always use enum.name()
to change the variable.
I use this to keep track of major blocks that a
I'm kind of surprised about that; are you storing the enum values
outside of the page instance (i.e. in the session?)
Inner classes are loaded by the disposable component class loader (the
class loader that handles retry logic and class transformation). When
a class changes, the class loader, pl
If Page or Component defines Enum internally, Tapestry throws a
ClassCastException the moment said page or component class (or even
the template) is "hot" reloaded due to any kind of change.
Can this be fixed/change to allow inner Enums?
-adam
as of 5.0.11
--
t;base", at the same level as the pages and components
packages.
For instance I have an AbstractReportPage that references Tapestry
ASOs, Injects things and Persists things. Then I have a few report
page classes that implement different flavors of very similar things.
It could be done differ
I have a few components and pages that I extend, and I put them in a
directory called "base", at the same level as the pages and components
packages.
For instance I have an AbstractReportPage that references Tapestry
ASOs, Injects things and Persists things. Then I have a few report
pa
in my tap5 project a library which
> includes tap5 pages
> and components.
> But when i try to extend a page from the library in
> my project, i get
> the following exception :
>
> java.lang.RuntimeException: Base class
> com.mylibrary.pages.FramePage
> (super class of com
xins especially), I avoid page extention.
sincerely,
chris
Steph wrote:
Hi all,
I need to import in my tap5 project a library which includes tap5 pages
and components.
But when i try to extend a page from the library in my project, i get
the following exception :
java.lang.RuntimeExcepti
Hi all,
I need to import in my tap5 project a library which includes tap5 pages
and components.
But when i try to extend a page from the library in my project, i get
the following exception :
java.lang.RuntimeException: Base class com.mylibrary.pages.FramePage
(super class of
25 matches
Mail list logo
