December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2151) Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples

by Pete Muir (JIRA)

Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2151 URL: http://jira.jboss.com/jira/browse/JBSEAM-2151 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Trivial Fix For: 2.0.1.GA -- 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2107) Seam example "seampay", asynchronous scheduler don't work on Tomcat with JBoss Embedded

by Stateless Bean (JIRA)

Seam example "seampay", asynchronous scheduler don't work on Tomcat with JBoss Embedded --------------------------------------------------------------------------------------- Key: JBSEAM-2107 URL: http://jira.jboss.com/jira/browse/JBSEAM-2107 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.6.GA Environment: windows xp, java 1.5 SDK and 1.6 SDK, tomcat 5.5.13 and 6.0 Postgresql 8.2 Reporter: Stateless Bean Fix For: 2.0.0.GA I try to run example seampay on tomcat with Jboss embedded, but seam asynchonos scheduler doesn't work on tomcat, Since 1.1.6 ver. of seam still I get null. On JBoss 4.0.5 example work fine! -- 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, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2132) consult class attribute on component XML declaration with namespace

by Dan Allen (JIRA)

consult class attribute on component XML declaration with namespace ------------------------------------------------------------------- Key: JBSEAM-2132 URL: http://jira.jboss.com/jira/browse/JBSEAM-2132 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Dan Allen Assigned To: Dan Allen Priority: Critical Fix For: 2.0.1.GA When a component template class is being configured (such as EntityHome, EntityQuery, etc), the class attribute should be considered prior to deriving the class name from the namespace info + XML element name. Doing so prevents the case where two components are being configured for the same name when the developer intends only to use it for configuration. Case in point: Let's say I create a class that extends EntityHome to provide some extra behavior. @Name("myEntityHome") public class MyEntityHome extends EntityHome { } Now I want to configure the properties of this class in components.xml <framework:entity-home name="myEntityHome" class="org.example.model.MyEntityHome"> <framework:created-message>You created it! Yeah!</framework:created-message> <framework:updated-message>You updated it! Yeah!</framework:updated-message> <framework:deleted-message>You deleted it! Yeah!</framework:deleted-message> </framework:entity-home> If the class attribute is not consulted, it will look for a @Name annotation on org.jboss.seam.framework.EntityHome rather than org.example.model.MyEntityHome. When it doesn't find one on the built-in class, it tries to create a new component definition. Why would I want to use XML namespace tags in this case? Simple. Tag completion and property recognition support. Note that this works if the class resolved from XML namespace + element name is the same as the component class. In the case when the component class extends the built-in class, you get this problem. -- 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, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2106) References to Hibernate entities in a list are null after returning from nested conversation

by Gabor Nagypal (JIRA)

References to Hibernate entities in a list are null after returning from nested conversation -------------------------------------------------------------------------------------------- Key: JBSEAM-2106 URL: http://jira.jboss.com/jira/browse/JBSEAM-2106 Project: JBoss Seam Issue Type: Bug Environment: Seam 2 CR 2, Windows XP, JDK 1.6b02 Reporter: Gabor Nagypal If a conversation- scope bean contains a list that references Hibernate entities, the references are nullified when the application returns from a nested conversation. -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2049) errant attributes on rich:calendar

by Dan Allen (JIRA)

errant attributes on rich:calendar ---------------------------------- Key: JBSEAM-2049 URL: http://jira.jboss.com/jira/browse/JBSEAM-2049 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.0.CR2 rich:calendar has attributes that were left behind from s:selectDate that are no longer needed event - no applicable for rich:calendar reRender - not needed because Ajax isn't used on calendar and prevents invalid date from being entered (reRender also makes it impossible to change month/year) bypassUpdates - not needed because reRender is not 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2091) Update oc4j docs for new dependencies

by Pete Muir (JIRA)

Update oc4j docs for new dependencies ------------------------------------- Key: JBSEAM-2091 URL: http://jira.jboss.com/jira/browse/JBSEAM-2091 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Fix For: 2.0.1.GA Still disucsses using thirdparty-all.jar etc. -- 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, 8 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2083) RichFaces - No active conversation context

by Wesley Hales (JIRA)

RichFaces - No active conversation context ------------------------------------------- Key: JBSEAM-2083 URL: http://jira.jboss.com/jira/browse/JBSEAM-2083 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Environment: 2.0.0.CR2 Embedded on Tomcat 6.0.13 Trinidad 1.0.2 RichFaces 3.2.0-SNAPSHOT Reporter: Wesley Hales Any page holding a RichFaces component throws java.lang.IllegalStateException: No active conversation context -- 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, 8 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2089) Document deploying Seam apps to WLS

by Pete Muir (JIRA)

Document deploying Seam apps to WLS ----------------------------------- Key: JBSEAM-2089 URL: http://jira.jboss.com/jira/browse/JBSEAM-2089 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Fix For: 2.0.x -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2032) make page resources configurable for Pages (i.e. WEB-INF/pages.xml)

by Dan Allen (JIRA)

make page resources configurable for Pages (i.e. WEB-INF/pages.xml) ------------------------------------------------------------------- Key: JBSEAM-2032 URL: http://jira.jboss.com/jira/browse/JBSEAM-2032 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.0.CR2 Everything is setup to be able to configure the location of the pages.xml file, except the property is not exposed. I feel this is both important for tests and allows users to put pages.xml on the classpath (i.e. META-INF/pages.xml) rather than in the web-specific WEB-INF directory. It will be configured using: <component class="org.jboss.seam.navigation.Pages"> <property name="resources"> <value>/WEB-INF/pages.xml</value> <value>/META-INF/pages.xml</value> </property> </component> The only limitation is that the ResourceLoader used only looks in the servlet life cycle classpath. That will need to be a separate enhancement. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2040) blog demo renderring error

by Norman Richards (JIRA)

blog demo renderring error --------------------------- Key: JBSEAM-2040 URL: http://jira.jboss.com/jira/browse/JBSEAM-2040 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR1 Reporter: Norman Richards Fix For: 2.0.0.CR2 The blog example index page shows: This page contains the following errors: error on line 117 at column 1024: Opening and ending tag mismatch: p line 0 and div Below is a rendering of the page up to the first error. ... This is probably a seam-text issue or a problem with the data. -- 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, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007