August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-903) @Bidirectional to combine @In and @Out

by Andrew (JIRA)

@Bidirectional to combine @In and @Out -------------------------------------- Key: JBSEAM-903 URL: http://jira.jboss.com/jira/browse/JBSEAM-903 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Andrew Priority: Minor IMO, it would be great to have an InOut annotation that can combine In and Out to avoid excessive typing. Examples: Now: @In(required=false, value="someString", scope=ScopeType.EVENT) @Out(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; Easier as: @Bidirectional(required=false, value="someString", scope=ScopeType.EVENT) private String localVariableName; -- 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, 6 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3173) Additional @Create documentation

by Mikael (JIRA)

Additional @Create documentation -------------------------------- Key: JBSEAM-3173 URL: https://jira.jboss.org/jira/browse/JBSEAM-3173 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA Reporter: Mikael Please add a little documentation saying that @Create annotated methods executes in the render response phase and thus Seam exception handling (navigation to error pages) won't work. -- 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, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2455) seam-gen dev profile does not read "WEB-INF/dev" directory for class files on Weblogic 10

by Jay Balunas (JIRA)

seam-gen dev profile does not read "WEB-INF/dev" directory for class files on Weblogic 10 ------------------------------------------------------------------------------------------ Key: JBSEAM-2455 URL: http://jira.jboss.com/jira/browse/JBSEAM-2455 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.GA Environment: RHEL 5 x86 JDK 1.6.0_02 Weblogic 10.3.TP Reporter: Jay Balunas A WAR application generated by seam-gen and modified as described in the new "Weblogic" chapter in the reference guide does not pick up the class files that deployed into the "WEB-INF/dev" directory. The easiest way to describe duplicating it is to refer to the reference guide chapter. What the user sees is that no matter what is entered into the login page it is a failed login - with no errors in the logs If the class files in the "WEB-INF/dev" directory are moved to the "WEB-INF/classes" directory the login page behaves as expected. Note the weblogic chapter to the reference guide is currently being finalized and I will note when it is checked in. -- 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, 6 months

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1508) Decouple framework from JSF

by Gavin King (JIRA)

Decouple framework from JSF --------------------------- Key: JBSEAM-1508 URL: http://jira.jboss.com/jira/browse/JBSEAM-1508 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.BETA2 We have dependencies there that we don't really need. -- 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, 6 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2680) conversationId doc change

by Samuel Mendenhall (JIRA)

conversationId doc change ------------------------- Key: JBSEAM-2680 URL: http://jira.jboss.com/jira/browse/JBSEAM-2680 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues Reporter: Samuel Mendenhall Priority: Minor references to conversationId=#{conversation.id} in the docs should be changed to #{manager.conversationIdParameter}=#{conversation.id}, ex. http://docs.jboss.com/seam/2.0.1.GA/reference/en/html_single/#d0e4594 -- 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, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-541) ConversationEntry reports the wrong description

by Norman Richards (JIRA)

ConversationEntry reports the wrong description ----------------------------------------------- Key: JBSEAM-541 URL: http://jira.jboss.com/jira/browse/JBSEAM-541 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.CR1 Reporter: Norman Richards Assigned To: Gavin King The linked forum post shows one example of this bug, though it is not directly the issue the poster is complaining of. Using the forum application as a guide, start a conversation and then start a nested conversation. End the nested conversation. The description of the parent conversation in the converstion list on will be incorrect. (it will have the name of the current conversation that just ended) This happens because of the following code: public String getDescription() { if ( isCurrent() ) { String desc = Conversation.instance().description; if (desc!=null) return desc; } return description; } public boolean isCurrent() { Manager manager = Manager.instance(); if ( manager.isLongRunningConversation() ) { return id.equals( manager.getCurrentConversationId() ); } else if ( manager.isNestedConversation() ) { return id.equals( manager.getParentConversationId() ); } else { return false; } } The parent conversation entry is considered "current". (isLongRunning() is false and isNestedConversation() is true) Because of this, the ConversationEntry description is ignored in favor of Conversation.instance().description. (Again, Conversation.instance(), is the nested conversation that just ended) Subsequent requests display the conversation description correctly since they are done in the context of the correct conversation. The isNestedConversation() check looks to be the source of the problem. I can't figure out what case that would make sense for. -- 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, 6 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2669) Document @AutoCreate overriding @Observer(create = false)

