May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3022) Enable DBUnitSeamTest to work with Oracle

by Tom Nicholls (JIRA)

Enable DBUnitSeamTest to work with Oracle ----------------------------------------- Key: JBSEAM-3022 URL: http://jira.jboss.com/jira/browse/JBSEAM-3022 Project: Seam Issue Type: Feature Request Components: Test Harness Environment: Oracle database Reporter: Tom Nicholls Enable Seam Integration tests to work with Oracle databases by implementing methods to enable and disable referential integrity. All code required for this is contained in the JBoss Forum reference given below in this issue. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2187) E-mail attachment <cid:xxxxxx> problem

by Stefano Zaccaria (JIRA)

E-mail attachment <cid:xxxxxx> problem -------------------------------------- Key: JBSEAM-2187 URL: http://jira.jboss.com/jira/browse/JBSEAM-2187 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.0.CR3 Reporter: Stefano Zaccaria Assigned To: Pete Muir Priority: Minor Fix For: 2.0.0.GA When use the cid: tag with seam like the document read <m:attachment value="#{person.photo}" contentType="image/jpeg" fileName="#{person.firstname}_#{person.lastname}.jpg" status="personPhoto" disposition="inline" /> <img src="cid:#{personPhoto.contentId}" /> In my email client (Thunderbird) the image is attachment and not place inline -- 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

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-81) Seam context variables hide JSF view-scoped things

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-81?page=all ] Pete Muir updated JBSEAM-81: ---------------------------- Summary: Seam context variables hide JSF view-scoped things (was: Seam context variables hide JSF page-scoped things) > Seam context variables hide JSF view-scoped things > -------------------------------------------------- > > Key: JBSEAM-81 > URL: http://jira.jboss.com/jira/browse/JBSEAM-81 > Project: Seam > Issue Type: Bug > Components: JSF Integration > Reporter: Gavin King > Assigned To: Gavin King > -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3013) @Converter for some target superclass doesn't work on it's subclasses

by Gena Batalski (JIRA)

@Converter for some target superclass doesn't work on it's subclasses --------------------------------------------------------------------- Key: JBSEAM-3013 URL: http://jira.jboss.com/jira/browse/JBSEAM-3013 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.0.A1, 2.0.2.GA Environment: Seam 2.1.0.A1 Reporter: Gena Batalski Priority: Minor I define the @Converter to target some class. This class is the parent of an inheritance hierarchy. Seam doesn't respect the inheritance and, thus, doesn't find the converter. If no converter found, the work is delegated to the JSF- AplicationImpl.createConverter(..). JSF tries then to determine the converter and analyzes the interfaces and superclass of the class, that should be converted. But it doesn't find anything, because Seam didn't register this converter to JSF properly. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3019) Support sending of StatusMessages for Remoting requests

by Shane Bryzak (JIRA)

Support sending of StatusMessages for Remoting requests ------------------------------------------------------- Key: JBSEAM-3019 URL: http://jira.jboss.com/jira/browse/JBSEAM-3019 Project: Seam Issue Type: Feature Request Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Fix For: 2.1.0.BETA1 Any StatusMessages raised during a Seam Remoting invocation should be sent back in the response, and made available to the callback function. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1274) Not able to query FacesMessages to determine if any messages have been added.

by Nathaniel Stoddard (JIRA)

Not able to query FacesMessages to determine if any messages have been added. ----------------------------------------------------------------------------- Key: JBSEAM-1274 URL: http://jira.jboss.com/jira/browse/JBSEAM-1274 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard It would be helpful to determine if messages have been added to FacesMessages. At this point, it is impossible to determine if messages are present in FacesMessages. -- 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

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-270) Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together

