Re: Re: Re: Re: Problems with a custom component when migrating from Glassfish(mojarra) to TomEE
Well I don't understand why they call it a MenuRenderer, as far as I can see it's a superclass for uiselectone uiselectmany... No equalent superclass is used for myfaces by the looks of things. So you might need to rewrite the whole thing from scratch and paying attention to making it portable. What you have there seems to be a hierarchy like ul li but with checkboxes instead. How does it work exactly? You select parent and it auto selects child nodes? Anyway if it's a bunch of selectone in a hierarchy you should be able to do it with css and ui:repeat and ajax? Give me a proper specification please Cheers On 14 February 2014 08:52, Rene Perschon chummer_r...@gmx.net wrote: Well the imports of com.sun.faces are offending, starting with MenuRenderer from which our custom renderer extends.. I've already tried to just swap the imports (for example for Apache Tobago's MenuRenderer, but it's final). I barely know about com.sun.faces and i've never used MyFaces before, so it's really hard for me to figure out the equivalents here Gesendet: Freitag, 14. Februar 2014 um 08:49 Uhr Von: Karl Kildén karl.kil...@gmail.com An: MyFaces Discussion users@myfaces.apache.org Betreff: Re: Re: Re: Problems with a custom component when migrating from Glassfish(mojarra) to TomEE Rene, I at least can't see anything. Another thing to think about it what impl stuff you have actually worked with? I mean mojarra should have about the same stuff as myfaces? To make myself clear, what does the components and stuff you extend really belong to? Shouldn't be impossible to find equivalents in myfaces... On 14 February 2014 08:45, Rene Perschon chummer_r...@gmx.net wrote: Yes, here it is. It's a two-stage component which displays a hierarchical (2 levels) selection choice. Gesendet: Donnerstag, 13. Februar 2014 um 16:57 Uhr Von: Howard W. Smith, Jr. smithh032...@gmail.com An: MyFaces Discussion users@myfaces.apache.org Betreff: Re: Re: Problems with a custom component when migrating from Glassfish(mojarra) to TomEE do you have a screen capture or some type of demo of the Select component? On Thu, Feb 13, 2014 at 8:39 AM, Rene Perschon chummer_r...@gmx.net wrote: I don't think a TagHandler or a custom component can do what that code does. It's used to display a Select in a very specific way. Gesendet: Donnerstag, 13. Februar 2014 um 14:29 Uhr Von: Karl Kildén karl.kil...@gmail.com An: MyFaces Discussion users@myfaces.apache.org Betreff: Re: Problems with a custom component when migrating from Glassfish(mojarra) to TomEE Have you considered a custom tagHandler / composite component instead? I took a quick look but I don't recognize much sorry. On 13 February 2014 14:09, Howard W. Smith, Jr. smithh032...@gmail.com wrote: I think Leonardo, Gerhard, or one of the other committers may provide her some good help, just to get another MyFaces user, especially when one is migrating from Mojarra to MyFaces. @Renee, +1 your goal/request. I migrated from Mojarra to MyFaces, first, and then 2 months later, I migrated from Glassfish to tomee (and JSF managed beans to CDI managed beans at same time). Thomas, Romain, Mark Struberg, and others provided great help and motivation. Apache tomee, MyFaces, tomcat user mail lists are definitely the place to be. But I didn't have code dependent on the Mojarra library like you do. Still, it took me about a week to migrate from Mojarra to MyFaces. Thomas and Leonardo motivated me to start the migration after reading about the performance comparison between Mojarra and MyFaces. Mark Struberg blog, why is OpenWebBeans so fast, motivated me to migrate to CDI and tomee. :-) I love high performance, that's why I opted to use MyFaces, tomee, OpenWebBeans, and JUEL. Wishing you much success. On Feb 13, 2014 7:23 AM, Thomas Andraschko andraschko.tho...@gmail.com wrote: I don't think that anyone will port your complete code and give you a complete solution ;) The biggest problem is AFAIR that the renderer implementations are not in the API packages. So you have to rebuild all this functionality without dependencies to the Impl. e.g. Attribute,AttributeManager - String[] with attribute namens Move all the utils functions to your own code (Util.componentIsDisabled, RenderKitUtils.getSelectItems. etc.) The most code doesn't really depent on the IMPL code. 2014-02-13 12:44 GMT+01:00 Rene Perschon chummer_r...@gmx.net: Hi everyone! I'm currently migrating an application from Glassfish 3.1.1 to TomEE. Now the problem is that this application contains a custom component which was unfortunately coded with hard dependencies on com.sun.faces classes
Re: Composite component does not render
Find a new answer on StackOverflow. You have to set the parameter org.apache.myfaces.STRICT_JSF_2_ALLOW_SLASH_LIBRARY_NAME as Leo suggested, than it works. Best regards Michi Am 13.02.2014 17:55, schrieb Kito Mann: Hello Johannesburg, Your namespace is incorrect. It should be: xmlns:meg=http://java.sun.com/jsf/composite/components/topNav; Assuming that you the folder [Web root]/resources/components/topNav is where your component is. On Thursday, February 13, 2014, Johannes Murth johannes.mu...@gmail.com wrote: See http://stackoverflow.com/questions/21582937/composite-component-in-jsf-2-2-will-not-render/21757729#21757729
Re: Composite components in myfaces 2.2.
Hi, would be interesting how your composite component looks like (the basic structure) and how it is embedded in the page. Best regards Michi Am 13.02.2014 13:10, schrieb Johannes Murth: Hi! I just upgraded from 2.1 to 2.2 and have rendering problem because xml doctype and html tag are rendered right before composite component. These break the layout and should just be swallowed. Thanks for any advice!
Re: myfaces 2.2 foe replace myfaces 2.1 into tomee
tank you very much
2014-02-14 8:47 GMT+01:00 Mark Struberg [via MyFaces]
ml-node+s10567n117182...@n7.nabble.com:
GAV = groupId + artifactId + version.
See the sample of the mysql connector
libmysql:mysql-connector-java:${mysql-connector.version}/lib
For myfaces this would be
liborg.apache.myfaces.core:myfaces-api:${myfaces.version}/lib
LieGrue,
strub
On Thursday, 13 February 2014, 19:09, maurojava [hidden
email]http://user/SendEmail.jtp?type=nodenode=117182i=0
wrote:
escuse me Mark i not know maven
how i can make the last your indication:
-
for adding jars to your tomee plugin, just use the maven GAV coordinates.
If it starts with remove:xxx, then it will remove all the jars starting
with this string.
---
how i can put the jars dor tomme plugin using the GAV coordinates?
2014-02-13 18:44 GMT+01:00 Mark Struberg [via MyFaces]
[hidden email] http://user/SendEmail.jtp?type=nodenode=117182i=1:
btw if you use the tomee-maven-plugin then you can automatically 'tune'
the lib folders with something like this:
build
plugins
plugin
groupIdorg.apache.openejb.maven/groupId
artifactIdtomee-maven-plugin/artifactId
version${tomee.mavenplugin.version}/version
configuration
...
libs
libmysql:mysql-connector-java:${mysql-connector.version}/lib
libremove:myfaces-api/lib
libremove:myfaces-impl/lib
/libs
/configuration
for adding jars to your tomee plugin, just use the maven GAV
coordinates.
If it starts with remove:xxx, then it will remove all the jars starting
with this string.
LieGrue,
strub
On Wednesday, 12 February 2014, 19:02, Karl Kildén [hidden email]
http://user/SendEmail.jtp?type=nodenode=117170i=0
wrote:
Try starting it outside of your IDE. If that works remove and reconnect
IDE
to a fresh TomEE on another path with the desired changes under /lib
On 12 February 2014 18:48, maurojava [hidden email]
http://user/SendEmail.jtp?type=nodenode=117170i=1
wrote:
my jsk is : jdk1.7.0_25
my tomee :tomee 1.6.0 plus
i have added myfaces-api2.2jar and myfaces-impl2.2.jar to tomee/lib
i have removed myfaces 2.1 impl and api
i not use codi
--
View this message in context:
http://myfaces.10567.n7.nabble.com/myfaces-2-2-foe-replace-myfaces-2-1-into-tomee-tp117127p117135.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the
discussion
below:
http://myfaces.10567.n7.nabble.com/myfaces-2-2-foe-replace-myfaces-2-1-into-tomee-tp117127p117170.html
To unsubscribe from myfaces 2.2 foe replace myfaces 2.1 into tomee,
click
here
.
NAML
http://myfaces.10567.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
--
View this message in context:
http://myfaces.10567.n7.nabble.com/myfaces-2-2-foe-replace-myfaces-2-1-into-tomee-tp117127p117173.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the discussion
below:
http://myfaces.10567.n7.nabble.com/myfaces-2-2-foe-replace-myfaces-2-1-into-tomee-tp117127p117182.html
To unsubscribe from myfaces 2.2 foe replace myfaces 2.1 into tomee, click
herehttp://myfaces.10567.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=117127code=bWF1cm8yamF2YTIwMTFAZ21haWwuY29tfDExNzEyN3wtMTExNzE4NzYyNQ==
.
NAMLhttp://myfaces.10567.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
--
View this message in context:
http://myfaces.10567.n7.nabble.com/myfaces-2-2-foe-replace-myfaces-2-1-into-tomee-tp117127p117196.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?
Can some one please clarify What is this attributes map otherwise really meant for? Is it to maintain JSF internal viewstate ? On Fri, Feb 14, 2014 at 1:31 AM, user 01 user...@gmail.com wrote: Thanks a lot Leonardo for the solution. Played somewhat with it, looks like it'll works for me. The data survives session destroys. What is this attributes map otherwise really meant for, to maintain JSF internal viewstate ? Is it safe for me to use it like that ? Looks like a hack infact:) I could use the attributes map to store values/ objects, can't I just use this map to store the viewscoped beans simply? On Thu, Feb 13, 2014 at 11:05 AM, Leonardo Uribe lu4...@gmail.com wrote: Hi In JSF 2.2 it was decided to store view scope beans always in session (take a look at the description of @ViewScoped annotation in the javadoc). But you can just call facesContext.getViewRoot() and use the attribute map. Just remember the values there must be Serializable or implement StateHolder. In my understanding, this was done in this way to support @PreDestroy annotation when the session is expired. regards, Leonardo Uribe 2014-02-12 23:28 GMT-05:00 user 01 user...@gmail.com: I'm using Myfaces 2.2 with Client-side state saving. I see that the ViewScoped beans data stored in viewmap is lost after the user session is destroyed. I came to know, not sure if it is correct, that this is the expected behavior but then what's the way to avoid view expired exceptions after session destroy? My problem is that I destroy the user session pretty quickly after some inactivity period(like after 20 minutes) but I want the viewscope data to survive even after that(when using client saving) so that when the user comes back after session destroy, he doesn't need to do a page refresh. I dont know why how this is so implemented but It is very normal that the user may be busy reading some section of website or be away for 20 minutes, as he comes back interacts with opened pages, how would I make that work without the state ? I think this is a common requirement for any public websites. I think the internally used jsf viewstate is not lost, if I use client side state saving(as my pages still work), but then why are those viewscoped beans scoped that were also serialized to page along with the viewstate. If this the designed behavior, Is there any way I could make the view scoped data survive session expiration ?
