March 2008 - seam-issues - Jboss List Archives

[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-2122) JPA example on OC4J 10

by Pete Muir (JIRA)

JPA example on OC4J 10 ---------------------- Key: JBSEAM-2122 URL: http://jira.jboss.com/jira/browse/JBSEAM-2122 Project: JBoss Seam Issue Type: Task Components: Examples Reporter: Pete Muir Fix For: 2.0.2.GA http://blogs.steeplesoft.com/2007/10/17/seam-and-jpa-hibernate-on-oc4j-1013/ - how to get a JPA app running on OC4J -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2449) The capturedView stuff doesn't support capturing the parameters emitted by s:link

by Andrew Elegante (JIRA)

The capturedView stuff doesn't support capturing the parameters emitted by s:link --------------------------------------------------------------------------------- Key: JBSEAM-2449 URL: http://jira.jboss.com/jira/browse/JBSEAM-2449 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Windows XP JBoss 4.2.2 GA Seam 2.0.0 GA RichFaces 3.1.2 GA Facelets 1.1.13 Reporter: Andrew Elegante I have a page with an s:link in it like so <s:link id="newFeeProduct" value="[#{feesNav.createNewFeeProduct}]" view="/fees/feeProduct/wizard/step1.xhtml" action="#{feeProductWizard.startNewWizard()}" propogation="begin" /> In my pages.xml I have the following: <page view-id="/fees/feeProduct/wizard/step1.xhtml" login-required="true" > </page> In my components.xml I have the following: <event type="org.jboss.seam.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.postAuthenticate"> <action execute="#{redirect.returnToCapturedView}"/> </event> It is possible that a user could click the link without having logged in which redirects to the login page. After logging in the redirect link retains the cid but loses the actionMethod param. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2444) Create a common "Extending Your seam-gen Application" chapter for the reference guide

by Jay Balunas (JIRA)

Create a common "Extending Your seam-gen Application" chapter for the reference guide ------------------------------------------------------------------------------------- Key: JBSEAM-2444 URL: http://jira.jboss.com/jira/browse/JBSEAM-2444 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Jay Balunas Create a common "Extending Your seam-gen Application" chapter. This will be used for common changes and upgrades for the basic seam-gen application. It should be written as container agnostic where possible. The individual container chapters will document any specific changes needed. This will allow the container specific chapters to reference this chapter rather than each document this. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1262) Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes)

by Nathaniel Stoddard (JIRA)

Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes) ------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1262 URL: http://jira.jboss.com/jira/browse/JBSEAM-1262 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard Currently, each validation specified a single message resource to be used as the error message. It would be helpful if there was some way to customize the error messages to be used such that in one case "Contact address is required." is displayed, while in others "Billing address is required", for example. Annotating model classes with validation rules limits the reuse of those classes since the validation messages offer limited flexibility. Since validated fields in the domain classes aren't necessarily associated with a UIInput on a page, it would be helpful to have more flexible annotations, such as: @MaxLength(messages = {@Message(role='contactForm', value='contact.too_long'), @Message(role='billingForm', value='billing.too_long')}) private String field; Also needed would be some way of indicated to the UIView which 'role' should be used when validation takes place. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2364) Resource-bundle from different modules bug

by Pierre Ingmansson (JIRA)

Resource-bundle from different modules bug ------------------------------------------ Key: JBSEAM-2364 URL: http://jira.jboss.com/jira/browse/JBSEAM-2364 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Windows XP, Eclipse, Seam running in a Tomcat 5.5.25 Reporter: Pierre Ingmansson We have a application that consists of several modules. Each module has it's own resource-bundle and therefore we created several "components.xml", one per module. In every "components.xml" we have the following (the name of the bundle varies per module off course..): <core:resource-loader> <core:bundle-names> <value>mymodule_messages</value> </core:bundle-names> </core:resource-loader> In a perfect world you would expect this to work, but it doesn't. Only the resource-bundle declared in the "components.xml" that was loaded last, is loaded into the ResourceLoader. My guess is that Seam stores all "component.xml"-parameters in some property during load, and when a new "components.xml" is loaded the settings are overwritten. Only the settings in the last "component.xml" is loaded.. -- 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
5
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 2008