[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3707) SEAM 2.1.0 causes flickering images
by Tim Evers (JIRA)
SEAM 2.1.0 causes flickering images
-----------------------------------
Key: JBSEAM-3707
URL: https://jira.jboss.org/jira/browse/JBSEAM-3707
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.GA
Environment: IE 6 with cache setting set to "check for new version every page visit"
Reporter: Tim Evers
When the project I am on upgraded from SEAM 2.0.1 to 2.1.0 we ran into this issue.
All our images in our application flicker on load. So, if we have a mouse over that changes the background of a button, the button will flicker on the event.
I've researched the whole flickering images problem with IE 6 and none of the workarounds are working. So it seems that there is some javascript(? maybe) in SEAM that is causing this to happen.
See forum reference for a little bit more info.
PLEASE NOTE: You must set your cache settings to "check for new version every page visit" for this bug to appear
I am 100% sure that this is a seam issue because I can revert just the SEAM libraries back to 2.0.1 and this issue will go away.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3694) Double database requests in contactlist
by Bernard Pons (JIRA)
Double database requests in contactlist
---------------------------------------
Key: JBSEAM-3694
URL: https://jira.jboss.org/jira/browse/JBSEAM-3694
Project: Seam
Issue Type: Bug
Components: Examples
Affects Versions: 2.0.2.SP1, 2.0.1.GA
Environment: Tomcat 6 / Embedded JBoss
Reporter: Bernard Pons
Any search initiated in contactlist example application generates the same request twice :
Hibernate:
select
top ? contact0_.id as id4_,
contact0_.address as address4_,
contact0_.businessPhone as business3_4_,
contact0_.cellPhone as cellPhone4_,
contact0_.city as city4_,
contact0_.country as country4_,
contact0_.firstName as firstName4_,
contact0_.homePhone as homePhone4_,
contact0_.lastName as lastName4_,
contact0_.state as state4_,
contact0_.version as version4_,
contact0_.zip as zip4_
from
Contact contact0_
where
lower(contact0_.firstName) like lower((?||'%'))
order by
contact0_.lastName
Hibernate:
select
top ? contact0_.id as id4_,
contact0_.address as address4_,
contact0_.businessPhone as business3_4_,
contact0_.cellPhone as cellPhone4_,
contact0_.city as city4_,
contact0_.country as country4_,
contact0_.firstName as firstName4_,
contact0_.homePhone as homePhone4_,
contact0_.lastName as lastName4_,
contact0_.state as state4_,
contact0_.version as version4_,
contact0_.zip as zip4_
from
Contact contact0_
where
lower(contact0_.firstName) like lower((?||'%'))
order by
contact0_.lastName
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 5 months