July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4331) Upgrade xstream dependency

by Anthony Whitford (JIRA)

Upgrade xstream dependency -------------------------- Key: JBSEAM-4331 URL: https://jira.jboss.org/jira/browse/JBSEAM-4331 Project: Seam Issue Type: Task Components: Drools Affects Versions: 2.2.0.GA Reporter: Anthony Whitford I am surprised to see a very old xstream dependency baked into the root pom: <dependency> <groupId>xstream</groupId> <artifactId>xstream</artifactId> <version>1.1.3</version> </dependency> This version was released January 13, 2006. The latest version is 1.3.1 which was released December 6, 2008. Note that according to JBRULES-1128 at least version 1.2.2 is required. Would prefer to see: <dependency> <groupId>com.thoughtworks.xstream</groupId> <artifactId>xstream</artifactId> <version>1.3.1</version> </dependency> See: http://repo2.maven.org/maven2/com/thoughtworks/xstream/xstream/1.3.1/ (For those of us using a new version of XStream in our projects with the current groupId, the legacy dependency causes issues if you don't exclude it.) -- 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

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4067) ELSupport.coerceToType modifies BigDecimal Values

by Pete Muir (JIRA)

ELSupport.coerceToType modifies BigDecimal Values ---------------------------------------------------- Key: JBSEAM-4067 URL: https://jira.jboss.org/jira/browse/JBSEAM-4067 Project: Seam Issue Type: Bug Components: EL Reporter: Pete Muir Assignee: Norman Richards Priority: Critical See https://issues.apache.org/bugzilla/show_bug.cgi?id=43656 -- 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

16 years, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4330) I18n documentation should include Seam Manager uri-encoding parameter used to encode URLs and page parameters

by Julien Kronegg (JIRA)

I18n documentation should include Seam Manager uri-encoding parameter used to encode URLs and page parameters ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4330 URL: https://jira.jboss.org/jira/browse/JBSEAM-4330 Project: Seam Issue Type: Feature Request Components: Documentation Issues Affects Versions: 2.2.0.CR1, 2.1.2.GA Environment: http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/doc/Seam... http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_2/doc/Seam... Reporter: Julien Kronegg Priority: Minor Seam Manager default encoding for URL and their parameters is UTF-8, which cause some issues for i18n, e.g. if the charset is ISO-8859-1. See JBSEAM-2710 and JBSEAM-3148. While source code has been corrected in JBSEAM-2710, the documentation is still missing this new configuration, so a lot of users have problems using accented characters in page.xml parameters (param tag), e.g. : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4054383 http://www.seamframework.org/Community/PagesxmlNavigationEncodingProblem http://seamframework.org/Community/EncodingProblemWithGermanSpecialCharac... It would be nice to add a paragraph in section "Other encoding settings" of chapter "Internationalization, localization and themes": "If your URLs or page parameters specified in page.xml contains charset sensitive characters like accented characters, you should change the URI encoding in Seam's Manager component of components.xml: <core:manager uri-encoding="ISO-8859-1" ...>" -- 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

16 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4328) Provide examples of using Seam debug under high load in ref doc

by asookazian (JIRA)

Provide examples of using Seam debug under high load in ref doc --------------------------------------------------------------- Key: JBSEAM-4328 URL: https://jira.jboss.org/jira/browse/JBSEAM-4328 Project: Seam Issue Type: Feature Request Components: Documentation Issues Affects Versions: 2.1.2.GA Environment: n/a Reporter: asookazian Priority: Minor >From 2.8. Seam and incremental hot deployment in ref doc: "You may see errors if the system is placed under any load and debug is enabled." Need to be more specific and/or provide sample errors. -- 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

16 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4327) Add example code of how to use Seam interceptors with JavaBean components in ref doc

by asookazian (JIRA)

Add example code of how to use Seam interceptors with JavaBean components in ref doc ------------------------------------------------------------------------------------ Key: JBSEAM-4327 URL: https://jira.jboss.org/jira/browse/JBSEAM-4327 Project: Seam Issue Type: Feature Request Components: Documentation Issues Affects Versions: 2.1.2.GA Environment: Windows Seam 2.1.2.GA Sun JDK 1.5 Reporter: asookazian Priority: Minor Fix For: The future Attachments: ProfilingInterceptor.java The Seam reference documentation needs an example of how to use Seam interceptors with JavaBean components. There is the following reference in 6.11: "You can even use Seam interceptors with JavaBean components, not just EJB3 beans!" but there is no example. I have provided a working example using a custom ProfilingInterceptor which outputs that a business method has begun execution as well as execution time for that method. -- 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

16 years, 8 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4242) EAR projects for GlassFish generated by seam-gen not working

by Chris Dunphy (JIRA)