by Denis Forveille (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-270?page=comments#action_12413356 ] Denis Forveille commented on JBSEAM-270: ---------------------------------------- oups forgot the details: seam 2.0.2 exception is slightly different and more precise: ... Caused by: java.lang.IllegalStateException: Multiple @DataModelSelection fields for: listeDocuments at org.jboss.seam.Component.initMembers(Component.java:571) at org.jboss.seam.Component.<init>(Component.java:254) at org.jboss.seam.Component.<init>(Component.java:217) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:974) > Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together > ---------------------------------------------------------------------------------------------------- > > Key: JBSEAM-270 > URL: http://jira.jboss.com/jira/browse/JBSEAM-270 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Affects Versions: 1.0 > Environment: WinXP Professional > JBoss AS 4.0.4.GA (ejb3.deployer libs replaced by EJB3 RC8 libs) > myFaces Core 1.1.3 > Tomahawk 1.1.3 > Facelets (as in Seam 1.0.0.GA) > JDK1.5.0_06 > Reporter: Jens Weintraut > Priority: Minor > > A seam component can't use both annotations @DataModelSelection and @DataModelSelectionIndex at once. If both are used deployment shows this error message: > java.lang.IllegalStateException: Multiple @DataModelSelection fields for: messageList > at org.jboss.seam.Component.initMembers(Component.java:533) > at org.jboss.seam.Component.<init>(Component.java:199) > at org.jboss.seam.Component.<init>(Component.java:159) > at org.jboss.seam.Component.<init>(Component.java:154) > at org.jboss.seam.Component.<init>(Component.java:149) > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:381) > at org.jboss.seam.init.Initialization.addComponents(Initialization.java:343) > at org.jboss.seam.init.Initialization.init(Initialization.java:195) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:32) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729) > ... -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-270) Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together

by Denis Forveille (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-270?page=comments#action_12413355 ] Denis Forveille commented on JBSEAM-270: ---------------------------------------- +1 for us > Annotations @DataModelSelection and @DataModelSelectionIndex can't be used in one component together > ---------------------------------------------------------------------------------------------------- > > Key: JBSEAM-270 > URL: http://jira.jboss.com/jira/browse/JBSEAM-270 > Project: Seam > Issue Type: Feature Request > Components: JSF Integration > Affects Versions: 1.0 > Environment: WinXP Professional > JBoss AS 4.0.4.GA (ejb3.deployer libs replaced by EJB3 RC8 libs) > myFaces Core 1.1.3 > Tomahawk 1.1.3 > Facelets (as in Seam 1.0.0.GA) > JDK1.5.0_06 > Reporter: Jens Weintraut > Priority: Minor > > A seam component can't use both annotations @DataModelSelection and @DataModelSelectionIndex at once. If both are used deployment shows this error message: > java.lang.IllegalStateException: Multiple @DataModelSelection fields for: messageList > at org.jboss.seam.Component.initMembers(Component.java:533) > at org.jboss.seam.Component.<init>(Component.java:199) > at org.jboss.seam.Component.<init>(Component.java:159) > at org.jboss.seam.Component.<init>(Component.java:154) > at org.jboss.seam.Component.<init>(Component.java:149) > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:381) > at org.jboss.seam.init.Initialization.addComponents(Initialization.java:343) > at org.jboss.seam.init.Initialization.init(Initialization.java:195) > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:32) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729) > ... -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3010) Multiple wars, pages.xml navigation rules incorrectly applied

by pieter martin (JIRA)

Multiple wars, pages.xml navigation rules incorrectly applied ------------------------------------------------------------- Key: JBSEAM-3010 URL: http://jira.jboss.com/jira/browse/JBSEAM-3010 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1 Environment: jboss-4.2.2.GA, svn trunk Seam 2.1.0 Reporter: pieter martin If there are multiple wars inside the ear then the navigation rules of the wrong pages.xml file gets applied. A more though row description is on the seam forum. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2941) Menu item editor is broken

by Christian Bauer (JIRA)

Menu item editor is broken -------------------------- Key: JBSEAM-2941 URL: http://jira.jboss.com/jira/browse/JBSEAM-2941 Project: Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer The menu item editor in the directory editor is broken. Even after switching to Petes new EntityLoader/EntityConverter mechanism, a bug introduce at some point in Seam is causing conversion of the combobox values to fail: >>> 10:58:41,843 INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=directoryEditForm:j_id387[severity=(ERROR 2), summary=(Value is not valid), detail=(Value is not valid)] -- 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

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008