March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2544) Exception handling for javax.persistence.OptimisticLockException fails the second time

by Christian Bauer (JIRA)

Exception handling for javax.persistence.OptimisticLockException fails the second time -------------------------------------------------------------------------------------- Key: JBSEAM-2544 URL: http://jira.jboss.com/jira/browse/JBSEAM-2544 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR2 Reporter: Christian Bauer Priority: Blocker Install the wiki, run it in dev profile. <exception class="javax.persistence.OptimisticLockException"> <end-conversation/>  <redirect view-id="/message.xhtml"> <message severity="WARN">#{messages['lacewiki.msg.OptimisticLockError']}</message> </redirect> </exception> Generate this exception by editing directory 'BBB' in two browser tabs, click Update in one of them, then click Update in the other. If you are lucky, you will now be on the message page with a proper error message. If you don't have a message, that's the bug. If you get a message, try again and repeat the concurrent update procedure. It will fail at some point, I needed no more than three attempts. Occasionally I get this exception (always doing the same clicks!): javax.el.ELException: /message.xhtml: Property 'handledException' not found on type org.jboss.seam.Namespace com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) Once you get that exception, it will never work again and you will always get this exception (I think). There are several open issues related to exception handling and message passing, this probably duplicates them. My guess is that we have a serious race condition somewhere in the exception handling code. -- 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

18 years

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2803) In specific cases, a closed entitymanager is injected by seam, resulting in illegalstateexceptions

by Indrek Altpere (JIRA)

In specific cases, a closed entitymanager is injected by seam, resulting in illegalstateexceptions -------------------------------------------------------------------------------------------------- Key: JBSEAM-2803 URL: http://jira.jboss.com/jira/browse/JBSEAM-2803 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.0.A1 Environment: Glassfish v2ur1, Icefaces 1.7.0 Reporter: Indrek Altpere EntityManager is put to event Scope for better memory usage and GC. Class that tries to use the entitymanager is itself in conversation scope, and this specific behavior occurs after icefaces file upload. Injected em is closed and throws IllegalStateException for every function used (as it should when it's closed). I dug around the persistence namespace/package and found once place that could explain it. src/main/org/jboss/seam/persistence/ManagedPersistenceContext.java line 225 to 229 if (entityManager!=null) { entityManager.close(); } As seen, entityManager is closed but since getEntityManager() function only creates new entitymanager when entityMAnager is null and does not check for entityManager being closed, the closed entitymanager gets passed around. I added entityManager = null; after the entityManager.close(); line so that the getEntityManager() would correctly return new entitymanager after old one was closed and recompiled the latest sources. It seemed to fix this issue, no more errors, em injected to the conversation scope class is not closed one anymore :) There may be some other things related to this like JBSEAM-2666 but I'm not entirely sure about it. -- 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

18 years

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2606) Natural conversation id already in use in seam-bay example

by Jacob Orshalick (JIRA)

Natural conversation id already in use in seam-bay example ---------------------------------------------------------- Key: JBSEAM-2606 URL: http://jira.jboss.com/jira/browse/JBSEAM-2606 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Jacob Orshalick In the seam-bay example if you view the itemdetail page, then select "Place Bid" a natural conversation is started. Using the back button to return to itemdetail and once again selecting "Place Bid" results in: java.lang.IllegalStateException: Conversation id is already in use: PlaceBid:<item-id> This has been noted in the latest from the trunk. This may be the same issue as JBSEAM-2124. I have also written an application that demonstrates the same issue. -- 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

18 years

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2583) <s:conversationPropagation type="join" /> seems not creating aq new conversation

by Tomas Cerny (JIRA)

