March 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3771) URL Rewriting Not Occurring

by Dave Everson (JIRA)

URL Rewriting Not Occurring --------------------------- Key: JBSEAM-3771 URL: https://jira.jboss.org/jira/browse/JBSEAM-3771 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.CR1 Environment: Windows Vista, JBoss 4.2.0, JRockit 1.5 Reporter: Dave Everson We have just updated Seam to 2.1.1CR1 We started to use the rewrite functionality within pages.xml. We have the following pages defined: <page view-id="/pages/account/check.xhtml"> <rewrite pattern="/newFamilyAccount" /> <begin-conversation join="true"/> <action execute="#{registerFamily.startEdit}"/> <navigation from-action="#{registerFamily.doAccountCheck}"> <rule if-outcome="exists"> <redirect view-id="/pages/account/existing.xhtml"/> </rule> <rule if-outcome="new"> <redirect view-id="/pages/account/new.xhtml"/> </rule> </navigation> </page> <page view-id="/pages/account/existing.xhtml"> <rewrite pattern="/existingAccounts" /> <begin-conversation join="true"/> </page> We are able to access /newFamilyAccount without issue and a conversation is started After entering data that already exists in the database, we should be taken to the /existingAccounts (/pages/account/existing.xhtml) view. We are taken to the view, however the URL shows: https://localhost/a/pages/account/existing.seam?cid=9. We have tried several things and can't see to ever have the rewritten URL appear. Does anyone have any suggestions on what we are doing incorrectly. 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

17 years

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3726) Methods with an InvocationContext parameter annotated with javax.ejb.PostActivate cause a validation exception in WebSphere v7.0

by Denis Forveille (JIRA)

Methods with an InvocationContext parameter annotated with javax.ejb.PostActivate cause a validation exception in WebSphere v7.0 --------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3726 URL: https://jira.jboss.org/jira/browse/JBSEAM-3726 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.0.SP1 Environment: WebSphere v7.0 Reporter: Denis Forveille When starting our app in WebSphere v7.0 with seam v2.1.0.SP1, we receive the exception below Is it possible that annotation "javax.ejb.PostActivate" is used instead of "org.jboss.seam.annotations.intercept.PostActivate" annotation and that the former does not accept any parameter for the annotated method (At least in WebSphere v7.0) and the latter does... The method in question is declared as @PostActivate public void postActivate(InvocationContext invocation) throws Exception This method siganture is present in classes SessionBeanInterceptor, EntityManagerProxyInterceptor and HibernateSessionProxyInterceptor Exception: [18/11/08 16:17:51:537 EST] 0000001a annotations E AnnotativeMetadataManagerImpl merge Caught exception while merging com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.persistence.EntityManagerProxyInterceptor.postActivate(Lorg/jboss/seam/intercept/InvocationContext;)V[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl@1b8e1b8e], parameters were specified, but null was the expected comparison -- 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

17 years

7
35
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3572) Seam nested booking example - NoSuchEJBException on undeploy

by Jozef Hartinger (JIRA)

Seam nested booking example - NoSuchEJBException on undeploy ------------------------------------------------------------ Key: JBSEAM-3572 URL: https://jira.jboss.org/jira/browse/JBSEAM-3572 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.GA Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger I am getting plenty of javax.ejb.NoSuchEJBException-s when undeploying nested booking example. For exceptions to appear preceeding interaction with example is needed. For details see attached log. -- 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

17 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3672) JpaPermissionStore throws IAE "Cannot resolve principal name for principal.."

by Stefano Travelli (JIRA)

JpaPermissionStore throws IAE "Cannot resolve principal name for principal.." ------------------------------------------------------------------------------ Key: JBSEAM-3672 URL: https://jira.jboss.org/jira/browse/JBSEAM-3672 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.SP1 Environment: JBoss 4.2.2 JVM 1.6.0 Reporter: Stefano Travelli Given the following conditions: - JpaPermissionStore configured with a permission entity having PermissionRole and PermissionUser properties mapped as @ManyToOne relations. - that @ManyToOne relations are lazy - checking a permission for a Class target (resolved by ClassIdentifierStrategy) JpaPermissionStore throws an IllegalStateException "Cannot resolve principal name for principal..". I'm figuring out the reason and working on a patch. -- 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

