I have an application where I am trying to change the JSF implementation
from MyFaces Core 1.2.6 to Mojarra 1.2_12. I was hoping the application
could still make use of the tomahawk saveState tag, as we use it heavily
throughout the application. But it appears that the saveState tag is not
-resolvercom.mypackage.util.CustomManagedBeanResolver/el-resolver
Seems to be working ok, just not sure if this will cause any issues.
Thanks,
Geoff
On Wed, Apr 8, 2009 at 8:41 AM, Geoff Longo gmlo...@gmail.com wrote:
I have an application where I am trying to change the JSF implementation
from MyFaces
explicitly - it's not depending on the
state saving method. Use
context-param
param-nameorg.apache.myfaces.USE_ENCRYPTION/param-name
param-valuefalse/param-value
/context-param
Regards,
Felix
-Original Message-
From: Geoff Longo [mailto:gmlo...@gmail.com]
Sent
We just upgraded our application to Myfaces 1.2 and periodically I get
the BadPaddingException. The strange part is, we are using
server-side state saving. From our web.xml:
context-param
descriptionState saving method: client or server (= default)
See JSF Specification 2.5.2/description
I think this might have been addressed in the latest RichFaces
development builds (3.2?) but I haven't been able to confirm. Has
anybody gotten around this issue?
On Mon, Mar 10, 2008 at 1:39 PM, Michael Heinen [EMAIL PROTECTED] wrote:
I am facing a problem with t:saveState which could be
I was wondering what the best way would be to create a dataTable that
has a column that includes a dropdown, but the dropdown choices may be
different in each row. Any ideas?
Thanks,
Geoff
I had the same issue with the javascript location. No matter what I
did, it always referred to the extensions resources.
-G
On 7/5/06, Michael Heinen [EMAIL PROTECTED] wrote:
Hi,
I don't want that the the InputCalendar loads the images from the resources
directory using the
Not sure if it matters, but have you tried putting an id on your
saveState tag? For example,
t:saveState id=pcwBacker value=#{pcwBacker}/
This is how we are set up and it works perfectly with Facelets.
Geoff
On 6/13/06, octoberdan [EMAIL PROTECTED] wrote:
Yes; everything else works.
--
Is this attribute still supported? I can't seem to get it to work.
Thanks,
Geoff
We had a similar issue. We have all our currencies defined as Doubles
currently, but we would get errors on values that resolved to Longs
(ex. 1.0). We had to create our own converter that always converted
the Number to a Double.
We wanted to extend the existing number converter just like you
Have you looked into the saveState component?
http://wiki.apache.org/myfaces/SaveState
On 4/25/06, Werner Punz [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb:
I have a Datatable which has thousands of items in it. I get this items
via a database. I don't want to store them in the
, Werner Punz [EMAIL PROTECTED] wrote:
Geoff Longo schrieb:
Have you looked into the saveState component?
http://wiki.apache.org/myfaces/SaveState
On 4/25/06, Werner Punz [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] schrieb:
I have a Datatable which has thousands of items in it. I get
Yeah, I noticed this too. I filed a bug a few weeks back. I would
give you the bug number, but the myfaces jira seems to be down.
-G
On 4/9/06, David Miller [EMAIL PROTECTED] wrote:
I think I figured it out.
- forceId = 'true' isn't working on the inputCalendar tag.
False or true, my id
I am having what appears to be an issue with saveState not working on
Websphere 6. My backing bean is request scoped and my jsf is saving
the state of the entire backing bean. This works perfectly on Tomcat
5.5, but when I deploy to Websphere, things seem to fall apart.
Currently, my backing
,
Geoff
On 3/29/06, Mike Kienenberger [EMAIL PROTECTED] wrote:
On 3/29/06, Geoff Longo [EMAIL PROTECTED] wrote:
I am having what appears to be an issue with saveState not working on
Websphere 6. My backing bean is request scoped and my jsf is saving
the state of the entire backing bean
I am trying to override the javascript location used by inputCalendar.
If I specify the following:
t:inputCalendar id=clientRequestBirthDate forceId=true
javascriptLocation=/ota/jsf/scripts
monthYearRowClass=yearMonthHeader weekRowClass=weekHeader
renderPopupButtonAsImage=true size=10
Thanks for your reply. I'll try the latest build to resolve the phase
listener issue. As for the calendar, I am now getting some resource
not found exceptions in the console when bringing the page up. So
when the page displays, there is a javascript error saying that it
can't find
The style on my div has no position specified.
#contentdiv
{
border-bottom: 1px solid #808080;
overflow: auto;
height:100%;
}
On 2/24/06, Lukchai Pattarakijkomjorn [EMAIL PROTECTED] wrote:
don't use position:absolute;
Since I started using the nightly builds, I am having a similar
problem. The calendar was popping up much lower than it did in the
previous stable builds. I noticed a comment in the issue tracking
that the positioning was fixed on 02/22
(http://issues.apache.org/jira/browse/MYFACES-635), but the
I noticed that in the nightly builds, the collapsed attribute of the
collapsiblePanel was removed. How do we specify that we want the
panel to be displayed as collapsed on entry to the page?
Thanks,
Geoff
I am having an issue with the latest nightly builds concerning the
calendar popup positioning. It is popping up and functioning
correctly, except it doesn't pop up next to the icon like it used to.
It now appears a few lines down from the icon that triggered it. Any
ideas?
Thanks,
Geoff
21 matches
Mail list logo
