Re: MyFaces 1.2.4 and WebLogic 10.3- strict servlet API: cannot call getWriter() after getOutputStream()

2009-03-13 Thread Matthias Wessendorf
Leo, looks correct -M On Fri, Mar 13, 2009 at 1:26 AM, Leonardo Uribe lu4...@gmail.com wrote: Hi There is a possible solution to this issue on MYFACES-1955. It could be good if anyone can probe it on WebLogic, to make sure if it works and close this issue regards Leonardo Uribe On

Re: Refresh View after HTTPSession Timeout

2009-03-13 Thread Simon Kitching
Hi, The solution I use is to put a ping script in the page which sends a request to the server every couple of minutes. With that, the session never times out while the browser window is open, and so the problem never occurs. Of course this requires javascript, but is javascript is disabled then

Re: Refresh View after HTTPSession Timeout

2009-03-13 Thread Walter MourĂ£o
Suggestion: 1 - add a javascript state change listener; 2 - check the contents of the request using TrXMLRequestEvent getResponseText() and/or getResponseStatusCode() 3 - if the result isn't a PPR result, notify the user or send the browser to a specified url. I'm planing to write something like

t:selectItems with a map

2009-03-13 Thread Johannes Ruthenberg
Hi! I'm new to this list and to JSF in general. I have a problem with the t:selectItems component and would be grateful for any advice. I'm using MyFaces 1.2.5, Tomahawk 1.1.8 and Facelets. I have this in my file: h:selectManyCheckbox id=selectedRoles value=#{myBean.selectedRoles}

Re: Memory issue : MyFaces objects in session

2009-03-13 Thread Simon Kitching
Hi Seema, On Thu, 2009-03-12 at 10:37 -0700, seemamani wrote: We are using MyFaces 1.1.5 in our web application deployed in WAS 6.1. Recently we faced some memory issues due to session size. We have set the STATE_SAVING_METHOD as server in web.xml. Our WebSphere support team found several

[TRINIDAD] Passing a request parameter to a session bean

2009-03-13 Thread Amaris Nieves
I can actually create a request managed bean that will hold the request parameters. I can use the properties of the managed bean on the page, but...What should I do to pass those parameters to a session bean? The f:param tag does not work with Trinidad commandButton's, right?