17 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4055) Create <s:requireAll /> tag

by Jakub Janczak (JIRA)

Create <s:requireAll /> tag --------------------------- Key: JBSEAM-4055 URL: https://jira.jboss.org/jira/browse/JBSEAM-4055 Project: Seam Issue Type: Feature Request Components: JSF Controls Reporter: Jakub Janczak Fix For: The future create similar to the s:validateAll tag that sets required=true for all refrenced methods (getters) that have @NotNull or @NotEmpty validation annotation. It could be quite handy but require some reflection work (as you can't get the validators from ClassValidator class). -- 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

17 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4002) InstantiationException at Stateful bean (Could not instantiate Seam component)

by Tamas Malatinszki (JIRA)

InstantiationException at Stateful bean (Could not instantiate Seam component) ------------------------------------------------------------------------------ Key: JBSEAM-4002 URL: https://jira.jboss.org/jira/browse/JBSEAM-4002 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.1.GA, 2.1.1.CR2 Environment: JBoss AS 4.2.2 / 4.2.3 / 5.0.0, WinXP / Debian Linux, JD1.6 update 7/11/12 Reporter: Tamas Malatinszki Stateful beans are failing with "Could not instantiate Seam component" error in Seam 2.1.1 CR2 and above. The root cause is "java.lang.ClassNotFoundException: No ClassLoaders found for: <stateful bean>". The application is working fine with Seam 2.1.1 CR1 (and before). See the whole stacktrace and the related code at http://www.seamframework.org/Community/StatefulBeanErrorInSeam211GAAndCR2 -- 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

17 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4062) Conversation deadlock for seam wicket pages with multiple request targets

by Clint Popetz (JIRA)

Conversation deadlock for seam wicket pages with multiple request targets ------------------------------------------------------------------------- Key: JBSEAM-4062 URL: https://jira.jboss.org/jira/browse/JBSEAM-4062 Project: Seam Issue Type: Bug Components: Wicket Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.0.CR1 If onRequestTarget is called multiple times in a given request thread, Manager.restoreConversation() will be called twice, and that class does not defend against this by making the second call a no-op, but instead increments the lock count on the conversation blindly, so when the request returns the conversation will be erroneously left with a lock count of one, and can't be subsequently 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

17 years

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4061) Seam booking example throws NotLoggedInException

by Marek Novotny (JIRA)

Seam booking example throws NotLoggedInException ------------------------------------------------ Key: JBSEAM-4061 URL: https://jira.jboss.org/jira/browse/JBSEAM-4061 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Reporter: Marek Novotny Priority: Minor To reproduce: 1.) Log in 2.) Go to change-password-page using Settings link 3.) Click Logout After this NotLoggedInException appears in the server log. See attached stack trace for details. -- 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

17 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4046) Downloading big files with s:resource is slow

by Stefano Travelli (JIRA)

Downloading big files with s:resource is slow --------------------------------------------- Key: JBSEAM-4046 URL: https://jira.jboss.org/jira/browse/JBSEAM-4046 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.2.CR1 Reporter: Stefano Travelli The reason is in the way method DocumentStoreUtils.writeStream() moves data between streams, that is one byte at time. -- 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

17 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3852) Specifically include "explode" and "deploy" seam-gen testing in release-process.txt

by Jay Balunas (JIRA)

Specifically include "explode" and "deploy" seam-gen testing in release-process.txt ----------------------------------------------------------------------------------- Key: JBSEAM-3852 URL: https://jira.jboss.org/jira/browse/JBSEAM-3852 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.1.2.CR1 -- 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

17 years

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