November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1973) Serialization error on FullTextEntityManagerImpl

by Norman Richards (JIRA)

Serialization error on FullTextEntityManagerImpl ------------------------------------------------ Key: JBSEAM-1973 URL: http://jira.jboss.com/jira/browse/JBSEAM-1973 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Fix For: 2.0.0.CR2 We're seeing serialization issues with hibernate search sessions: 3:59:22,080 WARN [Component] Exception calling component @Destroy method: categories java.lang.RuntimeException: org.jboss.serial.exception.SerializationException: Could not create instance of org.hibernate.search.jpa.impl.FullTextEntityManagerImpl - org.hibernate.search.jpa.impl.FullTextEntityManagerImpl See the forums posting for full stack trace. I noticed this exception today while testing on tomcat. -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4490) Messages: AbstractMap needs containsKey

by Dieter Rehbein (JIRA)

Messages: AbstractMap needs containsKey --------------------------------------- Key: JBSEAM-4490 URL: https://jira.jboss.org/jira/browse/JBSEAM-4490 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: Dieter Rehbein This seems to be a regression issue and was already fixed some time ago (see JBSEAM-2192): Component Message createMap() returns an AbstractMap without a containsKey() implementation, which leads to poor performance! -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4489) Allow <exception/> in *.page.xml

by Chris Bredesen (JIRA)

Allow <exception/> in *.page.xml -------------------------------- Key: JBSEAM-4489 URL: https://jira.jboss.org/jira/browse/JBSEAM-4489 Project: Seam Issue Type: Feature Request Reporter: Chris Bredesen Priority: Minor Seems logical to include <exception/> in the subset of elements allowed in *.page.xml navigation rule fragments. Struts, for example, allows both global exception handlers (here equivalent to pages.xml) and mapping-level handlers (missing in Seam). -- 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, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3541) Translation of the Annotations.po file in french

by Michael Courcy (JIRA)

Translation of the Annotations.po file in french ------------------------------------------------ Key: JBSEAM-3541 URL: https://jira.jboss.org/jira/browse/JBSEAM-3541 Project: Seam Issue Type: Feature Request Components: Documentation Translation Affects Versions: The future Reporter: Michael Courcy Priority: Optional Fix For: The future Attachments: Annotations.diff Translation of the Annotations.po file in french in the diff format. -- 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, 1 month

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

by Jay Balunas (JIRA)

Multiple WAR in EAR verification, example, and document ------------------------------------------------------- Key: JBSEAM-3119 URL: http://jira.jboss.com/jira/browse/JBSEAM-3119 Project: Seam Issue Type: Feature Request Components: Documentation Issues, Examples, Platform interoperability Affects Versions: 2.1.0.A1 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.1.0.GA Create an example of two seam WAR applications inside of an EAR. There has been quite a bit of forum traffic on the subject and it would be good to nail down an example and document. There may also be errors and other issue that need to be worked out. An admin console type application to the standard booking application may be a good way to go. It would be a real world/useful example. -- 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, 1 month

16
61
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4486) Seam with ICEFaces double urlencoding of non-ascii characters

by Arturo FrappÃ© (JIRA)

Seam with ICEFaces double urlencoding of non-ascii characters ------------------------------------------------------------- Key: JBSEAM-4486 URL: https://jira.jboss.org/jira/browse/JBSEAM-4486 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: Weblogic 10.31 or JBoss 5.1 / Icefaces 1.8.2 Reporter: Arturo FrappÃ© Priority: Critical When doing a post-back redirect if a field has a non -ascii character it gets urlencoded twice by the effect of org.jboss.seam.core.Manager::encodeParameters and com.icesoft.faces.context.BridgeExternalContext:redirect then the data returns with an urlencoded characters. -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4485) Wrong behavior with org.jboss.seam.preDestroyContext.SESSION event

by Andre Salvati (JIRA)

Wrong behavior with org.jboss.seam.preDestroyContext.SESSION event ------------------------------------------------------------------- Key: JBSEAM-4485 URL: https://jira.jboss.org/jira/browse/JBSEAM-4485 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: Running on JBoss 4.2.3 with Richfaces 3.3.1 GA Reporter: Andre Salvati http://seamframework.org/Community/OrgjbossseampreDestroyContextSESSIONIssue -- 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, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4481) Failed to find the component with the GWT integration.

by Ameeth Paatil (JIRA)

