December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4092) @TransactionTimeout doesn't work on Seam Managed Transactions

by Marek Nazarko (JIRA)

@TransactionTimeout doesn't work on Seam Managed Transactions ------------------------------------------------------------- Key: JBSEAM-4092 URL: https://jira.jboss.org/jira/browse/JBSEAM-4092 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Marek Nazarko Seam ignores @TransactionTimeout annotation on method executed from JSF page (as "action"). -- 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

14 years, 8 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1683) s:fileUpload with required attribute

by Jonas Erma (JIRA)

s:fileUpload with required attribute ------------------------------------ Key: JBSEAM-1683 URL: http://jira.jboss.com/jira/browse/JBSEAM-1683 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Jonas Erma Fix For: 2.0.0.CR1 Is it possible to introduce a required attribute into the s:fileUpload tag? That way, I wouldn't need to check in my action methods if the file is null. tazman -- 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

14 years, 8 months

5
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3493) The EntityHome should not preserve the value of its instance property after entering a nested transaction when having the @PerNestedConversation annotation

by Francisco Jose Peredo Noguez (JIRA)

The EntityHome should not preserve the value of its instance property after entering a nested transaction when having the @PerNestedConversation annotation ----------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3493 URL: https://jira.jboss.org/jira/browse/JBSEAM-3493 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.SP1 Reporter: Francisco Jose Peredo Noguez I have a reflective 1-n associations like Person childof Person. I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hands... When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok: Each conversation has it's own instance of PersonHome BUT: all of those instances is wired to the same instance of Person (the Entity)... I've tried to trace modifications on the "instance" field of Home but it's never setted so it should stay to null and then call my createInstance() overrided method....but this never happen because (as I said) Person instance is the same as the parent conversation one.... Did I miss something? Or is this a limitation of the CRUD framework? nowhere on the code the field "instance" is setted so I believe this is due to javassist proxying that my eclipse debugger can't see... If this feature isn't working how would you implement my "Create child" button to create a new Person has a child of the current conversation "personHome.instance" ?... -- 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

14 years, 8 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4267) Token-based Remember-me is not working

by Johnny Ren (JIRA)

Token-based Remember-me is not working -------------------------------------- Key: JBSEAM-4267 URL: https://jira.jboss.org/jira/browse/JBSEAM-4267 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.2.GA, 2.1.1.GA Environment: JBOSS 4.2.3 Reporter: Johnny Ren Steps to reproduce the problem: Step1: create an AuthenticationToken class as described in 15.3.5.1. Stpe2: Modify the components.xml as described in 15.3.5.1. <security:jpa-token-stor token-class="org.jboss.seam.example.jpa.AuthenticationToken"/> <security:remember-me mode="autoLogin"/> <event type="org.jboss.seam.security.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> <action execute="#{identity.tryLogin()}"/> </event> <event type="org.jboss.seam.security.loginSuccessful"> <action execute="#{redirect.returnToCapturedView}"/> </event> Step 3: Modify the home.xhtml under examples\jpa\view as described in 15.3.5 <div> <h:outputLabel for="rememberMe" value="Remember me"/> <h:selectBooleanCheckbox id="rememberMe" value="#{rememberMe.enabled}"/> </div> Step 4: execute ant jboss Step 5: deploy the jboss-seam-jpa.war Step 6: go to http://localhost:8080/jboss-seam-jpa/home.seam Step 7: Select Remember me and use "demo/demo" to login. Result: javax.servlet.ServletException: #{identity.login}: org.jboss.seam.security.management.IdentityManagementException: Could not create account package org.jboss.seam.example.jpa; import java.io.Serializable; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.Id; import org.jboss.seam.annotations.security.TokenUsername; import org.jboss.seam.annotations.security.TokenValue; /** * */ @Entity public class AuthenticationToken implements Serializable { private Integer tokenId; private String username; private String value; @Id @GeneratedValue public Integer getTokenId() { return tokenId; } public void setTokenId(Integer tokenId) { this.tokenId = tokenId; } @TokenUsername public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } @TokenValue public String getValue() { return value; } public void setValue(String value) { this.value = value; } } -- 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

14 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3391) Use Credentials and RememberMe in code and EL expressions in examples, seam-gen and src

by Luis Tama (JIRA)

Use Credentials and RememberMe in code and EL expressions in examples, seam-gen and src --------------------------------------------------------------------------------------- Key: JBSEAM-3391 URL: https://jira.jboss.org/jira/browse/JBSEAM-3391 Project: Seam Issue Type: Task Components: Examples, Tools Affects Versions: 2.1.0.BETA1 Reporter: Luis Tama As of SEAM 2.1.0, the Identity component has been updated and the getters and setters for the properties username, password and rememberMe have been deprecated. So now we should use Credentials and RememberMe components. There are still many references to those getters/setters/properties in source code and in EL expressions in /examples, /seam-gen (including templates), and in /src, that lead to use of deprecated code. They should be updated. -- 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

14 years, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3054) use outbound urlrewriting in seambay example

by Dan Allen (JIRA)

use outbound urlrewriting in seambay example -------------------------------------------- Key: JBSEAM-3054 URL: http://jira.jboss.com/jira/browse/JBSEAM-3054 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.0.A1, 2.0.2.SP1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.x, 2.1.0.BETA1 Let's show off outbound urlrewriting in the seambay example. The current hard-coded RESTful URLs look so labor intensive. Plus, it all stops working if you turn off urlrewriting. By pushing it all into the urlrewrite engine, it works either way. -- 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

14 years, 8 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4479) cannot override createPermissionQuery method as Discriminator param type is private in JpaPermissionStore class

