December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3766) examples is not working under tomcat 6.0

by Alexey Kakunin (JIRA)

examples is not working under tomcat 6.0 ---------------------------------------- Key: JBSEAM-3766 URL: https://jira.jboss.org/jira/browse/JBSEAM-3766 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.SP1 Environment: CentOs 5.2, java 1.6.10_u10, tomcat 6.0.18 Reporter: Alexey Kakunin Priority: Minor just following to documentation, configured tomcat.home in build.properties,switched to example project folder (for example registration) and called ant tomcat.deploy Project built and deployed to tomcat, but during initialization followed error generated: java.lang.NoClassDefFoundError: javassist/util/proxy/MethodFilter at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:243) at org.jboss.seam.contexts.Lifecycle.endApplication(Lifecycle.java:56) at org.jboss.seam.contexts.ServletLifecycle.endApplication(ServletLifecycle.java:135) at org.jboss.seam.servlet.SeamListener.contextDestroyed(SeamListener.java:39) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3882) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4523) Looks like javassist should be added into depepndencies -- 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

15 years, 5 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3457) Use dynamic proxies to implement delegation in persistence

by Emmanuel Bernard (JIRA)

Use dynamic proxies to implement delegation in persistence ---------------------------------------------------------- Key: JBSEAM-3457 URL: https://jira.jboss.org/jira/browse/JBSEAM-3457 Project: Seam Issue Type: Feature Request Components: Search Reporter: Emmanuel Bernard Fix For: 2.1.1.CR1 Today, when someone throw the new Hibernate Search version or a new Hibernate Core version having more methods in (FullText)Session, Seam blows up as (FullText)HibernateSessionProxy and (FullText)EntityManagerProxy directly implement those interfaces. An alternative approach could be to reimplement those proxies as dynamic proxies passing through unknown methods. Either the JDK dynamic proxy approach or the Javassist equivalent can be used. -- 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

15 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3773) Upgrade to RichFaces 3.2.2.SR1

by Jay Balunas (JIRA)

Upgrade to RichFaces 3.2.2.SR1 ------------------------------ Key: JBSEAM-3773 URL: https://jira.jboss.org/jira/browse/JBSEAM-3773 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Priority: Critical Fix For: 2.1.1.CR2 RichFaces team released 3.2.2.SR1 on Nov 3rd which fixes the critical security issue RF-4713. We should upgrade for the 2.1.1.CR2 so that any issue are found prior to GA. -- 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

15 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3741) It is now invalid to write an an EL expression inside view-id!

by Francisco Jose Peredo Noguez (JIRA)

It is now invalid to write an an EL expression inside view-id! -------------------------------------------------------------- Key: JBSEAM-3741 URL: https://jira.jboss.org/jira/browse/JBSEAM-3741 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez I am hitting this issue JBIDE-3248, at first I thougth it was an incompatiblity problem between JBoss Tools 2.1.2, and Seam 2.1.x, but now I think it is an error in http://jboss.com/products/seam/pages-2.1.xsd. In pages-2.1.xsd we have this code (that didnt exist in 2.0): <xs:simpleType name="view-id"> <xs:restriction base="xs:string"> <xs:pattern value="(/.*)|\*"/> </xs:restriction> </xs:simpleType> That is limiting view-id by preventing it from using EL expressions inside it, but EL expression do work inside view-id: <navigation from-action="#{someEntityHome.persist}"> <rule if-outcome="persisted" if="#{not empty someEntityFrom}"> <end-conversation/> <redirect view-id="{#someEntityFrom}"/> </rule> <rule if-outcome="persisted" if="#{empty someEntityFrom}"> <end-conversation/> <redirect view-id="/Crud/SomeEntityList.xhtml"/> </rule> </navigation> The line <redirect view-id="{#someEntityFrom}"/> is being reported as an error, but it is perfectly fine. I think the <xs:pattern value="(/.*)|\*"/> specified for view-id in pages-2.1.xsd is an error. -- 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