EAR projects for GlassFish generated by seam-gen not working ------------------------------------------------------------ Key: JBSEAM-4242 URL: https://jira.jboss.org/jira/browse/JBSEAM-4242 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA, 2.1.2.CR2 Environment: Had the same problem on Windows, Ubuntu Linux 9.04 and Mac OS X Leopard Reporter: Chris Dunphy I started a really simple seam-gen project with GlassFish 2.1 and MySQL using seam 2.1.2. This is the one Entity class I created: package dunphy.chris.hello.model; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.Id; @Entity public class User { private long id; private String username; private String password; @Id @GeneratedValue public long getId() { return id; } public void setId(long id) { this.id = id; } public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } } I ran seam setup, seam create-project. Here is my seam-gen.properties file: #Generated by seam setup #Fri Jun 12 14:34:39 MDT 2009 hibernate.connection.password=hello workspace.home=/Users/cdunphy/Code/Seam hibernate.connection.dataSource_class=com.mysql.jdbc.jdbc2.optional.MysqlDataSource model.package=dunphy.chris.hello.model hibernate.default_catalog=hello driver.jar=/Users/cdunphy/Code/mysql-connector-java-5.1.7/mysql-connector-java-5.1.7-bin.jar action.package=dunphy.chris.hello.action test.package=dunphy.chris.hello.test database.type=mysql richfaces.skin=glassX glassfish.domain=domain1 hibernate.default_schema.null= database.drop=n project.name=hello hibernate.connection.username=hello glassfish.home=/Users/cdunphy/glassfish hibernate.connection.driver_class=com.mysql.jdbc.Driver hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider jboss.domain=default project.type=ear icefaces.home= database.exists=n jboss.home=/Users/cdunphy/jboss/jboss-5.1.0.GA driver.license.jar= hibernate.dialect=org.hibernate.dialect.MySQLDialect hibernate.connection.url=jdbc\:mysql\://localhost\:3306/hello icefaces=n I ran seam generate-ui to create a view based on the one entity class that belongs to the project. So far so good. I ran ant gf-prepare, and I made the following changes to the seam-gen project (as per the glassfish-readme.txt file): /resources/WEB-INF/web.xml: <ejb-local-ref> <ejb-ref-name>hello/AuthenticatorBean/local</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home/> <local>rcd.hello.action.Authenticator</local> </ejb-local-ref>  <persistence-unit-ref> <persistence-unit-ref-name>hello/pu</persistence-unit-ref-name>  <persistence-unit-name>hello</persistence-unit-name> </persistence-unit-ref> /resources/META-INF/persistence-dev.xml: <?xml version="1.0" encoding="UTF-8"?>  <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0"> <persistence-unit name="hello"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>helloDatasource</jta-data-source>   <jar-file>../../hello.jar</jar-file> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.hbm2ddl.auto" value="update"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.format_sql" value="true"/> <property name="hibernate.default_catalog" value="hello"/> <property name="jboss.entity.manager.factory.jndi.name" value="java:/helloEntityManagerFactory"/> </properties> </persistence-unit> </persistence> Ok, so far its great. I can run gf-explode and the project is deployed to GlassFish no problem. I can use the default authenticator session component to login if I supply the admin username and the blank password. I can also browse the CRUD pages that are generated just fine. Here is where the problems start. First I add a username/password to the database. Then if I change AuthenticatorBean to do this: package dunphy.chris.hello.action; import javax.ejb.Stateless; import javax.persistence.EntityManager; import org.jboss.seam.annotations.In; import org.jboss.seam.annotations.Logger; import org.jboss.seam.annotations.Name; import org.jboss.seam.log.Log; import org.jboss.seam.security.Credentials; import org.jboss.seam.security.Identity; import dunphy.chris.hello.model.User; @Stateless @Name("authenticator") public class AuthenticatorBean implements Authenticator { @Logger private Log log; @In EntityManager entityManager; @In Identity identity; @In Credentials credentials; public boolean authenticate() { log.info("authenticating {0}", credentials.getUsername()); User user = (User) entityManager.createQuery( "select u from User u where username = :username") .setParameter("username", credentials.getUsername()) .getSingleResult(); if (user == null) { log.error("no matching user found in the database"); return false; } if (user.getPassword().equals(credentials.getPassword())) { log.info("Authentication successful for user {0}", credentials .getUsername()); return true; } log.info("Invalid password"); return false; } } It doesn't work. I get the following exception: [#|2009-06-12T14:43:37.641-0600|INFO|sun-appserver2.1|javax.enterprise.system.container.e jb|_ThreadID=19;_ThreadName=httpSSLWorkerThread-8080-0;| javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested excepti on is: java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java: comp/env/hello/pu java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:comp/en v/hello/pu at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFr omJndiOrValueBinding(ManagedPersistenceContext.java:245) at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(Managed PersistenceContext.java:78) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedP ersistenceContext.java:107) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j ava:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) at org.jboss.seam.Component.callComponentMethod(Component.java:2249) at org.jboss.seam.Component.unwrap(Component.java:2275) at org.jboss.seam.Component.getInstance(Component.java:2041) at org.jboss.seam.Component.getInstance(Component.java:1983) at org.jboss.seam.Component.getInstance(Component.java:1977) at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2349) at org.jboss.seam.Component.getValueToInject(Component.java:2301) at org.jboss.seam.Component.injectAttributes(Component.java:1736) at org.jboss.seam.Component.inject(Component.java:1554) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.jav a:61) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.j ava:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterce ptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.j This is a dead-simple EAR based project based clean right off of Seam gen. I can't seem to get the seam managed persistence to work with EJB/seam session bean components on glassfish, not off the project structure created by seam-gen. I try this workaround: Okay, so yeah, the way seam-gen sets up the project doesn't work for EAR projects on GlassFish. I had to take the following steps to fix it (starting from the point where you run seam-gen and follow the instructions in glassfish-readme.txt): 1. Disable the ant target that moves the persistence.xml file to /WEB-INF/classes/META-INF: <target name="gf-cleanup-ear" if="project.ear">  </target> 2. Comment out the persistence-unit-ref entry in web.xml 3. Don't try to lookup the seam managed context using @puJndiName@ in components.xml... instead use this: <persistence:entity-manager-factory name="entityManagerFactory" persistence-unit-name="hello" /> <persistence:managed-persistence-context name="entityManager" auto-create="true" entity-manager-factory="#{entityManagerFactory}" 4. Add ejb-transactions as well to components.xml (you need to add stuff to the namespace headers, see link at the end): <tx:ejb-transaction /> 5. Comment out the jboss.entity.manager.factory.jndi.name property in the persistence-dev.xml file. 6. Add the following property to persistence-dev.xml: <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.SunONETransactionManagerLookup" /> 7. Add an EJB ref for org.jboss.seam.transaction.LocalEjbSynchronizations to web.xml: <ejb-local-ref> <ejb-ref-name>hello/EjbSynchronizations/local</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home /> <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local> </ejb-local-ref> This fixes the persistence unit issue, but it seems to break the ability to use @In to inject session bean components. -- 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