Failed to find the component with the GWT integration. ------------------------------------------------------ Key: JBSEAM-4481 URL: https://jira.jboss.org/jira/browse/JBSEAM-4481 Project: Seam Issue Type: Bug Components: GWT Affects Versions: 2.2.0.GA Environment: Windows Reporter: Ameeth Paatil Priority: Minor Issue found in the GWTService class method RPC_invokeAndEncodeResponse. The method finds the incorrect interface name with the at the line. String serviceIntfName = serviceMethod.getDeclaringClass().getName(); This happens in the below scenario. 1. Create base service interface say X.java which has method sayHello(). 2. Create two other serviceInterfaces Y.java and Z.java which extends the X.java. 3. Create two seam components for these interfaces. then when you do remote method invocation for "sayHello" for the Y or Z interface it will try to search the component with interface name X insted it should have bean called for the Y or Z. depending on the service method invoked. The solution to this may be include the method name as well as interface name in SeamRPCRequest and do not use the interface name from the method object as it's returning the base interface. -- 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, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4480) Sometimes JSF lifecycle not completing which leaves conversation in locked state causing concurrent conversation error

by Ross Mills (JIRA)

Sometimes JSF lifecycle not completing which leaves conversation in locked state causing concurrent conversation error ---------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4480 URL: https://jira.jboss.org/jira/browse/JBSEAM-4480 Project: Seam Issue Type: Bug Components: Core, JSF Integration Affects Versions: 2.2.0.GA Environment: Linux Reporter: Ross Mills I have an Seam app that has a left menu on every page. When the user selects an item from the menu, it ends the current conversation and starts a new one. However, once in a while, I get a concurrent conversation exception. I have an automated test that does the following: (1) Logs the user in. (2) 10 seconds later, the user selects an item from the left hand menu (which ends the current conversation and begins a new one). This causes a seach form to appear. (3) 10 seconds later, the user fills in the form and submits. The search results are displayed. (4) 10 seconds later, the user navigates through the search results and drills down. (5) 10 seconds later, the user returns to step (2) by selecting the same item from the left hand menu and repeats the above steps. The user is able to cycle through these steps anywhere from a few seconds to several minutes until the concurrent conversation error occurs. When the error occurs, it is when the user attempts to submit the search form. The logs indicate that when the search form is displayed, the JSF lifecycle is not progressing beyond the RESTORE_VIEW phase. This causes the conversation to remain locked. Then when the user attempts to submit the form, the new thread finds the conversation locked and generated the concurrent conversation exception. My company policy may not allow me to provide you with code that you can use to duplicate the problem. But snippets of the logs can be found in the JBoss forum reference I am including. -- 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, 2 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4393) seam-gen produces wrong persistence unit configuration for unit tests

by Christian Bauer (JIRA)

seam-gen produces wrong persistence unit configuration for unit tests --------------------------------------------------------------------- Key: JBSEAM-4393 URL: https://jira.jboss.org/jira/browse/JBSEAM-4393 Project: Seam Issue Type: Bug Reporter: Christian Bauer Assignee: Dan Allen I've just generated a seam-gen project from 2.2 head and added a unit test. The test setup is wrong in build.xml: <target name="buildtest" depends="init,compiletest,copytestclasses" description="Build the tests"> <copy todir="${test.dir}"> <fileset dir="${basedir}/resources"> <exclude name="META-INF/persistence*.xml"/> <exclude name="import*.sql"/> <exclude name="${project.name}-*-ds.xml"/> <exclude name="components-*.properties"/> </fileset> <fileset dir="${basedir}/view"/> </copy> <copy tofile="${test.dir}/META-INF/persistence.xml" file="${basedir}/resources/META-INF/persistence-test.xml"/> <copy tofile="${test.dir}/import.sql" file="${basedir}/resources/import-test.sql"/>   <copy tofile="${test.dir}/components.properties" file="${basedir}/resources/components-test.properties"> <filterset > <filter token="puJndiName" value="java:/${project.name}EntityManagerFactory"/> </filterset> </copy> <copy todir="${test.dir}" flatten="true"> <fileset dir="${src.test.dir}"> <include name="**/*Test.xml" /> </fileset> </copy> </target> The components.properties had hardcoded values for persistence unit configuration, which were wrong. I've added this filter to build.xml and modified the components-test.properties: # These properties are used to replace Ant-style tokens in the component descriptor (components.xml) at runtime. jndiPattern=#{ejbName}/local debug=true seamBootstrapsPu=true # Wrong! #seamEmfRef=#{entityManagerFactory} #puJndiName=#{null} # Fix! seamEmfRef=#{null} puJndiName=@puJndiName@ Also, the readme.txt in the generated test folder doesn't mention that this Ant target has to run before you run the tests in the IDE and that you have to add the ${test.dir} folder to your classpath and NOT create a module dependency on your core application build output classpath etc. I don't know how that works in Eclipse but in IntelliJ I had to create a separate module with a completely separate list of classpath entries, and enable the 'buildtest' Ant target before the test suite runs. -- 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, 2 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2009