<s:conversationPropagation type="join" /> seems not creating aq new conversation -------------------------------------------------------------------------------- Key: JBSEAM-2583 URL: http://jira.jboss.com/jira/browse/JBSEAM-2583 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Environment: Linux, FireFox Reporter: Tomas Cerny Priority: Minor Fix For: 2.0.2.GA Assuming you will take a look in JBoss Forum Reference I have a search table and from table entry starting new explicit conversation (natural). My conversationName is defined in pages.xml when I use <h:commandLink styleClass="left clearBoth" action="#{teamManager.select(teamItem)}" value="select"> <s:conversationName value="teamHome"/> <s:conversationPropagation type="join" /> </h:commandLink> link invokes method but is not redirecting to entryHome (should start pageFlow defined on method) if I will remove <s:conversationPropagation type="join" /> then redirection to entryHome works but of course without joining. -- 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

18 years

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2802) Websphere: unable to inject EntityManager into non-EJBs

by Eric Jung (JIRA)

Websphere: unable to inject EntityManager into non-EJBs ------------------------------------------------------- Key: JBSEAM-2802 URL: http://jira.jboss.com/jira/browse/JBSEAM-2802 Project: JBoss Seam Issue Type: Patch Components: EJB3 Environment: Websphere 6.1 with EJB Feature Pack Reporter: Eric Jung Seam currently is unable to inject EntityManager instances into non-EJB components. Patch attached. -- 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

18 years

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2800) Upgrade to Drools 4.0.5

by Pete Muir (JIRA)

Upgrade to Drools 4.0.5 ----------------------- Key: JBSEAM-2800 URL: http://jira.jboss.com/jira/browse/JBSEAM-2800 Project: JBoss Seam Issue Type: Task Components: Drools Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.2.CR1, 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

18 years

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2801) Add a getConvertedRequestParameter method to the Parameters class

by Sylvain Leroux (JIRA)

Add a getConvertedRequestParameter method to the Parameters class ----------------------------------------------------------------- Key: JBSEAM-2801 URL: http://jira.jboss.com/jira/browse/JBSEAM-2801 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: any Reporter: Sylvain Leroux The current implementation of the Parameters class require two method calls to retrieve a request parameter. First you need to obtain the request parameters, then to convert the one you want to use: Map<String,String[]> paramMap = parameters.getRequestParameters(); int my_value parameters.convertMultiValueRequestParameter(paramMap, "my_param", Integer.class); It would be more natural to have a getConvertedRequestParameter(String name, Class<?> type) method. This is especially useful to access a request parameter from an EL expression in a jPDL action. -- 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

18 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2796) Detailed Seam messages don't work

by Jens Weintraut (JIRA)

Detailed Seam messages don't work --------------------------------- Key: JBSEAM-2796 URL: http://jira.jboss.com/jira/browse/JBSEAM-2796 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Environment: WinXP SP2, JBoss 4.2.2, ICEfaces 1.7.0 RC1 Reporter: Jens Weintraut I want to i18nize some Seam messages (e. g. org.jboss.seam.loginSuccessful). It works quite well, but there's one problem: I use just one h:messages to display messages with detail=true. But it seems that Seam doesn't follow JSF specs. I think so because this: org.jboss.seam.loginSuccessful=Welcome, #{user.name}. org.jboss.seam.loginSuccessful_detail=bla results in Welcome, <Name>.Welcome, <Name>.. So Seam should also take note of _detail when reading its own messages. -- 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

18 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2559) Create an LDAP Identity Store for Identity Management

by Shane Bryzak (JIRA)

Create an LDAP Identity Store for Identity Management ----------------------------------------------------- Key: JBSEAM-2559 URL: http://jira.jboss.com/jira/browse/JBSEAM-2559 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.1.0.GA We need one of these, as many people store their users and roles in LDAP. We should ensure that it works with Red Hat Directory Server (http://www.redhat.com/directory_server/) and OpenLDAP. -- 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

18 years

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2029) Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml

by Pete Muir (JIRA)

Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml ------------------------------------------------------------------------------------ Key: JBSEAM-2029 URL: http://jira.jboss.com/jira/browse/JBSEAM-2029 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Shane Bryzak Fix For: 2.0.1.GA Entity.forClass() isn't a great way to determine the entity's Class and should be done through PersistenceProvider -- 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

18 years

4
24
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 March 2008