August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3343) Bijection problem when page is deserialized from PageStore

by Marcell Barbacena (JIRA)

Bijection problem when page is deserialized from PageStore ---------------------------------------------------------- Key: JBSEAM-3343 URL: https://jira.jboss.org/jira/browse/JBSEAM-3343 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.0.BETA1 Environment: Windows, JBoss 4.2.2 Reporter: Marcell Barbacena I am receiving the following stacktrace when I double click in a link (from the stacktrace I am seeing it is trying to deserialize a page and I think that is because of the second click going to the same page as the first click): java.lang.ClassCastException: cannot assign instance of org.jboss.seam.wicket.ioc.WicketHandler to field br.gov.tse.secad.elo.web.CustomerList$1.handler of type org.jboss.seam.wicket.ioc.WicketHandler in instance of br.gov.tse.secad.elo.web.CustomerList$1 at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2032) at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:393) at org.apache.wicket.protocol.http.pagestore.AbstractPageStore.deserializePage(AbstractPageStore.java:228) at org.apache.wicket.protocol.http.pagestore.DiskPageStore.getPage(DiskPageStore.java:706) at org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get(SecondLevelCacheSessionStore.java:311) at org.apache.wicket.Session.getPage(Session.java:751) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:448) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1224) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1331) at org.apache.wicket.RequestCycle.request(RequestCycle.java:493) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:363) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194) at org.jboss.seam.web.WicketFilter$1.process(WicketFilter.java:57) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.web.WicketFilter.doFilter(WicketFilter.java:52) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) -- 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, 6 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1277) ServerConversationContext does not process removals / additions when an exception propagates up

by Chris Rudd (JIRA)

ServerConversationContext does not process removals / additions when an exception propagates up ----------------------------------------------------------------------------------------------- Key: JBSEAM-1277 URL: http://jira.jboss.com/jira/browse/JBSEAM-1277 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Reporter: Chris Rudd I have an Stateful EJB Component that throws an exception (this is expected, im testing that the system can recover from that error). This causes the component to be removed from the seam contexts (via the RemoveInterceptor). Then the exception floats up and is caught by the ExceptionFilter, and is redirected to a new view. All that works correctly. BUT when I return to the conversation that contained the EJB component, the component is still in it (even though the RemoveInterceptor removed it). Ive traced it down to this : ServerConversationContext.remove -- this adds the removal to the removals list, but does not update the session.attributes (the real storage for the context). ServerConversationContext.flush -- this applies the removals / additions to the session attributes map. The problem is that flush is never called when an exception propagates out. Thus the changes to that context are never flushed to the session attributes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3315) seamspace example does not validate permission settings

by Jay Balunas (JIRA)

seamspace example does not validate permission settings -------------------------------------------------------- Key: JBSEAM-3315 URL: https://jira.jboss.org/jira/browse/JBSEAM-3315 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Shane Bryzak Priority: Minor Fix For: 2.1.0.BETA2 minor comments: seamspace example does not validate permission settings. This means that you can set "comment" permission, but not "view" permissions. This results in users not able to see the image ;-) Also you don't have to set view or comment and it will just not create the permission when you submit - it should probably have an invalid config message. -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1902) Cannot use Seam EntitySecurityListener and MDBs

by Mike Pettypiece (JIRA)

Cannot use Seam EntitySecurityListener and MDBs ----------------------------------------------- Key: JBSEAM-1902 URL: http://jira.jboss.com/jira/browse/JBSEAM-1902 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.0.BETA1 Reporter: Mike Pettypiece After turning on Seam's EntitySecurityListener, the follow exception occurs when working with a @Restrict-annotated entity from a MDB. java.lang.IllegalStateException: No active session context at org.jboss.seam.security.Identity.instance(Identity.java:157) at org.jboss.seam.security.EntitySecurityListener.postLoad(EntitySecurityListener.java:26) ... There obviously isn't a session context in this case. Seam probably shouldn't check security permissions when there is no active session context. As well it would be useful to be able to programatically turn off security on a per-Identity basis. Please see the referenced Forum link for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2992) Wicket-Seam integration doesn't propagate the temporary conversation across a redirect

by Pete Muir (JIRA)

