Howard Lewis Ship wrote:
This is the essense of backwards compatibility.
Thanks for the answers Howard.
The reason I asked if I still need to extend the BasePage was because I
figured you may have implemented an alternative to the BasePage without
those warnings. IMO a framework should only give deprecation-warnings
during compile if the framework-user does something in a deprecated way.
It's just weird to get compiler-warnings if you do things the proper
way. It causes confusion.
regards,
Onno
On 8/14/05, Onno Scheffers <[EMAIL PROTECTED]> wrote:
I'm trying to get to grips with the Tapestry 4 way of doing things (beta
4). I still have a couple of questions:
- For every page that extends the BasePage I get 4 deprecation warnings:
Warning: Warning: line (14)[deprecation]
removePageRenderListener(org.apache.tapestry.event.PageRenderListener)
in org.apache.tapestry.IPage has been deprecated
Warning: Warning: line (14)[deprecation]
addPageRenderListener(org.apache.tapestry.event.PageRenderListener) in
org.apache.tapestry.IPage has been deprecated
Warning: Warning: line (14)[deprecation] getGlobal() in
org.apache.tapestry.IPage has been deprecated
Warning: Warning: line (14)[deprecation] getVisit() in
org.apache.tapestry.IPage has been deprecated
This quickly grows into a huge number of warnings. I do still need to
extend the BasePage, right? (The 'QuickStart: DirectLink' example still
does).
- The user guide on the website is not yet complete regarding
validation; I use the T3 way of using validFields, which gives me
runtime deprecation-warnings in my log.
What should I use instead of ValidFields?
TextField, and make use of the new translator and validators
parameters. Yes, its not well documented yet!
- When I implement my own ValidationDelegate the writeSuffix method
always gets null as a validator parameter. Is that supposed to happen?
Or does that have to do with my previous question?
The writeSuffix method is getting invoked for all sorts of stuff now,
not just ValidFields. For TextField, TextArea, etc., the validator
parameter will be null.
Validation itself is working, so I know the validators are ok. I've
tried it with the 'validator:'-prefix, setting up <bean>s for validators
and even provided validators through my own Page class just
to be sure. But no matter what I try I end up with a null-validator in
the writeSuffix method of my custom ValidationDelegate.
Any helps would be appreciated.
Regards,
Onno
---------------------------------------------------------------------
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]
