Bernd,
So to get this straight, is this going to be an extra jar file that you
add to the classpath and allows for partial lifecycle processing or is
this a change to the Trinidad impl itself?
If the latter, I think we need to be very careful about changing the
unoptimized lifecycle until people have a chance to wrap their heads
around it. If the former, then I would be willing to take a look, I had
some similar ideas recently and think this can only benifit the project.
Also, is there any real way we can take a look at the code before it's
committed? Maybe move it to the sandbox first so people can take a more
detailed look at it?
Also I don't undersand your todo's.. I have been off for a month with a
new child so I suppose it's possible I'm missing something.
Scott
Bernd Bohmann wrote:
Hello,
I just started with a partial lifecycle module for trinidad.
The partial lifecyle is currently an own artifact. The artifact
overrides the default lifecyle and supports partial processDecodes,
processValidators, processUpdates and rendering if the request parameter
partialTarget is present.
If no objections I will commit the trindad-partial-lifecycle module and
create an issue with the attached trinidad-impl diff for discussion.
Regards
Bernd
Following todo's:
Is partialTarget a valid choice for the parameter name?
partialRequest from inside Tree or Table
source inside a partialTarget
decode SubForms?
SubForms
Messages
NavigationTree
broadcast Events UIViewRoot has no public method
writeState is performed by patched FormRenderer
...
