May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1304) OC4J showing a blank page when deploying Glassfish example

by Richard Hoffman (JIRA)

OC4J showing a blank page when deploying Glassfish example ---------------------------------------------------------- Key: JBSEAM-1304 URL: http://jira.jboss.com/jira/browse/JBSEAM-1304 Project: JBoss Seam Issue Type: Feature Request Reporter: Richard Hoffman We are trying to get a Seam project deployed to OC4J. So far, the recommendation is to use the Glassfish example and deploy that to OC4J, but there are no instructions as to how to do this...so far, myself and a few others on the forums have only managed to get OC4J to show a blank screen. (I'm personally deploying via JDeveloper.) See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=100418 for petemuir's request to make this a Jira ticket. On a personal note, I don't have a preference as to who's EJB3 implementation to use (if any...Hibernate is fine, too). I just need to prove Seam works on OC4J...my client is making me use OC4J, despite my insistence that it's crap. :-/ -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3047) The version of the JVM impacts which version of mvel*.jar should be included.

by Earl Baugh (JIRA)

The version of the JVM impacts which version of mvel*.jar should be included. ----------------------------------------------------------------------------- Key: JBSEAM-3047 URL: http://jira.jboss.com/jira/browse/JBSEAM-3047 Project: Seam Issue Type: Thirdparty Change Affects Versions: 2.0.2.GA Environment: Seam and Java 1.4, 1.5 or 1.6 Reporter: Earl Baugh Priority: Minor As described on the MVEL web site, MVEL has some "compiler specific" issues. You can experience some odd behavior without the correct mvel*.jar that matches the JVM you are utilizing. The set up scripts should take this into consideration and/or the Seam package should include something to tell the developer that a different version may be required based on the JVM selected. See : http://mvel.codehaus.org/Downloading+MVEL for the different versions. They also state: "... if you are deploying to a specific environment, it is recommended you choose the build which matches your JRE version_" -- 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, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3043) seam root pom should declare type ejb for jboss-seam artifact

by Michael Brackx (JIRA)

seam root pom should declare type ejb for jboss-seam artifact ------------------------------------------------------------- Key: JBSEAM-3043 URL: http://jira.jboss.com/jira/browse/JBSEAM-3043 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: maven 2.0.9 Reporter: Michael Brackx the seam root pom should declare jboss-seam as follows <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <version>2.0.2.GA</version> <type>ejb</type> </dependency> If no type is specified, jar is used by default. There is no artifact defined as org.jboss.seam:jboss-seam:jar:2.0.2.GA -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1530) Seam-gen: @Length in char(1) property

by Luiz Augusto Ruiz (JIRA)

Seam-gen: @Length in char(1) property ------------------------------------- Key: JBSEAM-1530 URL: http://jira.jboss.com/jira/browse/JBSEAM-1530 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.3.0.ALPHA Reporter: Luiz Augusto Ruiz Seam-gen put a @Length Hibernate validator in char property. When a field of a table is CHAR(1) Hibernate generates a char property and seam-gen put a @Length(size=1). This can be fixed updating the template pojo/GetPropertyAnnotation.ftl: <#include "Ejb3PropertyGetAnnotation.ftl"/> <#if !property.optional> @${pojo.importType("org.hibernate.validator.NotNull")} </#if> <#if property.columnSpan==1> <#assign column = property.getColumnIterator().next()/> <#if !c2h.isManyToOne(property) && !c2h.isTemporalValue(property) && column.length!=255 && column.length!=1> @${pojo.importType("org.hibernate.validator.Length")}(max=${column.length?c}) </#if> </#if> " && column.length!=1" fix the bug. -- 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, 8 months

4
7
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2996?page=comments#action_12414604 ] Max Rydahl Andersen commented on JBSEAM-2996: --------------------------------------------- remove the nature and go on project settings and enable seam. > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assigned To: 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

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

by Rodrigo Souto (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2996?page=comments#action_12414587 ] Rodrigo Souto commented on JBSEAM-2996: --------------------------------------- is there any quick fix to this bug? > Imported seam-gen project does not show content assist on project specific components > ------------------------------------------------------------------------------------- > > Key: JBSEAM-2996 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2996 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.2.CR2 > Reporter: Jay Balunas > Assigned To: 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2352) Use of EL at no-conversation-view-id

by Joao Paulo (JIRA)

Use of EL at no-conversation-view-id ------------------------------------ Key: JBSEAM-2352 URL: http://jira.jboss.com/jira/browse/JBSEAM-2352 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Joao Paulo Priority: Optional Use of EL at no-conversation-view-id -- 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, 8 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3024) Performance issues in 2.0.2 release

by Alex Savitsky (JIRA)

Performance issues in 2.0.2 release ----------------------------------- Key: JBSEAM-3024 URL: http://jira.jboss.com/jira/browse/JBSEAM-3024 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.GA Reporter: Alex Savitsky For pages accessing components with many injections/outjections, performance is roughly 4x times worse when upgrading from 2.0.1 GA to 2.0.2 GA. -- 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, 8 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3046) Can't @RaiseEvent from EntityHome.setInstance

by Clint Popetz (JIRA)

Can't @RaiseEvent from EntityHome.setInstance --------------------------------------------- Key: JBSEAM-3046 URL: http://jira.jboss.com/jira/browse/JBSEAM-3046 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.GA Reporter: Clint Popetz If one overrides setInstance() in an entityHome subclass in order to raise an event when the instance changes: @Name("dateRangeHome") public class DateRangeHome extends EntityHome<DateRange> { @RaiseEvent("edu.academyart.monitor.action.dateRangeChanged") public void setInstance(DateRange instance) { super.setInstance(instance); } } and then does this in the view: <h:selectOneMenu value="#{dateRangeHome.instance}"> <s:selectItems value="#{dateRangeList.resultList}" var="dateRange" label="#{dateRange.title}"> <s:convertEntity/> <a:support event="onchange" action="refresh" ajaxSingle="true" reRender="graph"/> </h:selectOneMenu> the event will never be raised. This is because javac creates a synthetic setInstance(Object) in addition to the actual setInstance(Date), because the overridden method is a generic. When EL looks for setInstance() it finds the Object version first, which is not annotated, so the event interceptor does nothing, and the delegated call is of course not intercepted. Yuck! This might be considered a bug in javac, or a deficiency in the reflection API, or a bug in the BeanELResolver, depending on who you talk to. Here's a discussion: http://sensualjava.blogspot.com/2007/11/walls-and-bridges.html I can't think of an easy workaround in seam itself. Since the framework classes make use of templates, and since seam-gen users are inevitably going to try overriding methods in those classes and annotated them, it would be worth having documentation to clarify this behavior. -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3040) Messages from EntityHome when you create, update or delete

by Margarita Fazzio (JIRA)

Messages from EntityHome when you create, update or delete ----------------------------------------------------------- Key: JBSEAM-3040 URL: http://jira.jboss.com/jira/browse/JBSEAM-3040 Project: Seam Issue Type: Feature Request Reporter: Margarita Fazzio -- 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, 8 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008