June 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4238) Better PDF integration with rich:edtor control

by Robert Morse (JIRA)

Better PDF integration with rich:edtor control ---------------------------------------------- Key: JBSEAM-4238 URL: https://jira.jboss.org/jira/browse/JBSEAM-4238 Project: Seam Issue Type: Feature Request Components: PDF Environment: 2.1.2.GA Reporter: Robert Morse Creating PDFs with content out of a database or user input is a very powerful Seam feature. Currently, the rich:editor control coupled with the p:html or p:html / s:formattedText tags comes close to allowing a user to create relatively complex PDF output. However, there isn't consistency between what the rich:editor creates and what Seam PDF can produce. For example, saving rich:editor input as Seam Text disables the ability to create ordered or unordered lists. Saving it as html, loses the ability to define font characteristics. Possibly a quick fix would be to allow Seam PDF pages to reference a CSS. Another approach might be to modify the s:formattedText tag to handle what the rich:editor creates. I have a strong interest in this, and would be willing to try some solutions if I could get pointed in the correct direction. Thanks. -- 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, 4 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1572) Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly)

by Alex Savitsky (JIRA)

Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly) --------------------------------------------------------------------------- Key: JBSEAM-1572 URL: http://jira.jboss.com/jira/browse/JBSEAM-1572 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Alex Savitsky Priority: Minor ui:decorate preserves its children, while s:decorate groups them as one instead. This makes s:decorate unusable for form fields laid out using h:panelGrid, as there's no way to separate the field label from the field itself (they are grouped together). -- 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, 4 months

9
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3710) For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate

by Pete Muir (JIRA)

For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate ----------------------------------------------------------------------------------- Key: JBSEAM-3710 URL: https://jira.jboss.org/jira/browse/JBSEAM-3710 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 This is possible only in JavaBeans as the HttpSession is passed as an arguement to the sessionWillPassivate/sessionWillActivate call, and we can store the conversationId in @AroundInvoke method. In EJBs, the passivation/activation happens independently of the HttpSession. This should be a performance improvement, @PrePassivate (serialize out entities) will be called just as much, but @PostActivate will be called a lot less. -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2093) Optimize getting Id in Seam code for better performance

by Mikhail Grushinskiy (JIRA)

Optimize getting Id in Seam code for better performance ------------------------------------------------------- Key: JBSEAM-2093 URL: http://jira.jboss.com/jira/browse/JBSEAM-2093 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy This sequence of calls (used in PersistenceProvider) is quite slow Entity.forClass(bean.getClass()).getIdentifier(bean); 1) Entity.forClass() is reading annotations using JDK 5 methods (JDK 5 annotation reading is not that fast). Can it be cached? 2) JDK 5 reflection is used to get bean id (which is slower than optmized reflection with cglib) 3) There could be other reasons as well. I think repetitive calling of this sequence under profiler will give better picture. from PersistenceProvider.java /** * Get the value of the entity identifier attribute. * * @param bean a managed entity instance */ public Object getId(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getIdentifier(bean); } /** * Get the name of the entity * * @param bean * @param entityManager */ public String getName(Object bean, EntityManager entityManager) { return Entity.forClass(bean.getClass()).getName(); } /** * Get the value of the entity version attribute. * * @param bean a managed entity instance */ public Object getVersion(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getVersion(bean); } -- 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, 4 months

7
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4243) resteasy-2.1.xsd in jboss-seam-resteasy.jar and resteasy-2.1.xsd at http://jboss.com/products/seam/resteasy-2.1.xsd are not the same

by Matthew Bowman (JIRA)

resteasy-2.1.xsd in jboss-seam-resteasy.jar and resteasy-2.1.xsd at http://jboss.com/products/seam/resteasy-2.1.xsd are not the same ------------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-4243 URL: https://jira.jboss.org/jira/browse/JBSEAM-4243 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Matthew Bowman Attachments: resteasy-2.1.xsd.patch The new Seam RESTeasy integration documentation shows how to add the resteasy namespace to components.xml and how to enable the session context for REST requests: <resteasy:application destroy-session-after-request="false" /> The resteasy-2.1.xsd schema located at http://jboss.com/products/seam/resteasy-2.1.xsd seems out-of-date when compared to the resteasy-2.1.xsd contained in the jboss-seam-resteasy.jar integration library. -- 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, 4 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4174) Seam Conversation Issue with richmenu

by Tony Herstell (JIRA)

Seam Conversation Issue with richmenu ------------------------------------- Key: JBSEAM-4174 URL: https://jira.jboss.org/jira/browse/JBSEAM-4174 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.2.CR1 Environment: Win XP64 Pro, Ubuntu Reporter: Tony Herstell http://www.jboss.org/index.html?module=bb&op=viewtopic&t=149397 http://www.seamframework.org/Community/ConversationQuestion http://www.seamframework.org/Community/ProblemEndingConversationInRichFac... http://www.seamframework.org/Community/HowToUseSlinkInRichmenuItem ------ In Summary RF know of the problem but, I believe, are looking to seam to fix this... <rich:menuItem submitMode="ajax" value="#{messages.menu_button_facilities}" action="#{facilitiesController.enter}" > <s:conversationPropagation type="none"/> </rich:menuItem> Basically the above code should work but doesn't. Seam/RF do not honour the conversationPropagation Tag... so the current conversation is not suspended.. thus when you try to start the new conversation (from the menu click you just did) BANG!. The error you get is: The conversation ended, timed out or was processing another request The live site to see this is: http://www.selwynequestriancentre.co.nz/site/home.seam click register then click the menu for "home page" which goes from a conversation to a non-conversation click to enter a competition (actually all closed at present but should be open again next week) and then click to register to go from conversation to another conversation. -- 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, 4 months

1
1
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, 4 months

3
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, 5 months

1
1
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, 5 months

4
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4078) Jar locking during of component initialization on Windows

by Andrey Lomakin (JIRA)

Jar locking during of component initialization on Windows --------------------------------------------------------- Key: JBSEAM-4078 URL: https://jira.jboss.org/jira/browse/JBSEAM-4078 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows 2000, Java(TM) SE Runtime Environment (build 1.6.0_13-b03), GlassFish v3 Prelude (build b28c) Reporter: Andrey Lomakin JARs that contain components.xml are locked till server shutdown and can not be removed after application undeploy on Windows. As I understend following snippet of code in method org.jboss.seam.init.Initialization#initComponentsFromXmlDocuments: InputStream stream = url.openStream(); log.debug("reading " + url); try { installComponentsFromXmlElements(XML.getRootElement(stream), replacements); } finally { Resources.closeStream(stream); } should be replaced by URLConnection connection = url.openConnection(); connection.setUseCaches(false); InputStream stream = url.openStream(); // and so on... If cashes will not be switched of file will be opened but never closed. Returned instance of InputStream interface is sun.net.www.protocol.jar.JarURLConnection,JarURLInputStream that closes opened jar file only if cashes are not used. class JarURLInputStream extends java.io.FilterInputStream { 103 JarURLInputStream (InputStream src) { 104 super (src); 105 } 106 public void close () throws IOException { 107 try { 108 super.close(); 109 } finally { 110 if (!getUseCaches()) { 111 jarFile.close(); 112 } 113 } 114 } 115 } -- 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, 5 months

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 June 2009