by Andrzej Smolinski (JIRA)

cannot override createPermissionQuery method as Discriminator param type is private in JpaPermissionStore class --------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4479 URL: https://jira.jboss.org/jira/browse/JBSEAM-4479 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.2.0.GA Environment: doesn't matter, its code problem Reporter: Andrzej Smolinski cannot override createPermissionQuery method as Discriminator param type is private in JpaPermissionStore class, so no acces to this (Discriminator enum) type in extending class -- 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

14 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4124) Change org.jboss.seam.security.loggedOut to org.jboss.seam.security.PostLoggedOut and add org.jboss.seam.security.PreLoggedOut

by Shervin Asgari (JIRA)

Change org.jboss.seam.security.loggedOut to org.jboss.seam.security.PostLoggedOut and add org.jboss.seam.security.PreLoggedOut ------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4124 URL: https://jira.jboss.org/jira/browse/JBSEAM-4124 Project: Seam Issue Type: Feature Request Components: Security Reporter: Shervin Asgari Priority: Trivial It would be nice to have an Event that was fired right before the user logged out. Right now we only have the org.jboss.seam.security.loggedOut event, but I would like to possibilty to log some information about the user logging out, and I cannot do that after the user has logged out, because the user session is destroyed. Either changing the event loggedOut name to PostLoggedOut or just adding a preLoggedOut. Which ever is fine with me :-) -- 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

14 years, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4436) No Conversation Context Error

by mike jones (JIRA)

No Conversation Context Error ----------------------------- Key: JBSEAM-4436 URL: https://jira.jboss.org/jira/browse/JBSEAM-4436 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: WebSphere 7.0.5 Reporter: mike jones Hello, I have 3 simple pages with back and next buttons. Here is the button in the atbc_search page <s:button id="next" alt="Next button" value="#{messages['button.next']}" action="#{atSearchSFSB.next}" </s:button> value="#{messages['button.next']}" action="#{atbcSearchSFSB.find}" </s:button> <s:button id="previous" alt="Previous button" value="#{messages['button.previous']}" action="#{atSearchSFSB.previous}" </s:button> value="#{messages['button.next']}" action="#{atbcSearchSFSB.previous}" </s:button> When I navigate back and forth it works for a while then all of the sudden I get 10/7/09 9:41:13:616 EDT] 0000002b viewhandler E Error Rendering View[/view/atbc_change.xhtml] java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.Conversation.instance(Conversation.java:122) at org.jboss.seam.ui.component.UIConversationId.getName(UIConversationId.java:44) at org.jboss.seam.ui.util.ViewUrlBuilder.addParameter(ViewUrlBuilder.java:42) at org.jboss.seam.ui.component.UISeamCommandBase.getUrl(UISeamCommandBase.java:85) at org.jboss.seam.ui.renderkit.ButtonRendererBase.getOnClick(ButtonRendererBase.java:37) at org.jboss.seam.ui.renderkit.ButtonRendererBase.doEncodeBegin(ButtonRendererBase.java:66) at org.jboss.seam.ui.util.cdk.RendererBase.encodeBegin(RendererBase.java:79) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:802) at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:232) at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:118) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:826) at org.ajax4jsf.renderkit.RendererBase.renderChild(RendererBase.java:277) at org.ajax4jsf.renderkit.RendererBase.renderChildren(RendererBase.java:258) at org.richfaces.renderkit.html.PanelRenderer.doEncodeChildren(PanelRenderer.java:220) Its very consistent. It works for a while I can click the back and next buttons then I just get this error. I really need help with this. I am not getting this error when I use a regular JSF button. It only happens when I use a Seam button. Pages.xml <page view-id="/view/atbc_search.xhtml"> <navigation from-action="#{atbcSearchSFSB.find}"> <rule if-outcome="find"> <redirect view-id="/view/atbc_change.xhtml" /> </rule> </navigation> </page> <page view-id="/view/atbc_change.xhtml"> <navigation from-action="#{atbcChangeSFSB.back}"> <rule if-outcome="back"> <redirect view-id="/view/atbc_search.xhtml" /> </rule> <rule if-outcome="next"> <redirect view-id="/view/home.xhtml" /> </rule> </navigation> <navigation from-action="#{atbcChangeSFSB.next}"> <rule if-outcome="next"> <redirect view-id="/view/home.xhtml" /> </rule> </navigation> </page> I am also using the Seam Redirect Servlet I am using WebSphere 7.0. Seam 2.2.0 GA -- 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

14 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2240) refactor for easier extensibility of seam identity: seam identiy interface + seam identity base impl

by koen handekyn (JIRA)

refactor for easier extensibility of seam identity: seam identiy interface + seam identity base impl ---------------------------------------------------------------------------------------------------- Key: JBSEAM-2240 URL: http://jira.jboss.com/jira/browse/JBSEAM-2240 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: koen handekyn Priority: Optional to allow easier extensibility of the seam identity class it would be useful to have a clear seam identity interface with complementary base impl from (package org.jboss.seam.security) use case: i'm trying to define my own seam identiy that contains as an extra parameter domain (login@domain/password). to have a complete implementation (which also saves the domain into a cookie) i'm stuck as 1. i don't know have an interface that I should satisfy if I wanted to make an implementation from scratch 2. extending from seam idenity has some issues : i missing some protected accessors to some private members (that maybe could be protected?) alternatively my question would be solved if i could have extension points within initFromCookie and at "setCookieValueIfEnabled( getUsername() ); from method postAuthenticate()" such that i could combine and split login and domain when saving/reading the cookie. -- 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

14 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009