August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2996) Imported seam-gen project does not show content assist on project specific components

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2996?page=com.atlassian.jira.pl... ] Pete Muir reassigned JBSEAM-2996: --------------------------------- Assignee: Max Rydahl Andersen (was: Pete Muir) Enabling Seam causes the exploded project builder to go insane. Max, can you take a look? > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assignee: Max Rydahl Andersen > Fix For: 2.1.0.BETA1 > > > Following seam release-process.txt I imported a project I created with seam-gen using 2.0.2.CR2. > I used "import an existing project" option. Then added seam support to the project using a seam runtime I configured with 2.0.2.CR2. > When I opened a view file and tried out the content assist it showed a lot of Seam components, but none of the components in the project itself. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-2996) Imported seam-gen project does not show content assist on project specific components

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2996?page=com.atlassian.jira.pl... ] Pete Muir reassigned JBSEAM-2996: --------------------------------- Assignee: Pete Muir (was: Max Rydahl Andersen) > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assignee: Pete Muir > Fix For: 2.1.0.BETA1 > > > Following seam release-process.txt I imported a project I created with seam-gen using 2.0.2.CR2. > I used "import an existing project" option. Then added seam support to the project using a seam runtime I configured with 2.0.2.CR2. > When I opened a view file and tried out the content assist it showed a lot of Seam components, but none of the components in the project itself. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3217) SessionContext null in stateless

by Marek Nazarko (JIRA)

SessionContext null in stateless -------------------------------- Key: JBSEAM-3217 URL: https://jira.jboss.org/jira/browse/JBSEAM-3217 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Environment: JBoss 4.0.2 Reporter: Marek Nazarko >From stateless component Contexts.getSessionContext() gives null. -- 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, 8 months

2
3
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

17 years, 8 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

17 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3228) SeamResourceServlet should service all HTTP request methods

by Christian Bauer (JIRA)

SeamResourceServlet should service all HTTP request methods ----------------------------------------------------------- Key: JBSEAM-3228 URL: https://jira.jboss.org/jira/browse/JBSEAM-3228 Project: Seam Issue Type: Task Components: Core Reporter: Christian Bauer The SeamResourceServlet implements doGet() and doPost() - the latter redirecting to doGet(). This has to be removed and replaced with a simple service() method so that ALL HTTP requests are routed to the resources. This shouldn't break anything. -- 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, 8 months

1
1
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

17 years, 8 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

17 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3230) Seam distribution contains two cglib libraries

by Marek Novotny (JIRA)

Seam distribution contains two cglib libraries ---------------------------------------------- Key: JBSEAM-3230 URL: https://jira.jboss.org/jira/browse/JBSEAM-3230 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Marek Novotny There are two cglib libraries - cglib-nodep (asm classes included in it) is directly (optional dependency) used in jboss-seam-ioc and cglib is depended on hibernate core library. I don't see any reason to have both in distribution - cglib.jar + asm.jar + cglib-nodep (includes asm classes) -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3222) seam-gen project throwing exceptions due to missing rest-easy dependencies

by Jacob Orshalick (JIRA)

seam-gen project throwing exceptions due to missing rest-easy dependencies -------------------------------------------------------------------------- Key: JBSEAM-3222 URL: https://jira.jboss.org/jira/browse/JBSEAM-3222 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Fix For: 2.1.0.BETA1 seam-gen projects by default include all Seam jars into the deployed archive. This includes the new jboss-seam-resteasy.jar but not its dependencies. This does not fail the application on deployment but does throw exceptions on startup. -- 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, 8 months

3
3
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 August 2008