July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2986) Seam Transaction rolls back on all Exceptions

by Sean Burns (JIRA)

Seam Transaction rolls back on all Exceptions --------------------------------------------- Key: JBSEAM-2986 URL: http://jira.jboss.com/jira/browse/JBSEAM-2986 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2 Reporter: Sean Burns It looks like org.jboss.seam.util.Work rolls back a transaction for all exceptions if it had to create a transaction. This does not follow the normal EJB rollback spec, where transactions are only rolled back on Runtime Exceptions and @ApplicationException(rollback=true). I can work around this by using EJB Seam components instead of Seam POJO. -- 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, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3023) seam-gen generate-entities throws NoSuchMethodError on AnnotationConfiguration.setProperty

by Jay Balunas (JIRA)

seam-gen generate-entities throws NoSuchMethodError on AnnotationConfiguration.setProperty ------------------------------------------------------------------------------------------ Key: JBSEAM-3023 URL: http://jira.jboss.com/jira/browse/JBSEAM-3023 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Priority: Blocker Fix For: 2.1.0.BETA1 This is effecting the current trunk - I have not verified if this is happening in 2.1.0.A1. Below is the output from the console. I saw this error both with and without the fix for JBSEAM-3017. I quickly checked that the correct jars are in the lib, and should be loaded for the classpath in the seam-gen/build.xml. There may be a new dependency or configuration needed. jar: [copy] Copying 2 files to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar/META-INF [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar/META-INF [copy] Copying 1 file to /jboss/temp/workspace/libtest3/exploded-archives/libtest3.jar [hibernate] Executing Hibernate Tool with a JPA Configuration [hibernate] 1. task: generic exportertemplate: view/list.xhtml.ftl [hibernate] May 22, 2008 9:37:04 AM org.hibernate.cfg.annotations.Version <clinit> [hibernate] INFO: Hibernate Annotations 3.3.0.GA [hibernate] May 22, 2008 9:37:04 AM org.hibernate.ejb.Version <clinit> [hibernate] INFO: Hibernate EntityManager 3.3.2.GA [hibernate] An exception occurred while running exporter #2:generic exportertemplate: view/list.xhtml.ftl [hibernate] To get the full stack trace run ant with -verbose [hibernate] Problems in creating a configuration for JPA. Have you remembered to add hibernate EntityManager jars to the classpath ? [hibernate] java.lang.reflect.InvocationTargetException [hibernate] java.lang.NoSuchMethodError: org.hibernate.cfg.AnnotationConfiguration.setProperty(Ljava/lang/String;Ljava/lang/String;)Lorg/hibernate/cfg/AnnotationConfiguration; BUILD FAILED /jboss/temp/trunk/jboss-seam-2.1.0-SNAPSHOT/seam-gen/build.xml:1124: Problems in creating a configuration for JPA. Have you remembered to add hibernate EntityManager jars to the classpath ? -- 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, 3 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2432) Wildcard view-id descriptions for conversation switcher

by Jacob Orshalick (JIRA)

Wildcard view-id descriptions for conversation switcher ------------------------------------------------------- Key: JBSEAM-2432 URL: http://jira.jboss.com/jira/browse/JBSEAM-2432 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick Priority: Minor I have recently run into a requirement where it would be nice to have descriptions applied to wildcard view-ids. For example, if I have the following: Code: ... <page view-id="/section/*" conversation-required="true"> <description>Section 1</description> ... </page> ... Section 1 would be the description for all pages in /section/* unless specified otherwise in a higher precedence page definition. -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2899) Wrong JSF EL context used in cross-deployment calle

by Clint Popetz (JIRA)

Wrong JSF EL context used in cross-deployment calle --------------------------------------------------- Key: JBSEAM-2899 URL: http://jira.jboss.com/jira/browse/JBSEAM-2899 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR1 Reporter: Clint Popetz Attachments: cross-call-el-context.patch See the forum for an example. If a seam deployment servicing a JSF request invokes an EJB in another seam deployment, EL resolution in the callee will use the caller's ELContext. I patched this by having a threadlocal in Lifecycle called "inCall," setting that on beginCall(), clearing it on clearThreadLocals(), providing a static "isCall()" similar to isDestroying(), and having FacesExpressions use the non-JSF resolver if isCall() returns true. I'm not sure if that's the best approach (see the alternatives in the forum post) but it is the least invasive, and is more performant than forcing Expressions.instance() to look in all scopes so that we can override it by scope. -- 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, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1709) seam-gen generated code throws exception

by Ralph Schaer (JIRA)

seam-gen generated code throws exception ---------------------------------------- Key: JBSEAM-1709 URL: http://jira.jboss.com/jira/browse/JBSEAM-1709 Project: JBoss Seam Issue Type: Bug Components: Core, Framework Affects Versions: 2.0.0.BETA1 Environment: Seam (CVS checkout from today), JBoss 4.2.1, Java 6, Windows XP Reporter: Ralph Schaer A seam-gen generated application (with generated entities) is throwing the following error, when I click for example on the column header in a list (sort) or when I try to create a new object. Exception during request processing: Caused by java.lang.IllegalArgumentException with message: "Could not invoke method by reflection: Instance.getComponent() on: test.CarHome" org.jboss.seam.util.Reflections.invoke(Reflections.java:31) org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) Caused by java.lang.IllegalArgumentException with message: "object is not an instance of declaring class" sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jboss.seam.util.Reflections.invoke(Reflections.java:21) org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) org.jboss.seam.persistence.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:45) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:38) org.jboss.seam.util.Work.workInTransaction(Work.java:39) org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:32) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151) org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87) test.CarHome_$$_javassist_2.getComponent(CarHome_$$_javassist_2.java) org.jboss.seam.core.Validators.getValidator(Validators.java:85) Steps to reproduce the error 1. Create a table in the database (Example with mysql. I guess the database does not matter) CREATE TABLE `test`.`Car` ( `id` INTEGER UNSIGNED NOT NULL DEFAULT NULL AUTO_INCREMENT, `name` VARCHAR(255) NOT NULL, PRIMARY KEY (`id`) ) ENGINE = InnoDB; 2. seam setup (ear or war deployment does not matter. Problem exists in both deployment modes) 3. seam new-project 4. seam generate-entities 5. seam explode (jboss is already running) 6. Start the broser and type http://localhost:8080/name_of_webapp 7. Browser shows the Welcome screen. Everything looks fine. 8. Click on "Car List " 9. Click on "Create car" 10. Exception -- 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, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2916) Problem with the ejb-jar.xml file in jboss-seam.jar in WebSphere v6.1 (without ejb3 pack)

