February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2598) Exception handling - Never log and handle an exception, do one or the other

by Shane Bryzak (JIRA)

Exception handling - Never log and handle an exception, do one or the other --------------------------------------------------------------------------- Key: JBSEAM-2598 URL: http://jira.jboss.com/jira/browse/JBSEAM-2598 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Either I see my exception in the log (because it is one of the VERY RARE silently recoverable exceptions - I would not know a single one) or it is handled by my exception handler. Actually, I should never see an exception in my log unless I say so in my exception handler. I've seen Shane doing some commits about this but he only made logging configurable in Exceptions.handle(), which runs AFTER SeamPhaseListener already dumps a log.error("Uncaught exception", e). So basically, you can now configure if you want an exception logged twice or just once. This is btw killing me in production because my log fills up with login-password failures if someone makes a typo. -- 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

4
11
0 / 0

[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

15 years, 1 month

5
10
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

15 years, 1 month

7
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

15 years, 1 month

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

15 years, 1 month

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

15 years, 1 month

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

15 years, 2 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

15 years, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2292) Resources from resource servlet can't be re-rendered

by Christian Bauer (JIRA)

Resources from resource servlet can't be re-rendered ---------------------------------------------------- Key: JBSEAM-2292 URL: http://jira.jboss.com/jira/browse/JBSEAM-2292 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Christian Bauer Found this after using the captcha: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> This is a re-rendered s:decorate form field, so that onblur we get a new challenge (if the captcha repsonse was wrong). However, the graphicImage is not reloaded from the server, the browser caches it. To prevent browser caching, this is a quick hack: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha?nocache=#{wiki:generateRandomNumber()}" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> -- 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, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1712) Allow options for SMPC per Nested Conversation

by Andy Gibson (JIRA)

Allow options for SMPC per Nested Conversation ---------------------------------------------- Key: JBSEAM-1712 URL: http://jira.jboss.com/jira/browse/JBSEAM-1712 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Environment: Windows XP, Seam 2.0 Beta, JBoss 4.2 Reporter: Andy Gibson I'd like to request the option to specify that a nested conversation gets it's own entity manager instance as opposed to sharing it with it's parent conversation and other nested conversations. The problem with nested conversations is that you can't actually use them to edit multiple entities since when you flush the PC, you flush it for all conversations. This makes nested conversations only really useful for browsing data, and creating new top level conversation to edit items to isolate the flushes. The only alternative is to use a non-Seam managed PC, and make use of the "PC per stateful bean" rule to map a single PC to a single backing bean, but you lose the benefits of a seam managed PC. What might be nice is something like : @Begin(nested=true, newPC=true) and <begin-conversation nested="true" newPC="true"/> which would indicate that this new nested conversation gets it's own entity manager instance. The attribute would be ignored if this wasn't a nested conversation, and obviously, by default, the attribute is set to false, and a shared PC would be used in the nested conversation in such cases. I'm already using one PC per conversation by using top level conversations to edit items, I'd just like to use one PC per nested conversation (where applicable) to get the benefits of nested conversations. There are a couple of posts in the forums where I've touched on some of my problems with this issue : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111681 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111384 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113362 -- 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, 3 months

7
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008