16 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4322) Add JSF 1.2.13

by Shervin Asgari (JIRA)

Add JSF 1.2.13 -------------- Key: JBSEAM-4322 URL: https://jira.jboss.org/jira/browse/JBSEAM-4322 Project: Seam Issue Type: Feature Request Components: JSF Controls, JSF Integration Affects Versions: 2.2.0.CR1 Reporter: Shervin Asgari Maybe you can upgrade to the latest JSF release for 2.2.0.GA ?? https://javaserverfaces.dev.java.net/servlets/NewsItemView?newsItemID=7403 -- 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

16 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4274) hibernate-core.jar missing in Seam examples deployed to Tomcat6

by Jozef Hartinger (JIRA)

hibernate-core.jar missing in Seam examples deployed to Tomcat6 --------------------------------------------------------------- Key: JBSEAM-4274 URL: https://jira.jboss.org/jira/browse/JBSEAM-4274 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.CR1 Reporter: Jozef Hartinger Assignee: Norman Richards Fix For: 2.2.0.CR1 hibernate.jar is no longer being copied to WEB-INF/lib since it has been renamed to hibernate-core.jar in the dist. Jar names specified in examples/{hibernate, jpa}/build-*.xml need to be changed. -- 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

16 years, 8 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4304) Seam Text add new line when it finds html tag

by David Herrera Alonso (JIRA)

Seam Text add new line when it finds html tag ------------------------------------------------- Key: JBSEAM-4304 URL: https://jira.jboss.org/jira/browse/JBSEAM-4304 Project: Seam Issue Type: Bug Components: Seam Text Affects Versions: 2.1.0.SP1 Environment: Ubuntu Linux kernel 2.6.28-13-generic i686 ; Seam 2.1.0 SP1 ; Web browser Opera 10 beta2, Firefox 3.0.11 Reporter: David Herrera Alonso Setting value for <s:formattedText> Seam Text tag, reading it from database (for example), the output add new line if value has some characters with bold html tag. Let's see it with this input: This is text with bold format and this is normal format. After <s:formattedText> processed this input, the output is: This is text with bold format //(with bold format, this is ok) and this is normal format. //on a new line and this isn't ok) This only happens when there are some bold text using (or tag too). If instead of , we put or another style html tag, this strange behaviour doesn't appear. Let's see it: This is cursive text and this is normal text. And output will be: This is cursive text (in cursive format) and this is normal text. I commented it on various threads: http://seamframework.org/Community/BoldSeamTextForcesNewline http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243159#4243159 https://jira.jboss.org/jira/browse/RF-5777 (someone tells about richfaces rich editor bug, but this behaviour with bold and new line don't have relation with richfaces) -- 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

16 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4307) Spring example needs cglib library

by Ondrej Skutka (JIRA)

Spring example needs cglib library ---------------------------------- Key: JBSEAM-4307 URL: https://jira.jboss.org/jira/browse/JBSEAM-4307 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Environment: JBoss 5.1.0.GA, Sun JDK 6 Reporter: Ondrej Skutka Spring example crashes after clicking "Register new user" and complains about not having cglib library: org.springframework.aop.framework.AopConfigException: Cannot proxy target class because CGLIB2 is not available. Add CGLIB to the class path or specify proxy interfaces. After adding cglib-nodeps.jar into WEB-INF/lib library of the war, everything works. -- 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

16 years, 8 months

2
2
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 July 2009