Wicket-Seam integration doesn't propagate the temporary conversation across a redirect -------------------------------------------------------------------------------------- Key: JBSEAM-2992 URL: http://jira.jboss.com/jira/browse/JBSEAM-2992 Project: Seam Issue Type: Bug Components: Wicket Affects Versions: 2.1.0.A1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3191) Upgrade to jBPM 3.2.3

by Pete Muir (JIRA)

Upgrade to jBPM 3.2.3 --------------------- Key: JBSEAM-3191 URL: https://jira.jboss.org/jira/browse/JBSEAM-3191 Project: Seam Issue Type: Task Components: BPM Reporter: Pete Muir Fix For: 2.0.3.CR2, 2.1.0.BETA1 -- 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, 6 months

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2469) add postback flag to page actions

by Dan Allen (JIRA)

add postback flag to page actions --------------------------------- Key: JBSEAM-2469 URL: http://jira.jboss.com/jira/browse/JBSEAM-2469 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.x Page actions are incredibly useful, but sometimes they can get in the way during a postback. I would like to see a postback attribute added to the <action> tag that can be used to disable the action on postback. It's possible using a conditional, but it is ugly and a lot of typing. Here is the logic that would go into Pages.java private boolean isPostBack(FacesContext facesContext) { return facesContext.getExternalContext().getRequestParameterMap(). containsKey(ResponseStateManager.VIEW_STATE_PARAM); } The conditional alternative would be: <action execute="#{component.action}" if="#{empty param['javax.faces.ViewState']}"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

5
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2348) seam generate-ui fails for @OneToOne @PrimaryKeyJoinColumn annotated fields

by Thorsten Kunz (JIRA)

seam generate-ui fails for @OneToOne @PrimaryKeyJoinColumn annotated fields --------------------------------------------------------------------------- Key: JBSEAM-2348 URL: http://jira.jboss.com/jira/browse/JBSEAM-2348 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Environment: Seam 2.0.0.GA JBoss Tools Reporter: Thorsten Kunz Since I do use JBoss Tool I assume that this is cause by an error in the underlying seam generate-ui. It fails if you have entities annotated like this: public class User implements Serializable { @Id @GeneratedValue private Long id; @OneToOne @PrimaryKeyJoinColumn private UserData userData; } public class UserData implements Serializable { @Id private Long id; @OneToOne @PrimaryKeyJoinColumn private User user; } This will result in this Exception: org.eclipse.core.runtime.CoreException: org.hibernate.tool.hbm2x.ExporterException: Error while processing template view/list.xhtml.ftl org.eclipse.core.runtime.CoreException[666]: org.hibernate.tool.hbm2x.ExporterException: Error while processing template view/list.xhtml.ftl Caused by: freemarker.core.InvalidReferenceException: Expression property.value.typeName is undefined on line 39, column 6 in view/list.xhtml.ftl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1943) Support for destroying the entire ConversationStack

by Jacob Orshalick (JIRA)

Support for destroying the entire ConversationStack --------------------------------------------------- Key: JBSEAM-1943 URL: http://jira.jboss.com/jira/browse/JBSEAM-1943 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Jacob Orshalick There are situations where I would like to be able to destroy the entire conversation stack if a particular action occurs (say a user cancels everything during a nested conversation, an exception occurs during a nested conversation, etc). I am currently accomplishing this through the following: private void endRootConversation() { Conversation conversation = Conversation.instance(); while(conversation.isNested()) { conversation.root(); } conversation.endBeforeRedirect(); } I would prefer to say something like @End(root=true) or specifying conversationPropogation="endRoot". Similar discussions on the forum are: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112414&postdays=... http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118936&postdays=... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

4
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3088) Allow supported locales to be configured in the component descriptor

by Dan Allen (JIRA)

Allow supported locales to be configured in the component descriptor -------------------------------------------------------------------- Key: JBSEAM-3088 URL: http://jira.jboss.com/jira/browse/JBSEAM-3088 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.1.0.GA Just about the only setting that we still need to configure in faces-config.xml is the collection of supported locales. The Application class in the JSF API exposes the public method setSupportedLocales(Collection) to configure this collection. The support this feature request, a new application-scoped component will need to be created in the international package. The LocaleSelector cannot be used since it is per user session. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008