February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2563) update 3.2.7. Component names in documentation

by Norman Richards (JIRA)

update 3.2.7. Component names in documentation ---------------------------------------------- Key: JBSEAM-2563 URL: http://jira.jboss.com/jira/browse/JBSEAM-2563 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Norman Richards See forum reference. Docs still reference factory when we use import namespaces now. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2295) Tutorial docs for nestedbooking example

by Pete Muir (JIRA)

Tutorial docs for nestedbooking example --------------------------------------- Key: JBSEAM-2295 URL: http://jira.jboss.com/jira/browse/JBSEAM-2295 Project: JBoss Seam Issue Type: Task Components: Documentation, Examples Affects Versions: 2.0.0.GA Reporter: Pete Muir Fix For: 2.0.1.GA These can in part be based on Jacob's article. -- 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
5
0 / 0

[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

16 years, 3 months

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

16 years, 3 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

16 years, 3 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

16 years, 3 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

16 years, 3 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

16 years, 3 months

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

16 years, 3 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

16 years, 3 months

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008