July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3838) Permission check fails on collections that contain lazily initialized entities

by Georges Berscheid (JIRA)

Permission check fails on collections that contain lazily initialized entities ------------------------------------------------------------------------------ Key: JBSEAM-3838 URL: https://jira.jboss.org/jira/browse/JBSEAM-3838 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.SP1 Reporter: Georges Berscheid org.jboss.seam.security.permission.PermissionMapper.filterByPermission:94 The permission filter checks if the target of the check is of the same class as the target of the permission. If the collection-parameter is the result of a javax.persistence.Query.getResultList() (using Hibernate), and one of the entities returned in that List had previously been lazily fetched (e.g. as part of an entity relationship) this check will fail. Hibernate probably does some optimization and knows that it had fetched this entity before, and hence puts the lazy proxy into the result list. The proxy's class name is something like Entity_$$_javassist_12 which won't match the class name of the permission target (Entity). The only work-around I could find for this is to eagerly fetch all entity relationships that are affected by this behavior, which kills the performance of the application. -- 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

14 years, 11 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3778) MDB - IllegalStateException: No event context active

by John Gilbert (JIRA)

MDB - IllegalStateException: No event context active ---------------------------------------------------- Key: JBSEAM-3778 URL: https://jira.jboss.org/jira/browse/JBSEAM-3778 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.GA Reporter: John Gilbert ManagedPersistenceContext throws "IllegalStateException: No event context active" after MDB closes contexts. see - http://seamframework.org/Community/MDBIllegalStateExceptionNoEventContext... -- 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

14 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1246) pages.xml fails to load during application startup

by Mike Quilleash (JIRA)

pages.xml fails to load during application startup -------------------------------------------------- Key: JBSEAM-1246 URL: http://jira.jboss.com/jira/browse/JBSEAM-1246 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash pages.xml will not be found by the resource loader when the Pages component is @Created during startup ie outside a JSF request. One of my components that queries the Pages component is causing the component to be created and look for its pages outside a JSF request. The only resource lookup that can succeed for something in WEB-INF is the ExternalContext.getResource() but this is not available outside a JSF request. Using ServletContext.getResource() will work instead however this is not portable to Portlets etc. -- 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

14 years, 11 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4048) Upgrade Seam to use RichFaces 3.3.1

by Jay Balunas (JIRA)

Upgrade Seam to use RichFaces 3.3.1 ----------------------------------- Key: JBSEAM-4048 URL: https://jira.jboss.org/jira/browse/JBSEAM-4048 Project: Seam Issue Type: Task Components: Build Reporter: Jay Balunas RichFaces 3.3.1 is scheduled for May 4th. -- 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

14 years, 11 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3752) Allow to kill all conversation with the "s:conversationPropagation" tag

by Denis Forveille (JIRA)

Allow to kill all conversation with the "s:conversationPropagation" tag ------------------------------------------------------------------------ Key: JBSEAM-3752 URL: https://jira.jboss.org/jira/browse/JBSEAM-3752 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.CR1 Reporter: Denis Forveille Add the possibility to kill the conversation stack with the "s:conversationPropagation" is missing. It is possible to do that with annotation (@End(root=true),via the API or with pages.xml, but not with the "s:conversationPropagation" annotation maybe with <s:conversationPropagation type="endAll" /> ? -- 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

14 years, 11 months

5
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4087) Regexp Query.SUBJECT_PATTERN may be improved for JBSEAM-3032

by Julien Kronegg (JIRA)

