September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3399) java.lang.NullPointerException at org.jboss.seam.deployment.HotDeploymentStrategy.getScannedComponentClasses(HotDeploymentStrategy.java:162)

by Thomas März (JIRA)

java.lang.NullPointerException at org.jboss.seam.deployment.HotDeploymentStrategy.getScannedComponentClasses(HotDeploymentStrategy.java:162) -------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3399 URL: https://jira.jboss.org/jira/browse/JBSEAM-3399 Project: Seam Issue Type: Bug Components: Core Environment: Windows, Tomcat 6.0.18 Reporter: Thomas März Priority: Minor Since about a week I am getting the following Stacktrace with jboss-seam-2.1.0-SNAPSHOT.jar and <core:init debug="true" transaction-management-enabled="false" /> java.lang.NullPointerException org.jboss.seam.deployment.HotDeploymentStrategy.getScannedComponentClasses(HotDeploymentStrategy.java:162) org.jboss.seam.deployment.GroovyHotDeploymentStrategy.getScannedComponentClasses(GroovyHotDeploymentStrategy.java:71) org.jboss.seam.init.Initialization.installHotDeployableComponents(Initialization.java:698) org.jboss.seam.init.Initialization.redeploy(Initialization.java:685) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:50) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) When creating the folder /WEB-INF/dev the exception disappears. -- 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, 9 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3433) Lost facesMessage on redirect to the former page

by liu lei (JIRA)

Lost facesMessage on redirect to the former page ------------------------------------------------ Key: JBSEAM-3433 URL: https://jira.jboss.org/jira/browse/JBSEAM-3433 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.2.SP1 Environment: tomcat 6, jdk1.5.0.15,Seam 2.0.2sp,richfaces 3.2.2GA Reporter: liu lei Priority: Critical http://www.seamframework.org/Community/LostFacesMessageOnRedirect I explain what I encountered in the forum. For now, I just save the FacesMessages instance in the session scope to solve this problem. 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

15 years, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3250) Business process variable is not resolved in process definition EL

by Ivan B (JIRA)

Business process variable is not resolved in process definition EL ------------------------------------------------------------------ Key: JBSEAM-3250 URL: https://jira.jboss.org/jira/browse/JBSEAM-3250 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.2.SP1 Environment: jbpm-jpdl-3.2.3 jboss-4.2.2.GA Reporter: Ivan B Business process variable, declared in a Seam component as @Out(scope = ScopeType.BUSINESS_PROCESS, required = false) private String bannersCount; does not resolve in jPDL <decision name="check banner list" expression="#{bannersCount}"> <transition to="select stub" name="no banners found"></transition> <transition to="select banner" name="banners found"></transition> </decision> with the following exception 13:28:46,887 FATAL [application] javax.ejb.EJBTransactionRolledbackException: Identity 'bannersCount' does not reference a MethodExpression instance, returned type: java.lang.String javax.faces.el.EvaluationException: javax.ejb.EJBTransactionRolledbackException: Identity 'bannersCount' does not reference a MethodExpression instance, returned type: java.lang.String -- 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, 9 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3432) Seam 2.0.x needs SeamExpressionEvaluator patch to integrate correctly with jBPM

by Luis Tama (JIRA)

Seam 2.0.x needs SeamExpressionEvaluator patch to integrate correctly with jBPM ------------------------------------------------------------------------------- Key: JBSEAM-3432 URL: https://jira.jboss.org/jira/browse/JBSEAM-3432 Project: Seam Issue Type: Bug Components: BPM, EL Affects Versions: 2.0.3.CR1, 2.0.2.SP1 Environment: jbpm-jpdl-3.2.3 jboss-4.2.2.GA Reporter: Luis Tama Please include the fix from SVN Revision 8710 for SeamExpressionEvaluator in next Seam 2.0.3 CR or GA release. (See: http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/bpm/Se...) The patch submitted by Pete for JBSEAM-3250 is included in Seam 2.1.0 and works fine. I merged this patch into my Seam 2.0.2.SP1 and it also worked without problems. The patch is just a code reordering, so I think it will not be hard to merge in the next 2.0.x release. Please consider that it is not fair that only Seam 2.1.0 has the fix, while the 2.0.x branch remains with this bug described in https://jira.jboss.org/jira/browse/JBSEAM-3250, which affects Seam-jBPM integration via EL expressions. -- 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, 9 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3045) urlrewritefilter breaks basic authentication

