February 2010 - seam-issues - Jboss List Archives

[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, 2 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, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3918) org.jboss.seam.security.Identity needs to be decoupled from system for testing purposes

by Dan Hinojosa (JIRA)

org.jboss.seam.security.Identity needs to be decoupled from system for testing purposes --------------------------------------------------------------------------------------- Key: JBSEAM-3918 URL: https://jira.jboss.org/jira/browse/JBSEAM-3918 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA Environment: JBoss Seam 2.1.1.GA Reporter: Dan Hinojosa org.jboss.seam.security.Identity cannot be used in unit testing. Unit testing being defined as an isolated (no db, no app server) test. If I provide an identity into a test, once I call assertTrue(identity.hasRole("xxx")); I get an understandable NullPointerException because there is no Seam Context available. If I may recommend that org.jboss.seam.security.Identity be either an interface or a POJO with no dependencies as an API so TDD advocates can test their code easily. This would also fulfill Seam's idea that everything for the end user is testable. Example Test @Test(groups = "unit") public void testAuthenticateSuccessWithRoles() { Log log = createMock(Log.class); EntityManager entityManager = createMock(EntityManager.class); Query query = createMock(Query.class); Calendar createdDate = Calendar.getInstance(); Calendar updatedDate = Calendar.getInstance(); User user = new User(); user.setCreatedDate(createdDate); user.setEmail("ricardo(a)aol.com"); user.setFirstName("Ricardo"); user.setLastName("Montalban"); user.setName("rmontalban"); user.setNotes("userNotes2"); user.setPassword("passw0rd"); user.setId(220L); user.setUpdatedDate(updatedDate); Role role = new Role(); role.setName("mgmt"); role.setId(665L); Calendar createdDate2 = Calendar.getInstance(); createdDate2.set(2009, 1, 15, 12, 14, 15); role.setCreatedDate(createdDate2); Calendar updatedDate2 = Calendar.getInstance(); updatedDate2.set(2009, 1, 17, 13, 16, 20); role.setUpdatedDate(updatedDate2); role.setNotes("notes"); user.addRole(role); role.addUser(user); Credentials credentials = new Credentials(); credentials.setUsername("rmontalban"); credentials.setPassword("passw0rd"); Identity identity = new Identity(); log.info("authenticating #0", "rmontalban"); expect(entityManager.createQuery("SELECT u from User u " + "WHERE u.name = #{credentials.username} AND u.password = #{credentials.password}")).andReturn(query); expect(query.getSingleResult()).andReturn(user); replay(entityManager, query, log); Authenticator authenticator = new Authenticator(); authenticator.setLog(log); authenticator.setIdentity(identity); authenticator.setEntityManager(entityManager); authenticator.setCredentials(credentials); assertTrue(authenticator.authenticate()); assertTrue(identity.hasRole("mgmt")); //NullPointerException here verify(entityManager, query, log); } Output from the above test: java.lang.NullPointerException at org.jboss.seam.security.Identity.tryLogin(Identity.java:164) at org.jboss.seam.security.Identity.hasRole(Identity.java:444) at com.manning.mymanning.AuthenticatorTest.testAuthenticateSuccessWithRoles(AuthenticatorTest.java:128) -- 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, 2 months

2
3
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, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml

by Moritz Winter (JIRA)

RichFaces loses skin with login-required="true" in pages.xml ------------------------------------------------------------ Key: JBSEAM-4229 URL: https://jira.jboss.org/jira/browse/JBSEAM-4229 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.CR2 Environment: Seam 2.1.1.GA on JBoss 5.0.0.GA. Reporter: Moritz Winter -- 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, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4399) Specify the Quartz job name for @Asynchronous methods

by Nikolay Elenkov (JIRA)

Specify the Quartz job name for @Asynchronous methods ----------------------------------------------------- Key: JBSEAM-4399 URL: https://jira.jboss.org/jira/browse/JBSEAM-4399 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA Environment: JBoss 4.2.x, JBoss 5.x, Quartz Reporter: Nikolay Elenkov Attachments: quartz-job-name.patch When using the Quartz dispatcher, Seam implements asynchronous methods by creating Quartz job and trigger for every method, annotated with @Asynchronous. The QuartzDispatcher class uses UIDs for the job and trigger names, in order to generate unique names. While this is OK for one-off jobs and asynchronous events, it is not suitable for repeatable and cron jobs that might have to be paused, cancelled or rescheduled by the application. Jobs should have meaningful names, especially when they are saved in a database store. Requesting a means to specify the Quartz job name when declaring an asynchronous method. One way to do this is to add a new parameter annotation, JobName. The Quartz dispatcher should inspect the asynchronous method parameters and use the one annotated with @JobName (if any) as the base for the job/trigger name. -- 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, 2 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3938) Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them.

by John Sublette (JIRA)

Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them. --------------------------------------------------------------------------------------------------- Key: JBSEAM-3938 URL: https://jira.jboss.org/jira/browse/JBSEAM-3938 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. Reporter: John Sublette Priority: Minor Seam's Resteasy implementation does not support tagged interfaces, nor classes that implement them as described in RestEasy's documentation (section 28.2 - Sharing an interface...). An interface with tagged @Path throws an exception when it is registered - because an interface doesn't have a constructor. See org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap Line 112 through 138 for how RestEasy handles this by default - (using Scannotation) -- 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, 3 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4192) s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid

by Wolfgang Schwach (JIRA)

s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid ---------------------------------------------------- Key: JBSEAM-4192 URL: https://jira.jboss.org/jira/browse/JBSEAM-4192 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.2.CR2 Environment: all platforms Reporter: Wolfgang Schwach s.tld in jboss-seam.ui.jar/MANIFEST.MF/ is not valid as it contains two errors. There are two attribute entries in s.tld that are invalid according to the schema defined in http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd . These attribute entries can easily be found as both contain the words "Alias for" in their description element. It's my guess that these two entries are generated out of the alias entries in \ui\src\main\config\component\selectItems.xml -- 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, 3 months

6
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4460) <begin-conversation killPrevious="true"/>

by deanhiller (JIRA)

<begin-conversation killPrevious="true"/> ----------------------------------------- Key: JBSEAM-4460 URL: https://jira.jboss.org/jira/browse/JBSEAM-4460 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2 Reporter: deanhiller Please please please add the ability to kill the previous conversation when starting a new one. Nearly all seam code I have seen for starting a conversation would typically use this as this is typically the default that would be wanted(but does not yet exist). For backwards compatibility, keep the default false I guess, BUT have a property in components.xml or somewhere where developers can set previousKillDefaultValue="true" so the default will be true for all of my current begin conversation tags. I have looked in my project and start 16 conversations in different places all of which want to kill off the previous conversation instead of a debug.xhtml page popping up (or in production, the "a bug has occurred in our software, we are sorry for the inconvenience". thanks, Dean -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3996) Seam should ignore duplicate classes on classpath

by Max Rydahl Andersen (JIRA)

Seam should ignore duplicate classes on classpath ------------------------------------------------- Key: JBSEAM-3996 URL: https://jira.jboss.org/jira/browse/JBSEAM-3996 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA, 2.1.0.SP1 Reporter: Max Rydahl Andersen Assignee: Dan Allen Fix For: 2.1.2.GA As discussed in JBIDE-3623 then Seam is reporting "Two components with the same name and precedence - component name: <name>, component classes: <classname>" when the class name is exactly the same. In that case it should only be the one that is first on the classpath that is used; that the class exist in other locations is irrelevant since you won't be able to load the class anyway since in java classloading first-found wins. -- 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, 3 months

5
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2010