October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2125) Maven: jboss-seam has wrong packaging

by Stephan Bublava (JIRA)

Maven: jboss-seam has wrong packaging ------------------------------------- Key: JBSEAM-2125 URL: http://jira.jboss.com/jira/browse/JBSEAM-2125 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Stephan Bublava Priority: Minor Since jboss-seam is an EAR module it should have <packaging>ear</packaging> in it's pom.xml. This requires adding <type>ejb</type> to all dependency declarations. -- 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, 1 month

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2192) AbstractMap from org.jboss.seam.international.Messages needs containsKey()

by Damian Harvey (JIRA)

AbstractMap from org.jboss.seam.international.Messages needs containsKey() -------------------------------------------------------------------------- Key: JBSEAM-2192 URL: http://jira.jboss.com/jira/browse/JBSEAM-2192 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Environment: Mac OSX, Jboss 4.2.1 Reporter: Damian Harvey Performing a containsKey() on the AbstractMap from org.jboss.seam.international.Messages results in severe performance problems (800ms on 1,800 properties compared to under 1ms for a get()) eg: @In Map<String, String> messages; //This is the Seam messages bundle public void aMethod() { if(messages.containsKey("key.mykey")) { //do something } } I traced the containsKey for a while but it went on a mad run through ELResolvers and Pages.java etc. Simple solution is to add a containsKey to the AbstractMap: public boolean containsKey(String key) { if(messages.get(key).equals(key)) { return false; } else { return true; } } Would be nice to know why this 'mad run' happened though. Hopefully not symptomatic of something wrong deeper down. Cheers, Damian. -- 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, 1 month

2
5
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

17 years, 1 month

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

17 years, 1 month

3
8
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

17 years, 1 month

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

17 years, 1 month

2
3
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

17 years, 1 month

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1952) persistenceUnitProperties on EntityManagerFactory must be parameterized

by Dan Allen (JIRA)

persistenceUnitProperties on EntityManagerFactory must be parameterized ----------------------------------------------------------------------- Key: JBSEAM-1952 URL: http://jira.jboss.com/jira/browse/JBSEAM-1952 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Priority: Minor The XML configuration schema boast support for persistence-unit-properties on the EntityManagerFactory component. However, the configuration does not work because persistenceUnitProperties is not parameterized and therefore the Seam map converter cannot figure out what to do. If key/value pairs are specified, Seam fails to start. Here is an example: <persistence:entity-manager-factory name="emf" persistence-unit-name="pu"> <persistence:persistence-unit-properties> <key>hibernate.hbm2ddl.auto</key> <value>create-drop</value> </persistence:persistence-unit-properties> </persistence:entity-manager-factory> Here is the exception that is thrown: Caused by: java.lang.IllegalArgumentException: collection type not parameterized at org.jboss.seam.util.Reflections.getCollectionElementType(Reflections.java:188) at org.jboss.seam.Component$MapInitialValue.<init>(Component.java:2457) at org.jboss.seam.Component.getInitialValue(Component.java:526) at org.jboss.seam.Component.getTopInitialValue(Component.java:510) at org.jboss.seam.Component.initInitializers(Component.java:488) at org.jboss.seam.Component.<init>(Component.java:260) at org.jboss.seam.Component.<init>(Component.java:214) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:940) Unfortunately, the best option we have, from the converters that Seam supports, is to make it a Map<String, String>. In the patch supplied I have used this signature. -- 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, 1 month

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1947) incorrect id rendered from s:commandButton and s:commandLink components.

by Alexander Smirnov (JIRA)

incorrect id rendered from s:commandButton and s:commandLink components. ------------------------------------------------------------------------ Key: JBSEAM-1947 URL: http://jira.jboss.com/jira/browse/JBSEAM-1947 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Environment: any Reporter: Alexander Smirnov Assigned To: Pete Muir Wrong id encoded by s:commandButton and s:commandLink in HTML tags . Instead of clientId, simple getId() value rendered. As a result all html elements inside iterations have same id attribute value. -- 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, 1 month

2
6
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

17 years, 1 month

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007