+1 for #1
Yes, is is obvious that close() closes immediately.
Ciao,
Mario
Von: Gerhard [mailto:gerhard.petra...@gmail.com]
Gesendet: Samstag, 18. September 2010 17:52
An: MyFaces Development
Betreff: Re: [jira] Created: (EXTCDI-57) revisit Conversation#end
+1 for #1
regards,
[
https://issues.apache.org/jira/browse/ORCHESTRA-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845215#action_12845215
]
Mario Ivankovits commented on ORCHESTRA-42:
---
Hmmm ... The shared_* packages
[
https://issues.apache.org/jira/browse/MYFACES-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845216#action_12845216
]
Mario Ivankovits commented on MYFACES-2604:
---
Could someone of the MyFaces
Hi!
- Extend Orchestra use Conversations based on the JSF 2.0 custom scope
API, Extend Orchestra to work with Spring Conversations, to do
File-New Window Handling
Any idea how this should work?
What magic is Spring Conversations using here?
Ciao,
Mario
Handling
I was thinking based on a suggestion done on JSFDays to take advantage on
trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), and
refactor that code to allow orchestra conversation scope work without spring
(using the new JSF 2.0 custom scope).
[Mario
+1
Von: gerhard.petra...@gmail.com [mailto:gerhard.petra...@gmail.com] Im
Auftrag von Gerhard Petracek
Gesendet: Dienstag, 16. Februar 2010 12:01
An: MyFaces Development
Betreff: [VOTE] codi as a new myfaces extensions sub-project
hi @ all,
we have collected a lot of possible
Great to see a new release!!
:-)
Thanks Leonardo!
Von: Leonardo Uribe [mailto:lu4...@gmail.com]
Gesendet: Samstag, 19. Dezember 2009 01:09
An: annou...@apache.org; annou...@myfaces.apache.org
Cc: MyFaces Development; MyFaces Discussion
Betreff: [ANNOUNCE] release of myfaces orchestra
As far as I know, a release should be fine!
Ciao,
Mario
Von: Leonardo Uribe [mailto:lu4...@gmail.com]
Gesendet: Dienstag, 01. Dezember 2009 23:46
An: MyFaces Development
Betreff: [orchestra] could we do a release of this artifacts?
Hi
I would like to add a module for orchestra
Hi!
Even if you advertised at the beginning, I too think that JDK 1.4 compatibility
is no longer a must.
Merging core15 might then be the logical step.
Are you going to volunteer? ;-)
Ciao,
Mario
Von: Leonardo Uribe [mailto:lu4...@gmail.com]
Gesendet: Mittwoch, 14. Oktober 2009 01:21
An:
[
https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12763854#action_12763854
]
Mario Ivankovits commented on ORCHESTRA-40:
---
I think we all agree, having
.
Regards,
~ Simon
On Thu, Oct 1, 2009 at 1:25 AM, Mario Ivankovits
ma...@ops.co.atmailto:ma...@ops.co.at wrote:
+1 for jul
reduces dependencies - and sun also use it, no?
Von: Leonardo Uribe [mailto:lu4...@gmail.commailto:lu4...@gmail.com]
Gesendet: Donnerstag, 01. Oktober 2009 04:06
+1 for jul
reduces dependencies - and sun also use it, no?
Von: Leonardo Uribe [mailto:lu4...@gmail.com]
Gesendet: Donnerstag, 01. Oktober 2009 04:06
An: MyFaces Development
Betreff: [VOTE] use of jul or commons logging on myfaces core 2.0
Hi
Right now, facelets code added to myfaces core
[
https://issues.apache.org/jira/browse/ORCHESTRA-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12735612#action_12735612
]
Mario Ivankovits commented on ORCHESTRA-43:
---
Does it makes sense to have
Hmmm … it might be worth looking at using Orchestra without Spring. Guice is
not an option for your clients either, is it?
If you do not use Spring, you also do not use its persistence capabilities ;-)
So then, using a CGLIB based (or whatever enhancer lib) approach which simply
enhances the
Start voting? ;-)
From: Gerhard Petracek [mailto:gerhard.petra...@gmail.com]
Sent: Saturday, June 06, 2009 11:45 AM
To: MyFaces Development
Subject: Re: AW: slf4j and myfaces
yes the -1 vote would be a veto in view of slf4j
- no agreement - we would vote about jul.
or as mario suggested -
+1
Von: Gerhard Petracek [mailto:gerhard.petra...@gmail.com]
Gesendet: Dienstag, 09. Juni 2009 20:33
An: MyFaces Development
Betreff: [VOTE] jul instead of commons-logging
hi,
short description:
this first vote is about the switch from commons-logging (cl) to
java.util.logging (jul).
it's a
]
Gesendet: Freitag, 05. Juni 2009 20:50
An: MyFaces Development
Betreff: Re: slf4j and myfaces
On Fri, Jun 5, 2009 at 19:49, Mario Ivankovits ma...@ops.co.at wrote:
Hi!
Could one please eloberate a little bit more in detail what the pros are of
slf4j?
Pros:
No class loader ambiguousness (as you
in our libraries - just different namings.
Ciao,
Mario
[1] http://wiki.apache.org/myfaces/Trinidad_and_Common_Logging
-Ursprüngliche Nachricht-
Von: Mario Ivankovits [mailto:ma...@ops.co.at]
Gesendet: Samstag, 06. Juni 2009 08:08
An: 'MyFaces Development'
Betreff: AW: slf4j and myfaces
Hi!
There are two pros of slf4j I did not mention yet:
1. parameterized messages, which make it possible to omit those ugly
if (logger.isDebugEnabled()) {... conditions, without performance
issue: see http://www.slf4j.org/faq.html#logging_performance
that would be possible as well. i just started with slf4j since we already
discussed it and udo wrote about the switch to slf4j in the next release...
we could also vote first about slf4j and everybody who prefers jul should
vote -1
Just wait until Monday if possible, then enough
Hi!
The only downside I see is that we might break compatibility for java
1.4 since JUL gut some overhaul between 1.4 and 5, but on the other hand
is it really important anymore?
Which projects still have to be on 1.4
In 1.4.2 the log methods in question were already there. So - as a
Hi!
Not sure if this adds any value to this discussion, but
The only question is how facelets handles this case, but I assume
faclets simply skips comments and passes it through with out.write!
I'm talking about !-- on the page level, not on the component level.
Facelets will treat !--
Hi!
Could one please eloberate a little bit more in detail what the pros are of
slf4j?
Notice, I switched to it in our company project - but always using the
commons-logging api and just used the slf4j-over-cl wrapper. This is something
wich is possible for each and ever user of myfaces
, Development and
Courses in English and German
Professional Support for Apache MyFaces
2009/6/5 Mario Ivankovits ma...@ops.co.atmailto:ma...@ops.co.at
Hi!
Could one please eloberate a little bit more in detail what the pros are of
slf4j?
Notice, I switched to it in our company project
+1 Checked it now and looks good!
---
Mario
visit my blog at http://copy-con.blogspot.com/
-Original Message-
From: Mario Ivankovits [mailto:ma...@ops.co.at]
Sent: Tuesday, March 03, 2009 8:12 AM
To: 'MyFaces Development'
Subject: RE: [VOTE] Orchestra 1.3.1 release candidate
+0
+0 (I trust you made a high quality package again :-) )
-Original Message-
From: Simon Kitching [mailto:skitch...@apache.org]
Sent: Monday, March 02, 2009 9:58 PM
To: MyFaces Development
Subject: [VOTE] Orchestra 1.3.1 release candidate
Hi All,
I think it's time to release an
Hi!
-Original Message-
From: Jan-Kees van Andel [mailto:jankeesvanan...@gmail.com]
Mario, I've been looking at the Shale code that handles the annotation
scanning, but I saw it uses Reflection and standard Java ClassLoaders
for scanning the classpath for JSF artifacts. What's your
Hi!
not sure on the PERF, but if it is really (proven) the case, I am with
you.
Well... startup time isn't really a big problem, right? :-)
Is that ironic?
In projects with 3000 classes and 60 jar files you are up to 30 seconds, or
even more, scanning time.
Under load, with shale, I saw
Hi!
But there are some issues with this:
First, what paths to scan? AFAIK the spec doesn't state the classpaths
to scan. I suppose only /WEB-INF/lib and /WEB-INF/classes need to be
checked, but I can't find it in the spec.
What ever the spec says, we definitely should provide a configuration
-Original Message-
From: Jan-Kees van Andel [mailto:jankeesvanan...@gmail.com]
Sent: Wednesday, January 07, 2009 8:15 AM
To: dev@myfaces.apache.org
Subject: Re: Scanning for annotated classes in MyFaces 2
It might be smart to put this Shale code in a separate project. For
example
Hi!
Just wanted to post a link to mesir [1]. Mainly a pom.xml and a few examples,
but I like the idea of bundling all this together and state this a full stack.
From the pom.xml I can say that we use many of these libraries already in our
application and they turned out to be very stable. I
+0
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gerhard Petracek
Sent: Thursday, December 04, 2008 12:01 PM
To: MyFaces Development
Subject: [VOTE] Release of Extensions Validator 1.1.1
Hi,
I was running the needed tasks to get the 1.1.1 release of Apache MyFaces
Extensions
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Are there also MyFaces diapers available, that would
be the perfect present for my newborn child this year ;-)
cool. congrats!
is is a wernER or wernSIE ?
ROFL
Werner, whats up? Why haven't you
Welcome Mr. President!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Manfred Geiler
Sent: Thursday, November 20, 2008 10:08 AM
To: MyFaces Development
Subject: New MyFaces PMC chair
Please welcome our new MyFaces PMC chair Matthias Wessendorf!
]
Congratulations!
On Thu, Nov 20, 2008 at 11:42 AM, Mario Ivankovits [EMAIL
PROTECTED]mailto:[EMAIL PROTECTED] wrote:
Welcome Mr. President!
-Original Message-
From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL
PROTECTED]mailto:[EMAIL PROTECTED]] On
Behalf Of Manfred Geiler
At least, I can't access it either.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Matthias Wessendorf
Sent: Thursday, November 20, 2008 1:33 PM
To: MyFaces Development
Subject: Re: [Continuum] up? or down?
http://myfaces.zones.apache.org:8080/
Probably something went wrong during the copy process and you have old .svn
directories in the structure.
Check the content of the files in the .svn directory in
trinidad-1.0.10/trinidad-api and check if the url points to the correct svn
path and not to the trunk or any other tag path.
Ciao,
+1
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2008 12:15 PM
To: MyFaces Development
Subject: [orchestra flow] support JSF1.2 only?
Hi,
Currently orchestra-flow 0.0.1 supports JSF1.1. However in order to
allow pages that
Hi!
The problem is, that it is hard to ensure having a stopConversation
for each startConversation, and what about reloading the page where
possibly the startConversation gets called twice.
Well, if I'm not completely mistaken, you also have to invalidate all
Orchestra conversations
+1
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Friday, October 24, 2008 11:27 AM
To: MyFaces Development
Cc: MyFaces Discussion
Subject: [orchestra] [VOTE] Orchestra Core 1.3 Release
Hi All,
A release-candidate has been prepared for Orchestra Core
Hi!
Example 1)
I've developed some views for a search dialog that I wanted to use in
at
least two different conversations. Everything worked fine for the first
conversation. The following code listing should give you an idea of the
problem.
Simon developed Orchestra Flow which might solve
Hi!
Example 1)
I've developed some views for a search dialog that I wanted to use in at
least two different conversations. Everything worked fine for the first
conversation. The following code listing should give you an idea of the
problem.
However (as noted in my other email) flow
Hi!
Well, basically I'd refactor the ConversationContext so that it's
actually the main conversation of Orchestra. The conversation itself is
almost independent of Spring (of course, there's still an according
implementation of the Scope interface, but it will be implemented way
easier).
Hi!
Great!
I think it is a good time to make another Orchestra Core release.
There is nothing radical in this new version,
Yep, the radical stuff is kept for the next version ;-)
Ciao,
Mario
Hi!
+1 to number one.
Ciao,
Mario
Hi!
A while ago you added class SpringSingleConversationScope to orchestra
with the comment Mostly useful for dialog/flow frameworks.
The idea was that a dialog can have only one conversation. I can't remember
why we/I thought that we require that. Now that it works without this
limitation I
Hi!
This used to work in MyFaces 1.1, but in 1.2 it looks like the fact that
my type is an enum takes precedence over the fact that it implements
EnumCoded interface, so I end up with the built-in EnumConverter instead
of my GenericEnumTypeConverter.
Of course this issue was not relevant in
Hi!
If people are happy with adding a note to the tomahawk sandbox page as
described above then I'll do it.
I'd prefer this mark buoy.
Ciao,
Mario
+0
No chance to look at it for me now, but I trust that you did a good job
again :-)
Ciao,
Mario
On Tue, 2008-07-15 at 23:03 +0200, simon wrote:
Hi All,
The release candidate for MyFaces Orchestra Core 1.2 can be found in the
following places:
Download bundles:
Hi!
Note that I will be on holiday until Monday 15 July, so there is no hurry :-)
Monday OR 15 July, both together will not be possible ;-) Well, and even
15 July might be a VERY short vacation. *hehe*
Thanks or the work, I'll look at the artifacts in the next few days,
before my vacation
at the new version
before they pick up any of these changes.
+1 from me of course
Regards,
Simon
--
mit freundlichen Grüßen
Mario Ivankovits
Software Engineering
OPS EDV VertriebsgesmbH
A-1120 Wien, Michael-Bernhard-Gasse 10
Firmenbuch Nr.: FN51233v, Handelsgericht Wien
Tel.: +43-1
Hi!
Werner Punz schrieb:
Martin Marinschek schrieb:
In any case, I remain -1 to add a new component library - I am sorry.
Ok I am going to postpone this discussion until I can showcase something
then we can start it over...
Hmm ... was Martin's -1 a veto or did he just express his opinion.
much more work.
Ciao,
Mario
Thank you.
On Wed, Jul 9, 2008 at 1:39 AM, Mario Ivankovits [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi!
s:xmlTemplate
Dont know much, not to say nothing, about that.
s:pprPanelGroup (is this component ready? it could be good
Hi!
(a) create a sub-project myfaces/orchestra/trunk/flow, publish to
snapshot-repo and main myfaces website as normel, but make sure that the
welcome page for the website says SANDBOX in big letters and the version
number is something like 0.0.1
+1
Often even the sandbox will be used also
Hi!
s:xmlTemplate
Dont know much, not to say nothing, about that.
s:pprPanelGroup (is this component ready? it could be good but I don't
know if there is any objection).
I do not think that pprPanelGroup is ready for a release, there are some
things still missing and sometimes it stopps
Hi Leonardo,
I tried to upgrade to the latest Tomahawk+Sandbox and now the
application fails to run properly as the
TomahawkFacesContextWrapper does the AddResource processing AND
the ExtensionsFilter does the AddResource processing.
The code in extension filter that do
Hi!
the use-case is that people want the same type of functionality they
have in their web.xml (specifying an error-page per exception) in the
JSF-world as well. Just doing it in the web.xml is not sufficient, as
then the faces-context is already closed and not available anymore, so
important
Hi!
Ok then those things are cleared up, now back to the original question
sandbox or own subproject?
+1 for own subproject.
Any further influence with tomahawk/sandbox needs to be avoided.
These two projects are still waiting for a overhaul themself.
Ciao,
Mario
Hi!
What is the current state of MYFACES-434?
I tried to upgrade to the latest Tomahawk+Sandbox and now the
application fails to run properly as the TomahawkFacesContextWrapper
does the AddResource processing AND the ExtensionsFilter does the
AddResource processing. This results in having
Hi!
One possible enhancement to the error handling feature of myfaces
could be the capability of redirect to a jsf page.
Any concrete use-case for this, or just yet another
cool-we-can-make-it thingy? ;-)
Seriously, what's wrong with the error page capabilities of the webapp
container?
Hi!
Ok, just to say something here too.
If you are going to create an accessibility application you have to put
more work into it than just adding an ALT text to your images.
Since a meaningful default text is not easy to find, if not
impossible, my vote is:
that means:
- log a nag warning
Hi!
Doesn't this change break backward compatibility completley?
The value of the alias= attribute now has to be defined differently,
instead of the el-expressesion just the name needs to be set.
Even if this change is logical to me, a new tomahawk release will break
any existing application
[
https://issues.apache.org/jira/browse/TOMAHAWK-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607465#action_12607465
]
Mario Ivankovits commented on TOMAHAWK-1014:
at least t:inputCalendar allows
[
https://issues.apache.org/jira/browse/TOMAHAWK-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits reopened TOMAHAWK-1014:
HTMLInputDate ignores custom converters
simon schrieb:
In other words, keeping one line of code makes sense (less
maintenance) even if we lose some JSF1.2/JSF2.0-specific features or
performance boosts.
While I second the rest of your mail, I wont do so with the sentence above.
We are developers, and, at least in your younger years
Hi!
why not getElementsByName[0] ?
Well, in general document.getElementById is both faster and more elegant.
So in this case, rendering this component with id=clientId seems reasonable.
Hmm..but it is possible that there are multiple view state fields in
the page, one per form.
Hi!
And also ensure that every ViewState will be replaced and not only the
first [0] one.
When you do have multiple JSF forms (which is valid) each ViewState
needs to be replaced.
Yes, but only when they came from the same view!
I don't know much about JSF portal bridge stuff. Can this
Hi!
I ignore what happens when use multiple jsf portlets in the same page,
or when the page is using multiple forms on the same page (normal
submits should work on both environmets, but ajaxified components?).
With I ignore you mean you will not replace the ViewState for each
form having a
Hi!
[X] +1 for community members who have reviewed the bits
Thanks for being the release-manager again!
Ciao,
Mario
Hi!
Simon and me had to spend 5 hours today to track down a problem which in
the end uncovered a nasty bug in TomahawkFacesContextWrapper. In
.release() the delegation was broken (due to a return in the try block).
Bad stuff :-(
Also I found some questionable stuff:
* Some important todos like
Hi!
Reason #3: The development community is not (so far) very large. Jihoon
Kim's initial code looks nicely written, but it was written as a hobby
project rather than being driven by any long-term goal.
Shouldn't the project go through the incubator for this reason?
MyFaces can be the sponsor
Hi!
I tried deleting the part regardless to persistence from spring
configuration (application-context.xml) but no success. I encountered
exceptions thrown by the Orchestra Conversation Interceptor.
Not configuring the persistence related advice (e.g the
://svn.apache.org/repos/asf/myfaces/myfaces-build-tools/branches/builder_plugin/bigtest/core_trunk_11/
So please vote if you want to see this feature included on myfaces 1.x
and tomahawk
regards
Leonardo Uribe
--
mit freundlichen Grüßen
Mario Ivankovits
Software Engineering
OPS EDV VertriebsgesmbH
at this amazing editor
http://www.cdolivet.net/editarea/editarea/exemples/exemple_full.html
the best, the code is under apache license!!!
Werner
Check your browser settings FF2 is exactly what I am using to view it :-)
--
mit freundlichen Grüßen
Mario Ivankovits
Hi!
MyfacesBuilderPlugin is almost complete. Actually works for 1.1 and
all interested people could see the example here:
Cool work guys. Great job!
Thanks for all the hard work!
Ciao,
Mario
[
https://issues.apache.org/jira/browse/ORCHESTRA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590607#action_12590607
]
Mario Ivankovits commented on ORCHESTRA-23:
---
*shocked* Really?! All due
[
https://issues.apache.org/jira/browse/MYFACES-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587862#action_12587862
]
Mario Ivankovits commented on MYFACES-1855:
---
It would be really great if you
[
https://issues.apache.org/jira/browse/TOMAHAWK-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits resolved TOMAHAWK-1214.
Resolution: Later
Immediate need for this feature is no longer existent
Hi!
my position on this is we could make sev-en part of orchestra, if the
orchestra crew really, really wants it. If not, this should just be a
separate sub-module in MyFaces. It is interesting enough to stand on
its own.
First, Orchestra is part of the MyFaces community, so it really,
[
https://issues.apache.org/jira/browse/ORCHESTRA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587058#action_12587058
]
Mario Ivankovits commented on ORCHESTRA-21:
---
Ouch ... good catch. Will do so
[
https://issues.apache.org/jira/browse/ORCHESTRA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587059#action_12587059
]
Mario Ivankovits commented on ORCHESTRA-21:
---
done
URLs are always encoded
[
https://issues.apache.org/jira/browse/ORCHESTRA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits resolved ORCHESTRA-21.
---
Resolution: Fixed
Fix Version/s: 2.0
Assignee: Mario Ivankovits
We
[
https://issues.apache.org/jira/browse/ORCHESTRA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585939#action_12585939
]
Mario Ivankovits commented on ORCHESTRA-20:
---
Currently, the viewController
[
https://issues.apache.org/jira/browse/ORCHESTRA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585944#action_12585944
]
Mario Ivankovits commented on ORCHESTRA-20:
---
Committed a fix for that too
[
https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586009#action_12586009
]
Mario Ivankovits commented on ORCHESTRA-19:
---
First draft committed. Most
Key: ORCHESTRA-19
URL: https://issues.apache.org/jira/browse/ORCHESTRA-19
Project: MyFaces Orchestra
Issue Type: Improvement
Components: Conversation
Reporter: Mario Ivankovits
Hi!
sev-en is a new jsf-extension.
Looks Cool, I love it to see that a long standing idea now seems to be
realized.
You posted on the dev list .. cool .. you probably know we are
developers too ... so .. where do we find the code? Or is it just a
too-late April joke ;-)
I think that would make
Project: MyFaces Core
Issue Type: Bug
Components: General
Affects Versions: 1.2.2, 1.1.5
Reporter: Mario Ivankovits
Assignee: Mario Ivankovits
Priority: Critical
When using server side state saving with serialize state in view
single conversation
---
Key: ORCHESTRA-20
URL: https://issues.apache.org/jira/browse/ORCHESTRA-20
Project: MyFaces Orchestra
Issue Type: Improvement
Components: Conversation
Reporter: Mario Ivankovits
[
https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585648#action_12585648
]
Mario Ivankovits commented on ORCHESTRA-19:
---
The conversationContext URL
[
https://issues.apache.org/jira/browse/ORCHESTRA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585651#action_12585651
]
Mario Ivankovits commented on ORCHESTRA-19:
---
The conversationContext api needs
... with serialize in state disabled.
I've create a small test case which shows that the attributes map is
just copied over into the state. Which means that each and every
Component shares exactly the same map. Any change to this map will be
reflected in ALL saved states.
Correct would be to
Hi!
It's because the wrong constructor in api's _ComponentAttributesMap
class, it's assigning the map directly:
So we do agree that this needs to be fixed? Then I'll do so ...
Ciao,
Mario
Ping!
It seems that Orchestra has to implement a StateManager which
holds the view state in the conversationContext instead of the session.
At the moment it seems that large portions of JspStateManagerImpl can be
reused, but requires to copy it over into Orchestra.
With slight refactoring of
Hi!
Mario, you are not alone in hating the shared concept. ;-)
Good!
1) has a super stable API
That is true, that might be the hardest part.
2) is used (ie. shared) by the myfaces core(!) as well as other myfaces
projects
Sure!
3) may be used by the experienced JSF app
Hi!
Orchestra having its own JspStateManagerImpl sounds interesting
though. Enabling this on Sun Mojarra for example will quite radically
change the way that a JSF app on Mojarra performs. That's not really
Orchestra's role.
I thought about this like an optional feature one has to
Hi!
are there any plans to release the core15 module ?
soon :-)
I would like open-source the @ConversationName annotation in core15 and
then we should be ready. Volunteering doing the release then?
Ciao,
Mario
Hi!
Just to reiterate: I hate shared! ;-)
Seriously, it seems that Orchestra has to implement a StateManager which
holds the view state in the conversationContext instead of the session.
At the moment it seems that large portions of JspStateManagerImpl can be
reused, but requires to copy it over
Hi!
Sorry for the lengthy mail ... Solving this problem just made me crazy
so easy problem, and so complicate if not impossible solution with JSF.
Everything I toucht in the last couple of days had some
side-effect/influence on something else.
My simple country/zip immediate show city ppr
Hi!
What do you think about an enhancement for ppr which allows to customize
the DOM update of the response?
So, instead of the simple domElement.innerHtml=xx stuff, one is able
to hook into that and provide his/hers own dom update.
s:pprPanelGroup
1 - 100 of 974 matches
Mail list logo