by Stephane Epardaud (JIRA)

urlrewritefilter breaks basic authentication -------------------------------------------- Key: JBSEAM-3045 URL: http://jira.jboss.com/jira/browse/JBSEAM-3045 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Stephane Epardaud In web.xml, if I configure the urlwritefilter before the seamfilter, any basic authentication defined in components.xml with <web:authentication-filter url-pattern="/feed/*" auth-type="basic" realm="MyRealm" precedence="0"/> will be ignored. That is, pages in the /feed/* url space will not ask for authentication, and any security restrictions requiring those pages to be accessed as logged in users will throw exceptions. If the urlrewritefilter is defined within the seamfilter, then all works well, except that I'm not sure outboud rewrite rules will work correctly. I haven't found any documentation relating the order in which these filters must be declared in the Seam documentation. If this is not a bug, perhaps it would be nice to document it? -- 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

15 years, 9 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3427) Seam Components missing @Install(precedence = BUILT_IN) annotation

by Scott Olcott (JIRA)

Seam Components missing @Install(precedence = BUILT_IN) annotation ------------------------------------------------------------------- Key: JBSEAM-3427 URL: https://jira.jboss.org/jira/browse/JBSEAM-3427 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Reporter: Scott Olcott Component classes in the following packages should have @Install(precedence = BUILT_IN) annotation org.jboss.seam.security.management.action org.jboss.seam.security.permission.action -- 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, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3334) Icefaces example login does not work on JDK5

by Jozef Hartinger (JIRA)

Icefaces example login does not work on JDK5 -------------------------------------------- Key: JBSEAM-3334 URL: https://jira.jboss.org/jira/browse/JBSEAM-3334 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.SP1, 2.1.0.BETA1 Environment: JDK5 update 16 JBoss AS 4.2.3 Fedora 9 Reporter: Jozef Hartinger Log in does not work. After submiting login data page is just reloaded. No exception is present in server log. On JDK6 login works fine -- 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, 9 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3326) seam-gen icefaces application throws a 404 when creating a new Person following release process

by Jay Balunas (JIRA)

seam-gen icefaces application throws a 404 when creating a new Person following release process ----------------------------------------------------------------------------------------------- Key: JBSEAM-3326 URL: https://jira.jboss.org/jira/browse/JBSEAM-3326 Project: Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Gregory Dick Fix For: 2.1.0.BETA2 Follow the release process to create a base set of tables and generate entities. Selecting "save" when creating a new person throws 404 and trying to access : "http://localhost:8080/seamgenIce/iceSubmit('personeditForm');" Possibly related selected save when creating a vehicle does nothing. -- 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, 9 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3327) seam-gen icefaces "new-form" submit does nothing

by Jay Balunas (JIRA)

seam-gen icefaces "new-form" submit does nothing ------------------------------------------------ Key: JBSEAM-3327 URL: https://jira.jboss.org/jira/browse/JBSEAM-3327 Project: Seam Issue Type: Bug Components: ICE Faces Integration Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Gregory Dick Fix For: 2.1.0.BETA2 Follow release process, and create a new form called hello. When you submit the form nothing happens. - no errors, no exception, just nothing. -- 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, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3366) org.jboss.seam.util.Resources#getResourceAsStream() fails with newer versions of Tomcat, page.xml files aren't found

by Thomas März (JIRA)

org.jboss.seam.util.Resources#getResourceAsStream() fails with newer versions of Tomcat, page.xml files aren't found -------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3366 URL: https://jira.jboss.org/jira/browse/JBSEAM-3366 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.BETA1 Environment: Tomcat 6.0.16 on Fedora Reporter: Thomas März With <core:init debug="true" /> the reloading of page.xml files fails with the log entry: no pages.xml file found: customer/phot/list.page.xml And since the resource doesn't start with a slash, list.page.xml can't be loaded. Quoted from https://issues.apache.org/bugzilla/show_bug.cgi?id=43241 Say for example, you have a file style.css deployed in your context. The call to ServletContext.getResourceAsStream("style.css") returns an input stream. This is not correct behavior. The spec (2.3) says: > The path must be specified according to > the rules given in getResource. getResource() says: > The path must begin with a "/" and is interpreted > as relative to the current context root. My reading of these two things is that getResourceAsStream("style.css") should return null, not an input stream to the file. I got bit on this because my app behavior changed (broke) when ran on the current version of WebSphere. -- 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, 9 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2008