Hi!
Yesterday we had a meeting with Jürgen Höller and it turned out that it
would make very sense to integrate our ConversationTag [1] with Spring [2].
The plan is to create a custom Spring scope which uses our
ConversationManager.
Together with Spring's powerful bean management facility this
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.
This broke the examples!
Specifically line 950 and 951 are throwing NPE when the attributes style and
styleClass are node defined.
Paul Spencer
[EMAIL PROTECTED] wrote:
Author: mmarinschek
Date: Thu Dec 7 09:49:35 2006
New Revision: 483569
URL:
On 12/19/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
Yesterday we had a meeting with Jürgen Höller and it turned out that it
would make very sense to integrate our ConversationTag [1] with Spring [2].
The plan is to create a custom Spring scope which uses our
ConversationManager.
I do not see any related commits to the TLD.
Docs?
Paul Spencer
[EMAIL PROTECTED] wrote:
Author: mmarinschek
Date: Thu Dec 7 09:49:35 2006
New Revision: 483569
URL: http://svn.apache.org/viewvc?view=revrev=483569
Log:
added inBodyStart hook for overriding attributes of body (i.e. style and
Hi Matthias!
The plan is to create a custom Spring scope which uses our
ConversationManager.
Together with Spring's powerful bean management facility this should
now you are using it ?
Well, sometimes good things need time ;-). Yes, now I've seen what it
can do for us and I can't wait to give
Paul,
thanks for catching this. doc is like tests here ...
sometimes they exist :)
-M
On 12/19/06, Paul Spencer [EMAIL PROTECTED] wrote:
I do not see any related commits to the TLD.
Docs?
Paul Spencer
[EMAIL PROTECTED] wrote:
Author: mmarinschek
Date: Thu Dec 7 09:49:35 2006
New
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
+1
On 12/19/06, Grant Smith [EMAIL PROTECTED] wrote:
+1
On 12/18/06, Bernd Bohmann [EMAIL PROTECTED] wrote:
Here is my +1
Regards
Bernd
Bernd Bohmann wrote:
Hello,
I would like to release tobago 1.0.9,
This release contains over 70 changes.
For a detail list please consult
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
myfaces-api has unnecessary commons-digester dependency
---
Key: MYFACES-1513
URL: http://issues.apache.org/jira/browse/MYFACES-1513
Project: MyFaces Core
Issue Type: Bug
I would like to propose that MyFaces switch to a Tomcat style of release[1].
Specifically a
release is cut when specific conditions are met, then the PMC sets its status,
alpha/beta/stable. The conditions could include the following:
1) All tests pass.
2) All examples work.
3) Passed a
[
http://issues.apache.org/jira/browse/TOMAHAWK-78?page=comments#action_12459655
]
Jack Rudnick commented on TOMAHAWK-78:
--
I submit that this should be moved from major to critical
Error-page problem with ExtensionsFilter
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
I just noticed dojo 0.4 has been updated to dojo 0.4.1
my plan is to get the thing into tomahawk first week of january.
I want to run upfront tests if things are severely broken.
This is a bugfix release btw. so I assume things should work as expected
sans a lot of bugs.
If anyone has any
Cagatay Civici schrieb:
Hi,
I see a scriptaculous license in sandbox, do we have anything that uses
this js lib?
The phase out of this lib is a work in progress...
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
hard-coded component id in Tobago.Updater
-
Key: TOBAGO-222
URL: http://issues.apache.org/jira/browse/TOBAGO-222
Project: MyFaces Tobago
Issue Type: Bug
Affects Versions: 1.0.8, 1.0.9
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
[ http://issues.apache.org/jira/browse/TOBAGO-222?page=all ]
Volker Weber resolved TOBAGO-222.
-
Fix Version/s: 1.0.10
Resolution: Fixed
hardcoded componentIds removed
hard-coded component id in Tobago.Updater
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
[ http://issues.apache.org/jira/browse/TOMAHAWK-824?page=all ]
Joshua Gould resolved TOMAHAWK-824.
---
Resolution: Fixed
Crash is unrelated to tag and is caused when users deactivate Safari's cache,
using a program such as Safari Enhancer.
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:
Process Validate, Update and Decode for UIPopup only if popup is submitted not
activated
Key: TOBAGO-223
URL: http://issues.apache.org/jira/browse/TOBAGO-223
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)
[
http://issues.apache.org/jira/browse/TOMAHAWK-823?page=comments#action_12459734
]
Gabriel Enriquez commented on TOMAHAWK-823:
---
I am using JSP.
Actually the 2nd issue (regarding the JS error), is becuase:
There is clashing my layout
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
[
http://issues.apache.org/jira/browse/TOMAHAWK-823?page=comments#action_12459781
]
Gabriel Enriquez commented on TOMAHAWK-823:
---
ok. finally it's working.
The problem was that the filter-mapping order affects.
The reason:
[ http://issues.apache.org/jira/browse/TOMAHAWK-823?page=all ]
Gabriel Enriquez resolved TOMAHAWK-823.
---
Fix Version/s: 1.1.3
Resolution: Fixed
Order of the filter-mapping affects when used with other frameworks.
Just remember the response
Hi
I want to suggest the promotion of following dojo components:
a) The dojo modal dialog
b) The dojo fisheye component
both components seem to be stable enough to be promoted
in case of the dialog only the documentation is missing which I am
currently writing.
(will be committed tomorrow,
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
Thomas,
I sent a few posts relative to Revision: 483569 this morning. That revision has
broken Tomahawk. I am hoping the commiter will resolve the problem quickly.
Paul Spencer
Thomas Spiegl wrote:
tomahawk 1.1.4 branch is quite out of date by now. I'd like to skip
this one, and start
On 12/18/06, Paul Spencer [EMAIL PROTECTED] wrote:
This is yet another release status request.
...
MYFACES-1411Lifecycle phase executions repetitions
** Per an 8-Dec-2006 Posting from Mike Kienenberger:
MYFACES-1411 has I.P. issues.
...
None of the above issue are marked as blockers.
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
42 matches
Mail list logo
