July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2595) Exception handling - Never swallow an exception

by Shane Bryzak (JIRA)

Exception handling - Never swallow an exception ----------------------------------------------- Key: JBSEAM-2595 URL: http://jira.jboss.com/jira/browse/JBSEAM-2595 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA For example, if an action throws NPE, the exception handler checks what is defined in pages.xml. If no handler is defined, SeamPhaseListener swallows the exception after printing it in the log. This is a bad strategy, as most users start with no exception handling defined and no pages.xml, yet they don't see their exceptions on the page. We need SOME default handler, even if no pages.xml is present. -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2952) Icefaces example hotel search conversation timeouts

by Jay Balunas (JIRA)

Icefaces example hotel search conversation timeouts --------------------------------------------------- Key: JBSEAM-2952 URL: http://jira.jboss.com/jira/browse/JBSEAM-2952 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas I believe that the conversation handling may have a problem. - Search for hotels (note no hotel list by default - inconsistent will other booking examples). - Launch one hotel into a tab (typically using center mouse button) - The new tab contains the same search results, not the hotel from the link. - The links in the new tab table do not do anything. - Must click "more results" to have any other hotel links work. - Begin to book a different hotel in the original tab - At this point you should have 2 conversation/workspaces. - Note attempting to change the workspace using the links at the bottom do no do anything - Eventually you will get a "user session timeout" error. This is not a http session timeout. - I think that something gets confused with the conversations. -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3199) seam-gen test readme.txt jar listing needs to be updated

by Jay Balunas (JIRA)

seam-gen test readme.txt jar listing needs to be updated -------------------------------------------------------- Key: JBSEAM-3199 URL: https://jira.jboss.org/jira/browse/JBSEAM-3199 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Assignee: Pete Muir Fix For: 2.0.2.GA The readme.txt file that gets put in the seam-gen test source directory contains out of date jar files. Below is the complete readme. Changes need (from what I can see): - embedded-api.jar --> jboss-embedded-api.jar - jboss-deployers.jar --> jboss-deployers-client-spi.jar, jboss-deployers-core-spi.jar readme.txt If you want to run tests using the Eclipse TestNG plugin, you'll need to add these jars to the top of your TestNG classpath. Using the Run Dialog, select xml suite to run, and add /lib/test/jboss-embedded-all.jar, /lib/test/hibernate-all.jar, /lib/test/thirdparty-all.jar, /lib/embedded-api.jar, /lib/jboss-deployers.jar and /bootstrap as the first entries in the User classpath. To add tests to your project create a TestNG xml descriptor called *Test.xml e.g. FooTest.xml next to your test classes and run ant test. -- 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

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2522) Update to JBoss Cache 2.1

by Pete Muir (JIRA)

Update to JBoss Cache 2.1 ------------------------- Key: JBSEAM-2522 URL: http://jira.jboss.com/jira/browse/JBSEAM-2522 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA This should sort out our dependencies a bit I hope. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3083) urlBase on <m:message> does not work

by Dan Allen (JIRA)

urlBase on <m:message> does not work ------------------------------------- Key: JBSEAM-3083 URL: http://jira.jboss.com/jira/browse/JBSEAM-3083 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.3.CR1, 2.1.0.BETA1 The attribute urlBase on <m:message> is broken in two fundamental ways. First, the logic as to whether to use the urlBase doesn't make any sense at all, resulting in the urlBase never being used. The second problem is that EL value expressions in the urlBase are not getting resolved. I am proposing a strategy as part of this fix. If the urlBase is used, it is taken verbatim, without appending the current context path. The reason is, if urlBase is overridden, it may be because it is pointing to a completely different application. If the developer want to reuse the context path, the expression #{facesContext.externalContext.requestContextPath} must be included in the urlBase attribute. -- 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
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2508) openId support components

by koen handekyn (JIRA)

openId support components ------------------------- Key: JBSEAM-2508 URL: http://jira.jboss.com/jira/browse/JBSEAM-2508 Project: JBoss Seam Issue Type: Feature Request Reporter: koen handekyn Priority: Optional provide standard components to allow easy setup for openId support in a seam application. the seam identity contains both username and password fields. an openId identity consist soly of an identity string. ideally an openId authenticator takes in just a single openId identity, performs the openId logn procedures and concludes (in case of succesful authentication in a logged in session, with the identifier confirmed. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1891) Decouple page fragment caching from JBoss Cache

