August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3235) Remove missing template WARN when using datatable exporter

by Nicklas Karlsson (JIRA)

Remove missing template WARN when using datatable exporter ---------------------------------------------------------- Key: JBSEAM-3235 URL: https://jira.jboss.org/jira/browse/JBSEAM-3235 Project: Seam Issue Type: Bug Components: Excel Reporter: Nicklas Karlsson Will probably be gone in the css migration anyway. -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3243) <s:formattedText> doesn't support alt and align attribute for html img tag,

by Siarhei Dudzin (JIRA)

<s:formattedText> doesn't support alt and align attribute for html img tag, ---------------------------------------------------------------------------- Key: JBSEAM-3243 URL: https://jira.jboss.org/jira/browse/JBSEAM-3243 Project: Seam Issue Type: Bug Components: Seam Text Affects Versions: 2.0.0.GA Reporter: Siarhei Dudzin <s:formattedText> doesn't support alt and align attribute for html img tag, Whan an img tag with align or alt attributes are met 'sysouts' the "Seam Text parse error: unexpected token" message, besides it cuts all the text that comes after it, i.e. nothing is rendered after that. For example if we have the following text to be rendered: This is <img src="img.gif" alt="alt text" /> text after image! The following will be actually rendered: This is <img src="img.gif" I would expect s:formattedText either (worst case) skip the attributes it doesn't support of actually support them. I am not sure the problem existed in Seam 1.2.1 btw, I migrated an application and then noticed the behavior... -- 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

17 years, 5 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1485) Configure Default Interceptors

by Bruno E. Grossi (JIRA)

Configure Default Interceptors ------------------------------ Key: JBSEAM-1485 URL: http://jira.jboss.com/jira/browse/JBSEAM-1485 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: Linux with only Tomcat, not JBoss Reporter: Bruno E. Grossi Create an configuration option to disable some default interceptors that there are never used, improving the application's performance. On some systems there are no necessity of some interceptors, for example, the transactional ones (RollbackInterceptor, TransactionInterceptor and ManagedEntityIdentityInterceptor) that degrade performance. -- 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, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3242) web.xml parsing should not create dependency on Jaxen

by Christian Bauer (JIRA)

web.xml parsing should not create dependency on Jaxen ----------------------------------------------------- Key: JBSEAM-3242 URL: https://jira.jboss.org/jira/browse/JBSEAM-3242 Project: Seam Issue Type: Task Components: Core Reporter: Christian Bauer Assignee: Pete Muir For three lines of code we have a dependency on jaxen.jar, this needs to be rewritten. -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3226) Modify DBUnitSeamTest to permit use of DTDs generated by DBUnit

by John J. Genoese (JIRA)

Modify DBUnitSeamTest to permit use of DTDs generated by DBUnit --------------------------------------------------------------- Key: JBSEAM-3226 URL: https://jira.jboss.org/jira/browse/JBSEAM-3226 Project: Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.3.CR1 Environment: Any Reporter: John J. Genoese Priority: Minor Given: DBUnit's behavior is such that if the first row to be loaded (via DataSetOperation) into a table doesn't have all columns present, those columns will be dropped in every row loaded thereafter. Given: If a DTD is present, DBUnit will honor it, and refrain from the aforementioned behavior. DBUnit has a facility to generate said DTD. Given: The current DBUnitSeamTest (for which I am grateful indeed) doesn't permit specification of said DTD's location. Hence, I must manually massage my test data to ensure that the first row loaded into each table has values for all columns, which causes considerable inconvenience in my automated testing flow (which includes data generation). Request: Modify DBUnitSeamTest to permit use of DTDs generated by DBUnit -- 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

17 years, 5 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2986) Seam Transaction rolls back on all Exceptions

by Sean Burns (JIRA)

Seam Transaction rolls back on all Exceptions --------------------------------------------- Key: JBSEAM-2986 URL: http://jira.jboss.com/jira/browse/JBSEAM-2986 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2 Reporter: Sean Burns It looks like org.jboss.seam.util.Work rolls back a transaction for all exceptions if it had to create a transaction. This does not follow the normal EJB rollback spec, where transactions are only rolled back on Runtime Exceptions and @ApplicationException(rollback=true). I can work around this by using EJB Seam components instead of Seam POJO. -- 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, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3023) seam-gen generate-entities throws NoSuchMethodError on AnnotationConfiguration.setProperty

