August 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4336) Seamspace example - InvalidStateException at friend request

by Jozef Hartinger (JIRA)

Seamspace example - InvalidStateException at friend request ----------------------------------------------------------- Key: JBSEAM-4336 URL: https://jira.jboss.org/jira/browse/JBSEAM-4336 Project: Seam Issue Type: Bug Components: Examples Environment: JDK 5, 6 JBoss AS 4.2.3 Reporter: Jozef Hartinger Fix For: 2.2.1.CR1 I am getting InvalidStateException when trying to submit an introduction message at friend request. -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1572) Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly)

by Alex Savitsky (JIRA)

Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly) --------------------------------------------------------------------------- Key: JBSEAM-1572 URL: http://jira.jboss.com/jira/browse/JBSEAM-1572 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Alex Savitsky Priority: Minor ui:decorate preserves its children, while s:decorate groups them as one instead. This makes s:decorate unusable for form fields laid out using h:panelGrid, as there's no way to separate the field label from the field itself (they are grouped together). -- 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

15 years, 4 months

9
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3710) For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate

by Pete Muir (JIRA)

For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate ----------------------------------------------------------------------------------- Key: JBSEAM-3710 URL: https://jira.jboss.org/jira/browse/JBSEAM-3710 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 This is possible only in JavaBeans as the HttpSession is passed as an arguement to the sessionWillPassivate/sessionWillActivate call, and we can store the conversationId in @AroundInvoke method. In EJBs, the passivation/activation happens independently of the HttpSession. This should be a performance improvement, @PrePassivate (serialize out entities) will be called just as much, but @PostActivate will be called a lot less. -- 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

15 years, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2093) Optimize getting Id in Seam code for better performance

by Mikhail Grushinskiy (JIRA)

Optimize getting Id in Seam code for better performance ------------------------------------------------------- Key: JBSEAM-2093 URL: http://jira.jboss.com/jira/browse/JBSEAM-2093 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy This sequence of calls (used in PersistenceProvider) is quite slow Entity.forClass(bean.getClass()).getIdentifier(bean); 1) Entity.forClass() is reading annotations using JDK 5 methods (JDK 5 annotation reading is not that fast). Can it be cached? 2) JDK 5 reflection is used to get bean id (which is slower than optmized reflection with cglib) 3) There could be other reasons as well. I think repetitive calling of this sequence under profiler will give better picture. from PersistenceProvider.java /** * Get the value of the entity identifier attribute. * * @param bean a managed entity instance */ public Object getId(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getIdentifier(bean); } /** * Get the name of the entity * * @param bean * @param entityManager */ public String getName(Object bean, EntityManager entityManager) { return Entity.forClass(bean.getClass()).getName(); } /** * Get the value of the entity version attribute. * * @param bean a managed entity instance */ public Object getVersion(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getVersion(bean); } -- 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

15 years, 4 months

7
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4290) jboss-el.jar version in MANIFEST.MF doesn't correspond with real version in maven repo - it applies for 1.0_02.CR3 and 1.0_02.CR4

by Marek Novotny (JIRA)

jboss-el.jar version in MANIFEST.MF doesn't correspond with real version in maven repo - it applies for 1.0_02.CR3 and 1.0_02.CR4 ---------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4290 URL: https://jira.jboss.org/jira/browse/JBSEAM-4290 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.1.2.CR2, 2.1.2.CR1 Reporter: Marek Novotny Priority: Minor jboss-el.jar contains MANIFEST.MF file with version information 1.0_02.CR2. It is deployed in http://repository.jboss.org/maven2/org/jboss/el/jboss-el/ and this version information is in 1.0_02.CR3 and 1.0_02.CR4 versions instead of correct versions. -- 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

15 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4243) resteasy-2.1.xsd in jboss-seam-resteasy.jar and resteasy-2.1.xsd at http://jboss.com/products/seam/resteasy-2.1.xsd are not the same

by Matthew Bowman (JIRA)