by Christian Bauer (JIRA)

Document @AutoCreate overriding @Observer(create = false) --------------------------------------------------------- Key: JBSEAM-2669 URL: http://jira.jboss.com/jira/browse/JBSEAM-2669 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Reporter: Christian Bauer I'm not even sure this is semantically correct but a component with @AutoCreate is always instantiated when it is referenced. The documentation only mentions the "when @In does not specify create=true" case. However, if you have an @AutoCreate component and it has an @Observer method, setting @Observer(create = false) has no effect, the component will be instantiated when the event occurs. We definitely need to document this or discuss it further. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2716) Glassfish Integration reference guide chapter

by Jay Balunas (JIRA)

Glassfish Integration reference guide chapter --------------------------------------------- Key: JBSEAM-2716 URL: http://jira.jboss.com/jira/browse/JBSEAM-2716 Project: JBoss Seam Issue Type: Task Components: Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Following the existing interop reference guide chapters create a glassfish integration chapter. Likely version: glassfish v2ur1-b09d References: http://weblogs.java.net/blog/bleonard/archive/2006/06/running_jboss_s_1.html http://weblogs.java.net/blog/rogerk/archive/2006/05/seam_on_glassfi.html http://www.coffeecrew.org/docs/html/netbeansFaceletsSeamEjb3/netbeansFace... -- 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, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3337) Review and update container interop chapters

by Jay Balunas (JIRA)

Review and update container interop chapters --------------------------------------------- Key: JBSEAM-3337 URL: https://jira.jboss.org/jira/browse/JBSEAM-3337 Project: Seam Issue Type: Bug Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.BETA1 Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 2.1.0.GA Review the chapters for weblogic, and websphere specifically for the 2.1.0 GA release. They need to tested and update for the latest changes. Review OC4J chapter as a lower priority. -- 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, 6 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2893) Thread-safety issues on Websphere with EM-injected components

by Eric Jung (JIRA)

Thread-safety issues on Websphere with EM-injected components ------------------------------------------------------------- Key: JBSEAM-2893 URL: http://jira.jboss.com/jira/browse/JBSEAM-2893 Project: Seam Issue Type: Bug Environment: Websphere 6.1.0.13 with EJB Feature Pack on both Windows XP SP2 and Solaris 9 (SunOS 5.9) Reporter: Eric Jung I'm attaching an extremely simple application that demonstrates thread-safety issues with EntityManager / EntityManagerFactory in Websphere 6.1. This application has one entity bean, one session bean, and one web page. The problem is very easy to reproduce. Just start typing "e" in the search field, which uses rich:suggestionbox, and very quickly press the search button. This results in two queries being performed simultaneously--one from the rich:suggestionbox keypress, and one from submitting the page's form. All 1000 rows of data begin with "e" so the query is slow, making it easier to create queries that execute simultaneously. You'll get one of the following exceptions if you time things right (this isn't difficult, just hit the search button very quickly--if you're too slow, both queries will succeed without error): "javax.ejb.ConcurrentAccessException: TX_METHOD_READY: wrong transaction" or "java.lang.IllegalStateException: could not acquire lock on @Synchronized component: memberSearch" I've tried this EAR with both Hibernate and OpenJPA as persistence providers, and switched databases between Apache Derby and DB2. In all four permutations, I get the exact same exceptions. That should rule out any JDBC driver or JPA implementation issues. I suspect this problem is related to the issue mentioned in this blog post by Sahoo (a Sun engineer): http://weblogs.java.net/blog/ss141213/archive/2005/12/dont_use_persis_1.html. Unfortunately, WebSphere doesn't support servlets 2.5 so <persistence-context-ref/> isn't available in web.xml. I tried the approach he discusses in "Application Managed Entity Manager", but it hasn't yet worked. You can download a pre-built EAR (with source code included) at http://www.mediafire.com/?tlxxgaj4qtm, but I'll be attaching source code and configuration files here, too (can't attach the EAR directly since it's 11.6 MB with all the required JARs). -- 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, 6 months

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