by Jay Balunas (JIRA)

seam-gen generate-entities throws NoSuchMethodError on AnnotationConfiguration.setProperty ------------------------------------------------------------------------------------------ Key: JBSEAM-3023 URL: http://jira.jboss.com/jira/browse/JBSEAM-3023 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Priority: Blocker Fix For: 2.1.0.BETA1 This is effecting the current trunk - I have not verified if this is happening in 2.1.0.A1. Below is the output from the console. I saw this error both with and without the fix for JBSEAM-3017. I quickly checked that the correct jars are in the lib, and should be loaded for the classpath in the seam-gen/build.xml. There may be a new dependency or configuration needed. jar: [copy] Copying 2 files to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar/META-INF [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar/META-INF [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar [hibernate] Executing Hibernate Tool with a JPA Configuration [hibernate] 1. task: generic exportertemplate: view/list.xhtml.ftl [hibernate] May 22, 2008 9:37:04 AM org.hibernate.cfg.annotations.Version <clinit> [hibernate] INFO: Hibernate Annotations 3.3.0.GA [hibernate] May 22, 2008 9:37:04 AM org.hibernate.ejb.Version <clinit> [hibernate] INFO: Hibernate EntityManager 3.3.2.GA [hibernate] An exception occurred while running exporter #2:generic exportertemplate: view/list.xhtml.ftl [hibernate] To get the full stack trace run ant with -verbose [hibernate] Problems in creating a configuration for JPA. Have you remembered to add hibernate EntityManager jars to the classpath ? [hibernate] java.lang.reflect.InvocationTargetException [hibernate] java.lang.NoSuchMethodError: org.hibernate.cfg.AnnotationConfiguration.setProperty(Ljava/lang/String;Ljava/lang/String;)Lorg/hibernate/cfg/AnnotationConfiguration; BUILD FAILED /jboss/temp/trunk/jboss-seam-2.1.0-SNAPSHOT/seam-gen/build.xml:1124: Problems in creating a configuration for JPA. Have you remembered to add hibernate EntityManager jars to the classpath ? -- 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, 5 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2432) Wildcard view-id descriptions for conversation switcher

by Jacob Orshalick (JIRA)

Wildcard view-id descriptions for conversation switcher ------------------------------------------------------- Key: JBSEAM-2432 URL: http://jira.jboss.com/jira/browse/JBSEAM-2432 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick Priority: Minor I have recently run into a requirement where it would be nice to have descriptions applied to wildcard view-ids. For example, if I have the following: Code: ... <page view-id="/section/*" conversation-required="true"> <description>Section 1</description> ... </page> ... Section 1 would be the description for all pages in /section/* unless specified otherwise in a higher precedence page definition. -- 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, 5 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3237) Params in pages.xml don't accept multi-valued request parameters

by Philip Hansen (JIRA)

Params in pages.xml don't accept multi-valued request parameters ---------------------------------------------------------------- Key: JBSEAM-3237 URL: https://jira.jboss.org/jira/browse/JBSEAM-3237 Project: Seam Issue Type: Feature Request Reporter: Philip Hansen I was wondering if this was ever going to be implemented. I saw a post on the old forums where it sounded like it would be implemented at some point. I linked the post to this. -- 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

17 years, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2996) Imported seam-gen project does not show content assist on project specific components

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2996?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-2996: ----------------------------------- I added the .settings and .project to seam-gen for JBDS. However I don't have a value for the seam runtime. As soon as I specify a runtime, I see a problem where the exploded launch repeated runs with no action from me. Max, easy to reproduce - just create a project using seam-gen from trunk, then import into Eclipse, then specify a seam runtime. > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assignee: Max Rydahl Andersen > Fix For: 2.1.0.BETA1 > > > Following seam release-process.txt I imported a project I created with seam-gen using 2.0.2.CR2. > I used "import an existing project" option. Then added seam support to the project using a seam runtime I configured with 2.0.2.CR2. > When I opened a view file and tried out the content assist it showed a lot of Seam components, but none of the components in the project itself. -- 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

17 years, 5 months

1
0
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 August 2008