by Denis Forveille (JIRA)

Problem with the ejb-jar.xml file in jboss-seam.jar in WebSphere v6.1 (without ejb3 pack) ----------------------------------------------------------------------------------------- Key: JBSEAM-2916 URL: http://jira.jboss.com/jira/browse/JBSEAM-2916 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.0.2.CR1 Environment: WebSphere v6.1.0.15 without ejb3 pack, j2ee 1.4 Reporter: Denis Forveille Attachments: v61_SystemErr.log The "jboss-seam.jar" contains a file named "ejb-jar.xml" This makes WebSphere v6.1.0.15 (without ejb3 pack) to treat this jar as an ejb jar and as such, it tries to perform *some deployment actions* on it. This leads to the exception uploaded as attachment We are using seam 2.0.2 in POJOs mode (ie without ejb3). Also WebSphere does not know how to handle ejb3 jar files. However, even with this exception at deployment/startup, the applications seems to work fine If I remove the "ejb-jar.xml" file from jboss-seam.jar, the exception is gone and the applications works fine... -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2330) list.xhtml - Create Button disappearing when navigating

by Dupont Dupont (JIRA)

list.xhtml - Create Button disappearing when navigating ------------------------------------------------------- Key: JBSEAM-2330 URL: http://jira.jboss.com/jira/browse/JBSEAM-2330 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dupont Dupont When using seam-gen (2.0.0) I have the following issue : in list page, button 'Create entity' can disappear. To reproduce the problem, you'll need 2 associated entities (i.e. @ManyToOne) : 1 - navigate to entity A list. 2 - click 'Create entity A' button. 3 - click 'Select entity B' button. 4 - on entity B edit page, just click on the menu link 'Entity A List' 5 - you're back to 'Entity A List' page, but the 'Create entity A' button just disappeared. This issue is because Create button is rendered only if 'from' parameter is empty : <s:div styleClass="actionButtons" rendered="#{empty from}"> This isn't the case in interaction 4->5. Modifying menu.xhtml to force from parameter to '' and resolves this issue : changed from <s:link view="/CustomerList.xhtml" value="Customer List" propagation="none"/> to : <s:link view="/CustomerList.xhtml" value="Customer List" propagation="none"> <f:param name="from" value=""/> </s:link> -- 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, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3052) Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle

by Peter Maedel (JIRA)

Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle ------------------------------------------------------------------------- Key: JBSEAM-3052 URL: http://jira.jboss.com/jira/browse/JBSEAM-3052 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.2.GA Environment: JBoss AS 4.2.2 Seam 2.0.2 Reporter: Peter Maedel Lots of people have been dealing with the issue of overwritten exceptions: http://www.seamframework.org/Community/ConnectionProblem http://www.seamframework.org/Community/TransactionIsNotActiveWithCreateAn... Although in some cases this behaviour is part of EJB specification (EJB Container overwriting Exception) I am unsure if there isnt a possibility within Seam to print exceptions when they occure rather than have them overwritten with useless junk (cannot open connection, transaction is abort_only) later on. If you want to reproduce try opening a page that references a bean with this @create method: @Create public void iCrash(){ new File("nonExistentDirectory").listFiles(); } Honestly this behaviour has been a horrible waste of time so far! -- 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, 3 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2972) Unit test fails because of wicket unavailabity

by Joshua Partogi (JIRA)

Unit test fails because of wicket unavailabity ---------------------------------------------- Key: JBSEAM-2972 URL: http://jira.jboss.com/jira/browse/JBSEAM-2972 Project: Seam Issue Type: Task Components: Wicket Affects Versions: 2.1.0.A1 Reporter: Joshua Partogi Unit test fails because wicket component is not installed. Here are the message: java.lang.IllegalStateException: Must set application-class in <web:wicket-filter /> in components.xml at org.jboss.seam.web.WicketFilter.init(WicketFilter.java:80) at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97) at org.jboss.seam.mock.AbstractSeamTest.createSeamFilter(AbstractSeamTest.java:942) at org.jboss.seam.mock.AbstractSeamTest.setupClass(AbstractSeamTest.java:921) at org.jboss.seam.mock.SeamTest.setupClass(SeamTest.java:44) Developers shouldn't be forced to use wicket. It should be left optional. -- 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, 3 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3201) Update readme.txt, and other locations for JBoss 4.2.3 as needed

by Jay Balunas (JIRA)

Update readme.txt, and other locations for JBoss 4.2.3 as needed ---------------------------------------------------------------- Key: JBSEAM-3201 URL: https://jira.jboss.org/jira/browse/JBSEAM-3201 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.0.3.CR2, 2.1.0.BETA1 Update the readme.txt for seam, and search for other locations such as example readme files, reference guide, etc... Must test functionality first as well. -- 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, 3 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008