by Christian Bauer (JIRA)

Decouple page fragment caching from JBoss Cache ----------------------------------------------- Key: JBSEAM-1891 URL: http://jira.jboss.com/jira/browse/JBSEAM-1891 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Minor The code in UICache and PojoCache only works with this component: return (org.jboss.cache.aop.PojoCache) Component.getInstance(PojoCache.class, ScopeType.APPLICATION); Make this generic so that other cache providers can be used. -- 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

6
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3107) Jbpm.installPageflowDefinitions() changes order of pageflowDefinitions

by Wolfgang Schwendt (JIRA)

Jbpm.installPageflowDefinitions() changes order of pageflowDefinitions ---------------------------------------------------------------------- Key: JBSEAM-3107 URL: http://jira.jboss.com/jira/browse/JBSEAM-3107 Project: Seam Issue Type: Bug Environment: Seam 2.1 SVN trunk Reporter: Wolfgang Schwendt Priority: Blocker Fix For: 2.1.0.BETA2 current code in Seam 2.1. SVN-based trunk: org.jboss.seam.bpm.Jbpm private void installPageflowDefinitions() { Set<String> mergedPageflowDefinitions = new TreeSet<String>(); Set semantics is wrong here. In order to fix the bug described below, please change to ArrayList<String> mergedPageflowDefinitions = new ArrayList<String>(); Reason: when jPDL tries to parse pageflow with a <process-state> that calls a sub pageflow via a <sub-process name="subpageflow"/> child element, it can only parse the process-state if the subpageflow was parsed already. See org.jbpm.graph.node.ProcessState.read(). If the subpageflow was NOT parsed already before the <process state> of the parent pageflow gets parsed, jBPM's SubProcessResolver throws a null pointer exception (NPE). Hence, to avoid a NPE, we have have to list all included pageflows in a partial order in components.xml: The pageflows first listed are the included subpageflows, the pageflows listed last are the parent pageflows which call the preceding subpageflows. Now, if installPageflowDefinitions() puts the names of these pageflow definition files in a set (rather than list), the order gets lost and in turn the likelihood increases that jBPM's SubProcessResolver throws a null pointer exception. <!--Pageflow definition in a special order with subpageflows listed first -> <bpm:jbpm> <bpm:process-definitions></bpm:process-definitions> <bpm:pageflow-definitions> <value>/WEB-INF/benutzerKontoEroeffnen.jpdl.xml</value> <value>/WEB-INF/beimSystemAnmelden.jpdl.xml</value> <value>/WEB-INF/beimSystemAnmeldenTopLevel.jpdl.xml</value> <value>/WEB-INF/aufWartelisteSetzen.jpdl.xml</value> <value>/WEB-INF/persoenlicheDatenBearbeiten.jpdl.xml</value> <value>/WEB-INF/zumSeminarAnmelden.jpdl.xml</value> <value>/WEB-INF/seminarSuche.jpdl.xml</value> <value>/WEB-INF/seminardatenBearbeiten.jpdl.xml</value> <value>/WEB-INF/seminarbelegungenEinsehen.jpdl.xml</value> </bpm:pageflow-definitions> </bpm:jbpm> -- 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

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3099) Port JBSEAM-3048 to trunk "Add id attribute to markup for JSF components in Seam examples"

by Jay Balunas (JIRA)

Port JBSEAM-3048 to trunk "Add id attribute to markup for JSF components in Seam examples" ------------------------------------------------------------------------------------------ Key: JBSEAM-3099 URL: http://jira.jboss.com/jira/browse/JBSEAM-3099 Project: Seam Issue Type: Task Components: Examples Affects Versions: 2.1.0.A1 Reporter: Jay Balunas Assigned To: Stan Silvert Fix For: 2.1.0.BETA1 Port the changes made from JBSEAM-3048 to trunk. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3178) JDK6 reference guide and sfwk.org instructions for support

by Jay Balunas (JIRA)

JDK6 reference guide and sfwk.org instructions for support ---------------------------------------------------------- Key: JBSEAM-3178 URL: https://jira.jboss.org/jira/browse/JBSEAM-3178 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 2.0.3.CR2, 2.1.0.BETA1 The instructions for running Seam with JDK have changed slightly. You need to run using JDK 1.6u4 + so that you do not have an issue JAXB 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

16 years, 5 months

1
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 July 2008