June 2008 - seam-issues - Jboss List Archives

[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

17 years, 7 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

17 years, 7 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

17 years, 7 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

17 years, 7 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3102) Hibernate query at startup

by ricardo campos (JIRA)

Hibernate query at startup -------------------------- Key: JBSEAM-3102 URL: http://jira.jboss.com/jira/browse/JBSEAM-3102 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: JBoss 4.2.2.GA, Seam 2.0.2.SP1 Reporter: ricardo campos I believe the problem I posted here to be an issue: http://www.seamframework.org/Community/HibernateQueryAtStartup I'm getting "java.lang.IllegalStateException: No active session context" when executing a Hibernate query in a @Startup Component... -- 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

17 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3085) Renderer is only partially functional when used asynchronously

by Dan Allen (JIRA)

Renderer is only partially functional when used asynchronously -------------------------------------------------------------- Key: JBSEAM-3085 URL: http://jira.jboss.com/jira/browse/JBSEAM-3085 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Reporter: Dan Allen Fix For: 2.1.0.GA The Renderer, which is used to render Facelet templates, is partially crippled when used asynchronously. First of all, it throws an exception while setting up the MockFacesContext() because it tries to retrieve an Application from the real JSF FactoryFinder. That isn't going to work because JSF is not properly initialized. That leads to the second problem, which is that if the template has any JSF component tags, they aren't rendered because its not a real JSF environment. I think the solution is to use JSFUnit to emulate a JSF environment so that the Renderer can be used asynchronous. Otherwise, we cannot send email messages that use JSF components in the background. The second solution is to document that you cannot render JSF markup in your email if used asynchronously. This affects the /examples/mail demo application. -- 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

17 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2912) Translating Seam into your own language (sl-SI)

by Andrej Marolt (JIRA)

Translating Seam into your own language (sl-SI) ----------------------------------------------- Key: JBSEAM-2912 URL: http://jira.jboss.com/jira/browse/JBSEAM-2912 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: Andrej Marolt I would like to begin the process of translating Seam into Slovenian. (sl-SI) Language: Slovenian Locale: Slovenia -- 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

17 years, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2684) #{entityQuery.dataModel} returns empty model

by Alex Savitsky (JIRA)

#{entityQuery.dataModel} returns empty model -------------------------------------------- Key: JBSEAM-2684 URL: http://jira.jboss.com/jira/browse/JBSEAM-2684 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Alex Savitsky Priority: Critical When referenced from a JSF dataTable, a dataModel property from a conversation-scoped EntityQuery ALWAYS returns an empty model. The resultList property works normally, though. Placing the EntityQuery in session scope works, too. -- 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

17 years, 8 months

4
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2978) SeamFramework Wiki Login following clicking onto "Link" results in "HTTP Status 400 - Missing parentNodeId parameter"

by Leonid Maslov (JIRA)

SeamFramework Wiki Login following clicking onto "Link" results in "HTTP Status 400 - Missing parentNodeId parameter" --------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2978 URL: http://jira.jboss.com/jira/browse/JBSEAM-2978 Project: Seam Issue Type: Bug Components: Wiki Environment: Firefox 2.0.0.14 Win XP Reporter: Leonid Maslov Assigned To: Christian Bauer Priority: Minor h3. Scenario: * Go to Seam Framework site * Ensure Your are not logged in * Open any forum item * Enter Your cedentials and click "Login" * See "Login successful, welcome <username>." message * Click on "Link" link near the forum item title. * *Page fails with _HTTP Status 400 - Missing parentNodeId parameter_* and current page is: http://www.seamframework.org/docDisplay_d.seam h3. Expected result: The page stays the same as forum item page and without errors -- 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

17 years, 8 months

2
2
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 June 2008