Regexp Query.SUBJECT_PATTERN may be improved for JBSEAM-3032 ------------------------------------------------------------ Key: JBSEAM-4087 URL: https://jira.jboss.org/jira/browse/JBSEAM-4087 Project: Seam Issue Type: Quality Risk Components: Framework Environment: https://jira.jboss.org/jira/browse/JBSEAM-3032 http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/framew... Reporter: Julien Kronegg The regexp Pattern Query.SUBJECT_PATTERN has been added for JBSEAM-3032: private static final Pattern SUBJECT_PATTERN = Pattern.compile("^select (\\w+((\\s+|\\.)\\w+)*)\\s+from", Pattern.CASE_INSENSITIVE); This pattern should be improved because it will not match queries such as: select vehicle1.person from Vehicle vehicle1 select vehicle2.person, vehicle2.color from Vehicle vehicle2 select vehicle3.person from Vehicle vehicle3 where vehicle3.id in (select c.id from Cars c) select vehicle4 . person from Vehicle vehicle4 The following pattern will accept all of the above queries: Pattern.compile("^select\\s+(\\w+(?:\\s*\\.\\s*\\w+)*?)(?:\\s*,\\s*(\\w+(?:\\s*\\.\\s*\\w+)*?))*?\\s+from", Pattern.CASE_INSENSITIVE); The test case http://fisheye.jboss.org/browse/Seam/trunk/src/test/unit/org/jboss/seam/t... should also be completed by the queries above. Notes: - the priority has been set the same JBSEAM-3032 - the original pattern matches in about 300 ns while the proposed pattern matches in 2300 ns -- 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

14 years, 11 months

6
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1563) create "bin" distribution

by Dan Allen (JIRA)

create "bin" distribution ------------------------- Key: JBSEAM-1563 URL: http://jira.jboss.com/jira/browse/JBSEAM-1563 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA Reporter: Dan Allen The current releases of Seam are ridiculously large, weighing in at around 80MB. That is almost as big as the JBoss AS download! While it is critical to offer the entire bundle for Seam developers, contributors, and source builders, I think it would be appropriate to offer a "bin" distribution that is intended just to run Seam. Perhaps just spin off seam-gen as its own download. That should give people exactly what they need to run Seam, and nothing more. Below is a comparison table of some competing projects: Spring Framework: 10MB (2.6MB if you pull it from the maven repository) Ruby on Rails: 2.2 MB (standalone version) I remember when I first discovered Seam, I put off trying it out because it was too hefty of a download. Let's make it more attractive. -- 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

14 years, 11 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1557) Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle

by Neil Griffin (JIRA)

Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle -------------------------------------------------------------------------------------------------- Key: JBSEAM-1557 URL: http://jira.jboss.com/jira/browse/JBSEAM-1557 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: WinXP / Liferay 4.3.0 / Tomcat 6.0.13 Reporter: Neil Griffin Background: I found this problem when attempting to package the Seam "Registration" example as a portlet under Liferay Portal. Section 7.4.2 of the JSF 1.1 specifcation says that since redirects are not possible in the case of portlets. Nevertheless, the Seam Conversation Manager (Manager.java) is forcing the portal to redirect outside its portal pages, rather than use the portlet lifecycle. The way this would be manifested to the user would be like this: If a Seam application was contained within a portlet, and the portlet were placed on a portal page, then when the user clicks on a button that invokes navigation to a different JSF view, then the Seam application would "jump out" (so to speak) of the rectangular portlet container, and become a full-browser-page thing. This is incorrect. If a Seam application starts out as a portlet, then it must remain a portlet for its entire lifespan. In addition, the current behavior of Seam is not conforming to section 7.4.2 of the JSF 1.1. specification. Now, it might be the case that this redirect works under JBoss Portal, but it causes exceptions to be thrown under Liferay Portal. This is because Liferay Portal expects JSF-based portlets to not perform redirects, as they must not do that anyway. -- 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

14 years, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1554) Validation message obtainable by EL within <s:decorate /> tag

by Slawomir Trybus (JIRA)

Validation message obtainable by EL within <s:decorate /> tag ------------------------------------------------------------- Key: JBSEAM-1554 URL: http://jira.jboss.com/jira/browse/JBSEAM-1554 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.3.0.BETA1 Reporter: Slawomir Trybus It would be very useful to have #{invalidMessage} available inside <s:decorate /> tag. -- 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

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1525) Add the EJB @Remove like functionality for POJO components.

by Chris Rudd (JIRA)

Add the EJB @Remove like functionality for POJO components. ----------------------------------------------------------- Key: JBSEAM-1525 URL: http://jira.jboss.com/jira/browse/JBSEAM-1525 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd Currnrntly Statefull EJBs can be removed from the Seam context when an @Remove method is called. This functionality would be helpful for Pojo components as well. -- 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

14 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009