From: Martin Marinschek [EMAIL PROTECTED]
Hi Craig,
Facelets supports a
setPropertyActionListener
as well - if Clay does, I can't say.
The current Clay JSF 1.2 support is limited to the things that are not 1.2
specific. As you know, the new SetPropertyActionListener uses the
On 12/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Just out of curiousity, where did they add it? I don't see any
reference
to updateActionListener in 1.2.
it is named setPropertyActionListener in the spec and in trinidad
setActinListener
Thanks ... I had not recalled that from
On 12/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
By the way, is this similar to (or identical to) your idea for a
preupdate()
method in Shale's ViewController (SHALE-338)? If so, I still like the
idea
... just need to see the follow through :-).
:) I am on it, but got blocked by
Hi!
Our plan was to implicit start a conversation as soon as a conversation
been will be created through spring.
Well, to know which conversationContext we are currently working in
(this context is required for multiple window awareness) we have to
add a request parameter to every rendered url.
2) standardize the backing-bean concept (aka ViewController)
Technically spoken: We have a PhaseListener which try to lookup a bean
using a name derived from the viewId (like shale's ViewController).
then what will happen to users who use Seam or future WebBean with MyFaces?
as you may know
then what will happen to users who use Seam or future WebBean with MyFaces?
as you may know seam also has its own phase listener and bean managment
facility.
webbeans is not ready for now.
regarding seam, I think that this feature is not mandatory, sorta
optional extension.
perhaps jsf itself
how's JSF 1.2 coming along btw?
Hi!
as you may know seam also has its own phase listener and bean
managment facility.
Having a phase listener does not necessarily mean we break the JSF
lifecycle or something else.
can seam users also continue using myfaces?
definitely: Yes!
MyFaces JSF Impl
Hi Jacob!
how's JSF 1.2 coming along btw?
What do you mean?
As far as I can see JSF 1.2. do not introduce any new (flash or
conversation) scope.
So (IMHO) our solution works with JSF 1.2 too.
If you mean how far our (MyFaces) JSF 1.2 implementation is ... well ...
then I have to say there
Oh, thanks!
Hi Jacob!
how's JSF 1.2 coming along btw?
What do you mean?
As far as I can see JSF 1.2. do not introduce any new (flash or
conversation) scope.
So (IMHO) our solution works with JSF 1.2 too.
If you mean how far our (MyFaces) JSF 1.2 implementation is ... well ...
then I have
Hi
Since jacob is also here, it is a long time that some components like tree
don't work well with facelets, is resolving the issues on the plan?
On 12/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Oh, thanks!
Hi Jacob!
how's JSF 1.2 coming along btw?
What do you mean?
As far as I can
at least here is a famous blog, which shows the usage of tree2 and facelets
(with ajax4jsf)
On 12/19/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote:
Hi
Since jacob is also here, it is a long time that some components like tree
don't work well with facelets, is resolving the issues on the plan?
http://www.jroller.com/page/plainoldweblog?entry=use_tomahawk_tree2_and_ajax4jsf
On 12/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
at least here is a famous blog, which shows the usage of tree2 and facelets
(with ajax4jsf)
On 12/19/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote:
Hi
Thanx Matthias,
very useful link,
but I meant the old tree component not tree2, which people who need a tree
table should still use it (according to myfaces web site)
On 12/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
On 12/19/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Our plan was to implicit start a conversation as soon as a conversation
been will be created through spring.
Well, to know which conversationContext we are currently working in
(this context is required for multiple window awareness)
Hi Craig!
One of the architectural approaches that MyFaces developers seem to do
pretty often, even when they don't have to, is think of everything as
needing a component.
Hehe, yes indeed. But I'll try to move away from such approaches, the
Spring Conversation integration should no longer need
I might be biased too from the Seam side, but writing this, even in small steps
may grow into a monster :-) I can see committing to only an implicit flash
scope (90% of the cases-- and very useful), but pursuing full conversation
management and transactions without an actual separate project
On 12/19/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Craig!
One of the architectural approaches that MyFaces developers seem to do
pretty often, even when they don't have to, is think of everything as
needing a component.
Hehe, yes indeed. But I'll try to move away from such approaches,
Hi Jacob!
I might be biased too from the Seam side, but writing this, even in small
steps may grow into a monster :-)
Yep, and thats why we have no plans to do so ... and there are numerous
implementations out there dealing with it, I don't plan to gather new
enemies ;-)
I can see
Craig McClanahan schrieb:
One of the architectural approaches that MyFaces developers seem to do
pretty often, even when they don't have to, is think of everything as
needing a component. To me, this involves the person building the view
in decisions that really belong to the person working
Well,
sometimes somethings work well, even the design is not that best.
Regard the separation, I think that is true for the
updateActionListener as well.
I love that guy, Trinidad has a similar and now the spec folks saw
what's useful und added it
Just my $0.02
-M
On 12/20/06, Werner Punz
On 12/19/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Well,
sometimes somethings work well, even the design is not that best.
Regard the separation, I think that is true for the
updateActionListener as well.
I love that guy, Trinidad has a similar and now the spec folks saw
what's useful
Just out of curiousity, where did they add it? I don't see any reference
to updateActionListener in 1.2.
it is named setPropertyActionListener in the spec and in trinidad
setActinListener
-M
By the way, is this similar to (or identical to) your idea for a preupdate()
method in Shale's
By the way, is this similar to (or identical to) your idea for a preupdate()
method in Shale's ViewController (SHALE-338)? If so, I still like the idea
... just need to see the follow through :-).
:) I am on it, but got blocked by other *tasks*
Stay tuned
-M
Craig
Just my $0.02
-M
On
23 matches
Mail list logo
