October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2601) Exception handling - Improve the exception reporting with more context information

by Shane Bryzak (JIRA)

Exception handling - Improve the exception reporting with more context information ---------------------------------------------------------------------------------- Key: JBSEAM-2601 URL: http://jira.jboss.com/jira/browse/JBSEAM-2601 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Once we clean up #{exception} and #{handledException} (remove one...), we need to add more context information. I don't know how to do that so I don't have any recommendation how this could be implemented - only that I heard that Tapestry has good exceptions. What I need (especially now in production) is more information about the request that triggered the exception. For example, I want to be able to reproduce the exception by executing the same GET/POST request. So this needs to include request header/parameter information and information about the server-side state (is it a new session, etc). I need to be able to access that information in my exception handler and for production optionally have it logged. Without this, I need to rely on user error reports which so far have not resulted in a single bugfix of the wiki, because I can't reproduce what the users are doing. -- 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

16 years, 4 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2296) @DataModelSelection makes tests impossible

by Christian Bauer (JIRA)

@DataModelSelection makes tests impossible ------------------------------------------ Key: JBSEAM-2296 URL: http://jira.jboss.com/jira/browse/JBSEAM-2296 Project: JBoss Seam Issue Type: Bug Components: Test Harness Reporter: Christian Bauer @Name("testBean") @Scope(ScopeType.CONVERSATION) @AutoCreate public class TestBean { @DataModel private List<String> names; public List<String> getNames() { return names; } public void setNames(List<String> names) { this.names = names; } @DataModelSelection private String name; public String getName() { return name; } public void setName(String name) { this.name = name; } public void init() { this.names = new ArrayList<String>(); this.names.add("A"); this.names.add("B"); this.names.add("C"); } } The test: @Test public void test() throws Exception { new FacesRequest() { protected void invokeApplication() throws Exception { TestBean testBean = (TestBean)getInstance("testBean"); testBean.init(); testBean.setName("B"); System.out.println("#### NAME IS: " + testBean.getName()); assert testBean.getName().equals("B"); } }.run(); } This test fails and prints the selected name as "A". If you remove @DataModelSelection, it prints the correct "B". -- 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

16 years, 4 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1469) @In for GWT clients

by Gavin King (JIRA)

@In for GWT clients ------------------- Key: JBSEAM-1469 URL: http://jira.jboss.com/jira/browse/JBSEAM-1469 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.3.0.GA The GWT code to call a server-side component is *really* ugly. You should be able to get a Seam component just by injecting it into your GWT client-side object. -- 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

16 years, 4 months

7
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-982) Make SeamText parser more flexible

by Christian Bauer (JIRA)

Make SeamText parser more flexible ---------------------------------- Key: JBSEAM-982 URL: http://jira.jboss.com/jira/browse/JBSEAM-982 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer We need a more flexible seam-text.g - possibly several stages with an AST in the middle. This is needed for - generating PDF output from seam text - implementing a diff algorithm -- 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

16 years, 4 months

2
3
0 / 0

[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

16 years, 4 months

3
6
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

16 years, 4 months

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

16 years, 4 months

16
61
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2305) GWT 1.4 DTO support for java.io.Serializable

by darren hartford (JIRA)

GWT 1.4 DTO support for java.io.Serializable -------------------------------------------- Key: JBSEAM-2305 URL: http://jira.jboss.com/jira/browse/JBSEAM-2305 Project: JBoss Seam Issue Type: Task Components: Remoting Affects Versions: 2.0.0.GA Reporter: darren hartford Assigned To: Shane Bryzak GWT 1.4 supports java.io.Serializable, but the SEAM remoting to GWT still --requires-- any DTO to implement com.google.gwt.user.client.rpc.IsSerializable. This is not documented anywhere and should be documented for 2.0.0.GA (to avoid frustrations) as well as examine support in the future to no longer require IsSerializable for SEAM-GWT-Remoting. -- 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

16 years, 4 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2144) s:link builds absolute path URL with private IP address

by koen handekyn (JIRA)

s:link builds absolute path URL with private IP address ------------------------------------------------------- Key: JBSEAM-2144 URL: http://jira.jboss.com/jira/browse/JBSEAM-2144 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Environment: the same on windows/linux with jboss 4.2.1 Reporter: koen handekyn link to view "/example.xhtml" becomes "http://10.0.0.1:8080/example.seam" (including private server address and protocol) which breaks when run behind an apache proxy from my code: <li><s:link view="/mobistar/portal.xhtml" value="portal" /></li> becomes rendered as <li><a href="http://localhost:8080/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> while it should be <li><a href="/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> -- 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

16 years, 5 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3225) Seam Remoting JS memory leak in IE

by Joshua Davis (JIRA)

Seam Remoting JS memory leak in IE ---------------------------------- Key: JBSEAM-3225 URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: IE 6 Reporter: Joshua Davis Assignee: Shane Bryzak Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- 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

16 years, 5 months

2
14
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 October 2008