Aug
27
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
I have this idea that maybe it is something related to serialization. Maybe my Serializable @SessionBean is serializing and saving a @ManagedProperty on my Serializable @ApplicationBean. Maybe when I restart the application a new @ApplicationBean is created but the deserialization recovers the old one on the @SessionBean @ManagedProperty, and that's why I have two instances and two different references for my @ApplicationBean?
Aug
27
comment Order of FacesContext.getCurrentInstance().getApplication().getSupportedLocales()
This is really cool! 2.2 here we go! :-)
Aug
26
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
I've been trying to, but no luck. Whatever it is causing the problem I am not able to pinpoint it clearly enough. Now that I have a workaround I'll let it rest and try again with a fresher mind and more time to analyze it. If I find something I'll be posting it here. Thanks for the help :-)
Aug
26
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
Anyway, thanks for the link. I had already checked it, as well as your other excellent answer: stackoverflow.com/questions/7499534/… which I followed for the implementation I have right now (using the ScheduledExecutorService on my RefreshListsTaskScheduler and the @PostConstruct and @Predestroy methods).
Aug
26
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
..., and I still can't identify what triggers this issue.
Aug
26
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
Anyway, now I don't pass any managed property to my Runnable. I pass the reference to the RefreshListsTaskScheduler, and the RefreshListsTaskScheduler takes care of the actual refresh. I don't use managed properies anymore, just the Faces.evaluateExpressionGet method, and that fixes the problem, but not the cause. I still get different object ids for the application bean retrieved as a @ManagedProperty and as Faces.evaluateExpressionGet; it happens only on some runs; sometimes the application starts and both ids are the same and nothing happens...
Aug
26
comment Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
Actually the ManagedProperty was not in the Runnable. I had an @ApplicationBean, RefreshListsTaskScheduler, where the @ManagedProperty is retrieved and passed to the RefreshListsTask implementing Runnable. I oversimplified the example.
Aug
26
revised Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
edited body
Aug
26
revised Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
deleted 1 character in body
Aug
26
asked Faces.evaluateExpressionGet('#{myBean}'); and @ManagedProperty(value="#{myBean}"); returning different objects
Aug
26
accepted Order of FacesContext.getCurrentInstance().getApplication().getSupportedLocales()
Aug
25
revised Order of FacesContext.getCurrentInstance().getApplication().getSupportedLocales()
added 1 character in body
Aug
25
asked Order of FacesContext.getCurrentInstance().getApplication().getSupportedLocales()
Aug
24
comment The "Stack Overflow in Spanish" Project is Underway!
Cuando los arrays acaben siendo arreglos y el código de la última aplicación que metí en github se muera de asco en lugar de ser revisado y mejorado para beneficio mutuo por un programador alemán que se encontró exactamente lo que buscaba, a pesar de ser una necesidad de 1 entre varios millones, ahorrándonos a ambos cientos de horas gracias a que github contiene proyectos de cientos de millones de colaboradores usando una lengua franca en lugar de la que les impone su gobierno, espero que todas esas ventajas de que cada palo aguante su vela sigan pareciendo igual de excepcionales.
Aug
24
awarded Tumbleweed
Aug
22
revised StackOverflow brings together millions of programmers in a collective effort. Why partition it into mutually exclusive areas of overlapping info?
added 389 characters in body
Aug
22
revised StackOverflow brings together millions of programmers in a collective effort. Why partition it into mutually exclusive areas of overlapping info?
added 389 characters in body
Aug
22
comment The "Stack Overflow in Spanish" Project is Underway!
Ahí es donde diferimos: Hay que llegar a los que no hablan inglés, pero llevar la montaña a mahoma no es la solución: estarias dejando al resto sin montaña. Ayudar a que la gente aprenda inglés de la misma manera que les ayudamos a aprender a programar SI es la solución; y la mejor forma de maximizar la probabilidad de que el día de mañana ellos nos ayuden a nosotros. Stackoverflow se basa en la solidaridad y la necesidad de alimentar el ego con reconocimiento. Centremonos en lo primero, que es lo realmente útil para todos.
Aug
22
revised Text/Code highlight with jsDoc
edited body
Aug
22
revised Text/Code highlight with jsDoc
added 1 character in body
1 2 3 4 5