15 years, 5 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3713) Drop the OC4J chapter from the Reference Guide

by Jay Balunas (JIRA)

Drop the OC4J chapter from the Reference Guide ---------------------------------------------- Key: JBSEAM-3713 URL: https://jira.jboss.org/jira/browse/JBSEAM-3713 Project: Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.SP1 Reporter: Jay Balunas Fix For: 2.1.1.CR2 The OC4J reference guide chapter was written for OC4J 11g. This has been dropped by Oracle because they acquired BEA and are shipping WebLogic now. OC4J 10.X is effectively an end of life phase product and so we will not be updating the reference guide chapter for it. We will drop the OC4J chapter from the reference guide. -- 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

15 years, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3745) org.jboss.seam.util.Strings improvements

by Anthony Whitford (JIRA)

org.jboss.seam.util.Strings improvements ---------------------------------------- Key: JBSEAM-3745 URL: https://jira.jboss.org/jira/browse/JBSEAM-3745 Project: Seam Issue Type: Patch Components: Core Affects Versions: 2.1.1.CR1 Reporter: Anthony Whitford I noticed some improvements that could be made to the core Strings utility class. 1. The isEmpty method is inefficient: public static boolean isEmpty(String string) { return string == null || string.trim().length() == 0; } See http://pmd.sourceforge.net/rules/strings.html#InefficientEmptyStringCheck I think you really want something closer to Apache Commons Lang StringUtils.isBlank: - http://commons.apache.org/lang/api-release/org/apache/commons/lang/String... - http://svn.apache.org/viewvc/commons/proper/lang/trunk/src/java/org/apach... 2. Consider the code: public static String toString(String sep, Object... objects) { if (objects.length==0) return ""; StringBuilder builder = new StringBuilder(); for (Object object: objects) { builder.append(sep).append(object); } return builder.substring(2); } The magic number 2 passed to the substring looks suspicious. I think this assumes that sep has a length of 2. This utility should avoid making assumptions. A similar function avoids the assumption by using sep.length: public static String toString(String sep, Class... classes) { if (classes.length==0) return ""; StringBuilder builder = new StringBuilder(); for (Class clazz: classes) { builder.append(sep).append( clazz.getName() ); } return builder.substring(sep.length()); } Overall, the hard-coded 2's should be replaced with sep.length. 3. StringBuilder is used, but some StringBuffer remains -- those could be replaced. 4. Some appends on one character strings could be replaced with char versions. (See http://pmd.sourceforge.net/rules/strings.html#AppendCharacterWithChar ). -- 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

15 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3588) seamspace example needs to use @Begin(join=true) for some actions

by Jay Balunas (JIRA)

seamspace example needs to use @Begin(join=true) for some actions ----------------------------------------------------------------- Key: JBSEAM-3588 URL: https://jira.jboss.org/jira/browse/JBSEAM-3588 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK6 AS 5 CR2 Reporter: Jay Balunas Assignee: Shane Bryzak Priority: Minor Fix For: 2.1.1.CR1 If you click on create user or create role twice you get the exception below in the log Caused by: java.lang.IllegalStateException: begin method invoked from a long-running conversation, try using @Begin(join=true) on method: createRole at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:47) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) -- 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

15 years, 5 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3749) login-required should support EL

by Przemyslaw Jaskierski (JIRA)

login-required should support EL -------------------------------- Key: JBSEAM-3749 URL: https://jira.jboss.org/jira/browse/JBSEAM-3749 Project: Seam Issue Type: Feature Request Reporter: Przemyslaw Jaskierski There is a lot of scenarios which are impossible to accomplish without EL support in login-required attribute. Example: some pages should be freely accessed by recognized users (users who have e.g. you cookie set in it), but require login or registration from unrecognized users. Conditional check against e.g. session-scoped bean in login-required would be clean an elegant way to achieve 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

15 years, 5 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008