September 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2000) add excel file type to DocType enum

by Dan Allen (JIRA)

add excel file type to DocType enum ----------------------------------- Key: JBSEAM-2000 URL: http://jira.jboss.com/jira/browse/JBSEAM-2000 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Priority: Minor The document store facility (org.jboss.seam.pdf.DocumentStore) is an excellent reuse library for those who want to push down files in their Seam-based application (outside of just using the PDF tags). However, the module has one major limitation. The file types are stored in an enum and thus cannot ever be changed (enums cannot be extended or overridden). Unfortunately this renders the library completely useless if you are not using one of the 3 built-in types (PDF, RTF, HTML). Since Excel downloads are so popular in business applications, it makes sense that even though Seam doesn't export excel, the file type could be added to allow those using Seam-based applications to take advantage of this excellent document storage design. I have included a patch, but the line is simply: EXCEL("xls", "application/vnd.ms-excel") -- 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

18 years, 4 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-971) Conversations with business ids

by Gavin King (JIRA)

Conversations with business ids ------------------------------- Key: JBSEAM-971 URL: http://jira.jboss.com/jira/browse/JBSEAM-971 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical By defining a <conversation/> in pages.xml, pages can have the conversation propagated via a meaningful (restful) request parameter. By the way, we can make conversationIsLongRunning stuff disabled by default, unless its name is explicitly defined in components.xml. -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1998) javassist 3.3 and 3.4 are both imported by maven when I declare hibernate dependency

by Michael Yuan (JIRA)

javassist 3.3 and 3.4 are both imported by maven when I declare hibernate dependency ------------------------------------------------------------------------------------ Key: JBSEAM-1998 URL: http://jira.jboss.com/jira/browse/JBSEAM-1998 Project: JBoss Seam Issue Type: Bug Reporter: Michael Yuan Assigned To: Pete Muir Priority: Minor Fix For: 2.0.0.GA I have the following dependencies defined: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-validator</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> </dependency> And the generate WAR has both: javassist-3.3.ga.jar javassist-3.4.GA.jar Perhaps one of them should be removed. Thanks. -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1984) Please add icefaces dependency jars to the jboss maven repo

by Michael Yuan (JIRA)

Please add icefaces dependency jars to the jboss maven repo ----------------------------------------------------------- Key: JBSEAM-1984 URL: http://jira.jboss.com/jira/browse/JBSEAM-1984 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Pete Muir Fix For: 2.0.0.CR2 We need to make icefaces a dependency for the icefaces-seam-booking example and the icefaces-based seam-gen. The JARs we need are: Icefaces release 1.6.1: * icefaces.jar * icefaces-facelets.jar * icefaces-comps.jar Commons digester 1.6: * commons-digester.jar Commons fileupload 1.2: * commons-fileupload.jar Backport util concurrent 2.2: * backport-util-concurrent.jar All other icefaces dependencies are already satisfied by Seam. -- 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

18 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1972) s:decorate input control ID change from 1.2.1 to 2.0

by steve tynor (JIRA)

s:decorate input control ID change from 1.2.1 to 2.0 ---------------------------------------------------- Key: JBSEAM-1972 URL: http://jira.jboss.com/jira/browse/JBSEAM-1972 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Reporter: steve tynor I'm not sure if this is a bug or is intended behavior, but component ID's have changed from Seam version 1.2.1 to 2.0.0.CR1. This has broken our Selenium integration tests and many of our Javascript functions which access and manipulate the input controls via DHTML. Given something like: <s:decorate id="fooDecoration" template="/WEB-INF/facelets/templates/edit.xhtml"> <ui:define name="label">Foo</ui:define> <h:inputText id="foo" value="#{fooHome.instance.foo}"/> </s:decorate> In Seam1.2.1, the control was addressable as "fooForm:foo". In Seam2, that has changed and we must address it as "fooForm:fooDecoration:foo". Is this intentional? Is it likely to change before 2.0.0GA? -- 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

18 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1968) JPA (tomcat) example - requires Embedded Jboss?

by Matt Drees (JIRA)

JPA (tomcat) example - requires Embedded Jboss? ----------------------------------------------- Key: JBSEAM-1968 URL: http://jira.jboss.com/jira/browse/JBSEAM-1968 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.0.CR1 Reporter: Matt Drees Priority: Minor The readme for the JPA/tomcat example is ambiguous; it's not clear whether the example requires embedded Jboss or not. Also, assuming it should deploy on pure tomcat, it appears the example is now missing some (many?) required jar files. See forum post for details. -- 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

18 years, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1963) Seam gen .classpath is incorrect for new jar names

by Matt Drees (JIRA)

Seam gen .classpath is incorrect for new jar names -------------------------------------------------- Key: JBSEAM-1963 URL: http://jira.jboss.com/jira/browse/JBSEAM-1963 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR1 Reporter: Matt Drees Priority: Minor seam-gen/build-scripts/.classpath and seam-gen/icefaces/build-scripts/.classpath both have entries like "drools-core-4.0.0.jar", when they should have "drools-core" -- 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

18 years, 4 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1938) s:validateAll doesn't work correctly

by Ilya Shaikovsky (JIRA)

s:validateAll doesn't work correctly ------------------------------------ Key: JBSEAM-1938 URL: http://jira.jboss.com/jira/browse/JBSEAM-1938 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Ilya Shaikovsky Seems like when you add validators - you didn't expect that components that implements EditableValueHolder could be childs that also implements it. Our TabPanel and child inputs inside are simple example. -- 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

18 years, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1934) French message bundle for seam-gen

by Pierre Raoul (JIRA)

French message bundle for seam-gen ---------------------------------- Key: JBSEAM-1934 URL: http://jira.jboss.com/jira/browse/JBSEAM-1934 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Pierre Raoul Add messages_fr.properties in seam-gen -- 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

18 years, 4 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1929) Turkish message bundle for seam-gen

by Ali Sadik Kumlali (JIRA)

Turkish message bundle for seam-gen ----------------------------------- Key: JBSEAM-1929 URL: http://jira.jboss.com/jira/browse/JBSEAM-1929 Project: JBoss Seam Issue Type: Patch Components: Tools Affects Versions: 2.0.0.BETA1 Environment: Not relavent Reporter: Ali Sadik Kumlali Priority: Minor Hi, Attached messages_tr.properties file can be distributed as Turkish message bundle. I've tested it by adding following lines into faces-config.xml. <application> <locale-config> <default-locale>tr</default-locale>  </locale-config> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> </application> Regards, Ali Sadik Kumlali -- 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

18 years, 4 months

4
11
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 September 2007