Available)
MyFaces 2.2 throws UnsupportedOperationException with an eager ManagedBean
with ManagedProperty
---
Key: MYFACES-4010
URL: https://issues.apache.org/jira/browse
Bill Lucy created MYFACES-4010:
--
Summary: MyFaces 2.2 throws UnsupportedOperationException with an
eager ManagedBean with ManagedProperty
Key: MYFACES-4010
URL: https://issues.apache.org/jira/browse/MYFACES-4010
[
https://issues.apache.org/jira/browse/MYFACES-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Lucy updated MYFACES-4010:
---
Status: Patch Available (was: Open)
MyFaces 2.2 throws UnsupportedOperationException
Hello Leonardo,
Thanks for your reply. I'm the creator of this component. The component
belongs to the PrimeFaces Extensions. As I already told you, this was
working in JSF 2.0, 2.1 and still works in Mojarra 2.2. So, I don't think
we have a bug there. Do you mean we don't need
in JSF 2.0 and 2.1 because that statement effectively does not
have any effect. In other words, it is just ignored. It fails in
MyFaces 2.2 because
MyFaces takes care of it, which has sense to me.
The implementation done in Mojarra 2.2 has a lot of problems related to
vdl.createComponent
Leonardo Uribe created MYFACES-3877:
---
Summary: Add @ListenerFor(systemEventClass =
PostRestoreStateEvent.class) causes StackOverflowException on MyFaces 2.2
Key: MYFACES-3877
URL: https://issues.apache.org/jira
= PostRestoreStateEvent.class) causes
StackOverflowException on MyFaces 2.2
-
Key: MYFACES-3877
URL: https://issues.apache.org/jira/browse/MYFACES-3877
every component is already subscribed to that event. The reason
is the binding attribute uses PostRestoreStateEvent to restore the bindings.
In fact, it works in JSF 2.0 and 2.1 because that statement effectively does
not
have any effect. In other words, it is just ignored. It fails in
MyFaces
the
bindings.
In fact, it works in JSF 2.0 and 2.1 because that statement effectively
does not
have any effect. In other words, it is just ignored. It fails in
MyFaces 2.2 because
MyFaces takes care of it, which has sense to me.
The implementation done in Mojarra 2.2 has a lot of problems
Hello MyFaces team,
We get a StackOverflowError since MyFaces 2.x. The stack trace is shown
here http://forum.primefaces.org/viewtopic.php?f=14t=36999
The problem: Wenn we call super.processEvent(event) in the
processEvent() of a custom component, we get a recursion which ends in
By the way, it is a common pattern to call in a custom component e.g.
super.processDecodes() in processDecodes() or super.processValidators()
in processValidators(). This was always working before.
Am 30.03.2014 23:23, schrieb Oleg Varaksin:
Hello MyFaces team,
We get a StackOverflowError
Hi
I can see a change that was introduced in JSF 2.2. It has the
following description:
// JSF 2.2 vdl.createComponent() requires special handling
to refresh
// dynamic parts when refreshing is done. The only way to do it is
// attaching a listener to
Hi
For the people who want to know quickly what's new in MyFaces 2.2, I
have written a summary of the new features here:
http://lu4242.blogspot.com/2014/01/whats-new-in-myfaces-22.html
regards,
Leonardo Uribe
or features from earlier versions in MyFaces 2.2
--
Key: MYFACES-3715
URL: https://issues.apache.org/jira/browse/MYFACES-3715
Project: MyFaces Core
Issue Type: Task
not affect the
way how state saving restoring works. I unfortunately have to say that your
comment does not have sense. This feature is something new, ouside JSF 2.2
spec but proposed to be included in MyFaces 2.2. What we are doing here and we
have done for more than 1 year is discuss
but proposed to be included in MyFaces 2.2. What we are doing here and
we have done for more than 1 year is discuss and justify the addition of
this feature.
regards,
Leonardo Uribe
Regards,
Dora Rajappan.
On Friday, December 13, 2013 2:21 PM, Thomas Andraschko
andraschko.tho
Cool leo! Thanks for your effort :)
2013/12/13 Leonardo Uribe lu4...@gmail.com
Hi
Finally the code for View Pooling has been comitted. After some
performance
tests with the know demo application, it has been confirmed the following
improvements:
- A reduction of 25% of the transient
Not bad +1 for view pool.
When VIEW_POOL_ENABLED the param
org.apache.myfaces.NUMBER_OF_SEQUENTIAL_VIEWS_IN_SESSION is not considered and
not required to set.
org.apache.myfaces.NUMBER_OF_SEQUENTIAL_VIEWS_IN_SESSION is valid for state
saving client/server.
Regards,
Dora Rajappan.
On
in MyFaces 2.2. What we are doing here and
we have done for more than 1 year is discuss and justify the addition of
this feature.
regards,
Leonardo Uribe
Regards,
Dora Rajappan.
On Friday, December 13, 2013 2:21 PM, Thomas Andraschko
andraschko.tho...@gmail.com wrote:
Cool leo! Thanks
works. I unfortunately have to say that your comment
does not have sense. This feature is something new, ouside JSF 2.2 spec but
proposed to be included in MyFaces 2.2. What we are doing here and we have done
for more than 1 year is discuss and justify the addition of this feature.
regards
not have sense. This feature is something new, ouside JSF 2.2
spec but proposed to be included in MyFaces 2.2. What we are doing here and
we have done for more than 1 year is discuss and justify the addition of
this feature.
regards,
Leonardo Uribe
Regards,
Dora Rajappan
Hi
Finally the code for View Pooling has been comitted. After some performance
tests with the know demo application, it has been confirmed the following
improvements:
- A reduction of 25% of the transient memory used, which means a lot less
memory is used and it is used at a slower pace. It also
Hi Leo,
sounds fine! thanks :)
2013/12/9 Leonardo Uribe lu4...@gmail.com
Hi
I think we could add it as a parameter for f:view tag, for example call it
oamEnableViewPool. The patch proposed uses already an attribute for disable
the pool in some cases, but after doing some experiments
Hi
It seems we have an inconsistency between what was proposed to enable the
view pool and the inclusion of the new parameter.
At start we have this:
org.apache.myfaces.VIEW_POOL_ENABLED (enable / disable for all pages in the
app, by default false)
But if we use an attribute in f:view like
Hi Leo,
a attribute for the viewroot sound greats. +1.
How would you set this attribute then?
Setting the attribute should only be required one time - so maybe a
PhaseListener isn't the best place.
Regards,
Thomas
2013/12/7 Leonardo Uribe lu4...@gmail.com
Hi Thomas
What I can do is use an
Hi
I think we could add it as a parameter for f:view tag, for example call it
oamEnableViewPool. The patch proposed uses already an attribute for disable
the pool in some cases, but after doing some experiments (MYFACES-3831) I
have found we need to change some parts of the algorithm.
Leo, one question:
Is it possible to mark a view as poolable via code?
We configure all our views via typesafe view config from CODI/DS
2013/12/4 Thomas Andraschko andraschko.tho...@gmail.com
Looks fine for me!
2013/12/3 Leonardo Uribe lu4...@gmail.com
Hi
I have been thinking about how
Hi Thomas
What I can do is use an attribute to mark the view as poolable or not
poolable.
The annotation code must be done outside core.
regards,
Leonardo
2013/12/7 Thomas Andraschko andraschko.tho...@gmail.com
Leo, one question:
Is it possible to mark a view as poolable via code?
We
Looks fine for me!
2013/12/3 Leonardo Uribe lu4...@gmail.com
Hi
I have been thinking about how to define the configuration for the view
pool. The idea is add the following new web config parameters:
org.apache.myfaces.VIEW_POOL_ENABLED (enable / disable for all pages in
the app, by
Hi
I have been thinking about how to define the configuration for the view
pool. The idea is add the following new web config parameters:
org.apache.myfaces.VIEW_POOL_ENABLED (enable / disable for all pages in the
app, by default false)
org.apache.myfaces.VIEW_POOL_MAX_POOL_SIZE (the number of
Hi,
+1 for this feature in core 2.2.
Regards,
Kocicak
2013/11/24 Thomas Andraschko andraschko.tho...@gmail.com
Perfect. Thanks for Info.
So +1 from my side.
2013/11/24 Leonardo Uribe lu4...@gmail.com
Hi
2013/11/24 Thomas Andraschko andraschko.tho...@gmail.com
Hi Leo,
By
are compatible, that view is poolable.
Should we include it in MyFaces 2.2.x? why not? after all, it is something
that can be optional. For example, libraries like Trinidad provides
org.apache.myfaces.trinidad.
CACHE_VIEW_ROOT web config param. This feature
is something that aims to the same
Hi Leo,
By default all the code in UIComponentBase is already in place, so if all
components extend from UIComponentBase everything will work just fine
cool, perfect!
What about Behaviors or ActionListeners like:
Hi
2013/11/24 Thomas Andraschko andraschko.tho...@gmail.com
Hi Leo,
By default all the code in UIComponentBase is already in place, so if all
components extend from UIComponentBase everything will work just fine
cool, perfect!
What about Behaviors or ActionListeners like:
Perfect. Thanks for Info.
So +1 from my side.
2013/11/24 Leonardo Uribe lu4...@gmail.com
Hi
2013/11/24 Thomas Andraschko andraschko.tho...@gmail.com
Hi Leo,
By default all the code in UIComponentBase is already in place, so if
all components extend from UIComponentBase everything will
significantly the time spent in ajax request.
- If all components in a view are compatible, that view is poolable.
Should we include it in MyFaces 2.2.x? why not? after all, it is something
that can be optional. For example, libraries like Trinidad provides
org.apache.myfaces.trinidad
the advantages justify the introduction of this concept? In my personal
opinion probably yes by two main reasons:
- It improves significantly the time spent in ajax request.
- If all components in a view are compatible, that view is poolable.
Should we include it in MyFaces 2.2.x? why not? after all
Hello,
Is there a projected release date for MyFaces 2.2?
___
Kito D. Mann | @kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info |
@jsfcentral
+1 203-998-0403
* Listen
Hi Kito
Not yet, but we are close to have all big ticket features in place.
Obviously the code requires review, so stay tuned.
regards,
Leonardo Uribe
2013/6/26 Kito Mann kito.m...@virtua.com:
Hello,
Is there a projected release date for MyFaces 2.2?
___
Kito D. Mann | @kito99 | Author
Leonardo Uribe created MYFACES-3715:
---
Summary: Remove unnecessary parameters or features from earlier
versions in MyFaces 2.2
Key: MYFACES-3715
URL: https://issues.apache.org/jira/browse/MYFACES-3715
Hi folks!
Who is setting this up?
If you point me to a job I can copy then I can also handle it.
LieGrue,
strub
Hi
Look on this link:
https://builds.apache.org/
I can see a job with name myfaces-current22 ... Gerhard started it 3
minutes ago.
regards,
Leonardo Uribe
2012/11/23 Mark Struberg strub...@yahoo.de:
Hi folks!
Who is setting this up?
If you point me to a job I can copy then I can also
done (see [1]).
regards,
gerhard
[1] https://builds.apache.org/view/M-R/view/MyFaces/job/myfaces-current22/
http://www.irian.at
Your JSF/JavaEE powerhouse -
JavaEE Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2012/11/23 Mark Struberg
Mark Struberg created MYFACES-3650:
--
Summary: myfaces-2.2.x poms not properly set up
Key: MYFACES-3650
URL: https://issues.apache.org/jira/browse/MYFACES-3650
Project: MyFaces Core
Issue
[
https://issues.apache.org/jira/browse/MYFACES-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved MYFACES-3650.
Resolution: Fixed
Fix Version/s: 2.2.0
myfaces-2.2.x poms not properly set
on my testing project on apache extras, I would like to ask
what the status is regarding a MyFaces 2.2 branch.
Is there any intention to open one? I would like to merge my work back
into the main repository.
Werner
No one interested, Leonardo whats your opinion about the jsf 2.2 branch?
Werner
Werner Punz created MYFACES-3621:
Summary: Create MyFaces 2.2 Branch
Key: MYFACES-3621
URL: https://issues.apache.org/jira/browse/MYFACES-3621
Project: MyFaces Core
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/MYFACES-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved MYFACES-3621.
--
Resolution: Fixed
Create MyFaces 2.2 Branch
Am 09.10.12 10:43, schrieb Werner Punz:
Hello everyone, since I have started to work on jsf 2.2 jsf.js but
currently on my testing project on apache extras, I would like to ask
what the status is regarding a MyFaces 2.2 branch.
Is there any intention to open one? I would like to merge my work
have started to work on jsf 2.2 jsf.js but
currently on my testing project on apache extras, I would like to ask
what the status is regarding a MyFaces 2.2 branch.
Is there any intention to open one? I would like to merge my work back
into the main repository.
Werner
No one interested
Hello everyone, since I have started to work on jsf 2.2 jsf.js but
currently on my testing project on apache extras, I would like to ask
what the status is regarding a MyFaces 2.2 branch.
Is there any intention to open one? I would like to merge my work back
into the main repository.
Werner
Hi,
are there any plans on starting a MyFaces Core 2.2 branch? I think Leo
mentioned something a while ago.
Regards
Michi
Hi
For now there is only the branch for test windowId improvement:
http://svn.apache.org/repos/asf/myfaces/core/branches/2.1.x-client-window/
I think it is better to create a branch after the public review, and
instead keep an eye on what's going in jsr344-experts list.
regards,
Leonardo
53 matches
Mail list logo