resteasy-2.1.xsd in jboss-seam-resteasy.jar and resteasy-2.1.xsd at http://jboss.com/products/seam/resteasy-2.1.xsd are not the same ------------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-4243 URL: https://jira.jboss.org/jira/browse/JBSEAM-4243 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Matthew Bowman Attachments: resteasy-2.1.xsd.patch The new Seam RESTeasy integration documentation shows how to add the resteasy namespace to components.xml and how to enable the session context for REST requests: <resteasy:application destroy-session-after-request="false" /> The resteasy-2.1.xsd schema located at http://jboss.com/products/seam/resteasy-2.1.xsd seems out-of-date when compared to the resteasy-2.1.xsd contained in the jboss-seam-resteasy.jar integration library. -- 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

15 years, 4 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4335) support "with" in dynamic restrictions

by Daniel Tomsu (JIRA)

support "with" in dynamic restrictions -------------------------------------- Key: JBSEAM-4335 URL: https://jira.jboss.org/jira/browse/JBSEAM-4335 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.2.0.GA Reporter: Daniel Tomsu Priority: Minor I would like the org.jboss.seam.framework.EntityQuery to understand WITH as a restriction, right now only where is correctly understood. This will lead to problems with outer joins where a constraint can not be expressed in a where clause. For example my EJBQL is: select new entity.combined.EmployeePerformance(employee, performance) from Employee as employee left outer join employee.performances as performance my restrictions are: with performance.process=#{processManager.currentProcess} where (employee.id in (#{sessionView.employeeIds}) In my opinion there should be two restriction categories with and where, which both allow EL expressions. My quick fix was to form a dynamic EJBQL, dependent on the processManager, which concats to the EJBQL the desired with expression. -- 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

15 years, 4 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4332) HTTP sessions expiration cause a "javax.naming.ConfigurationException" while trying to "Destroy" the EntityManager components in WebSphere

by Denis Forveille (JIRA)

HTTP sessions expiration cause a "javax.naming.ConfigurationException" while trying to "Destroy" the EntityManager components in WebSphere ------------------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-4332 URL: https://jira.jboss.org/jira/browse/JBSEAM-4332 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: Seam 2.2.0 GA, WebSphere 7.0.0.5 Reporter: Denis Forveille Assignee: Denis Forveille Fix For: 2.2.1.CR1 In WebSphere when the HTTP user session expires, the Seam session listener intercepts the event and try to clean all the pending components A call to the method annotated "@Destroy" is called on EntityManager (ie method close()) This methods checks if there is an active Transaction to throw an exception in case there is an active transaction. For this it performs a JNDI lookup on java:comp/env/UserTransaction In this context, the lookup fails with a javax.naming.ConfigurationException in WebSphere because it is illegal to do such operation in such a thread (The one spawned by WebSphere to timeout the session) and the EntityManager is never closed and the whole clean process fails.. This can be corrected by intercepting the exception in the ManagedPersistenceContext.close() method and continue with the close operation on the EntityManager -- 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

15 years, 4 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4174) Seam Conversation Issue with richmenu

by Tony Herstell (JIRA)

Seam Conversation Issue with richmenu ------------------------------------- Key: JBSEAM-4174 URL: https://jira.jboss.org/jira/browse/JBSEAM-4174 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.2.CR1 Environment: Win XP64 Pro, Ubuntu Reporter: Tony Herstell http://www.jboss.org/index.html?module=bb&op=viewtopic&t=149397 http://www.seamframework.org/Community/ConversationQuestion http://www.seamframework.org/Community/ProblemEndingConversationInRichFac... http://www.seamframework.org/Community/HowToUseSlinkInRichmenuItem ------ In Summary RF know of the problem but, I believe, are looking to seam to fix this... <rich:menuItem submitMode="ajax" value="#{messages.menu_button_facilities}" action="#{facilitiesController.enter}" > <s:conversationPropagation type="none"/> </rich:menuItem> Basically the above code should work but doesn't. Seam/RF do not honour the conversationPropagation Tag... so the current conversation is not suspended.. thus when you try to start the new conversation (from the menu click you just did) BANG!. The error you get is: The conversation ended, timed out or was processing another request The live site to see this is: http://www.selwynequestriancentre.co.nz/site/home.seam click register then click the menu for "home page" which goes from a conversation to a non-conversation click to enter a competition (actually all closed at present but should be open again next week) and then click to register to go from conversation to another conversation. -- 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

15 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2009