April 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBSEAM-3269) Fixate webservice URL in examples

by Marek Novotny (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-3269?page=com.atlassian.jira.pl... ] Marek Novotny closed JBSEAM-3269. --------------------------------- > Fixate webservice URL in examples > --------------------------------- > > Key: JBSEAM-3269 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3269 > Project: Seam > Issue Type: Sub-task > Components: Examples > Affects Versions: 2.0.2.SP1 > Environment: JBoss 4.2.0.GA > JDK 1.5.0_01 > Reporter: Jan Hoeve > Assignee: Marek Novotny > Priority: Minor > Fix For: 2.2.1.CR2 > > > The session beans in the examples which are exposed as WebServices are difficult to call. > What I mean: The url for the webservices is changing very often (JBossWS?) , and thus it is very difficult to walk through the examples. > Easy fix: add an annotation @WebContext just below the @WebService in the beans. > Example: > @Stateless > @WebService(name = "AuctionService", serviceName = "AuctionService") > @WebContext(contextRoot ="auction-ws") > public class AuctionService implements AuctionServiceRemote > The webservice is now available under http://127.0.0.1:8080/auction-ws/AuctionService > This is easier than to find/google that it is available under AuctionServiceService. > Maybe it is also possible to mention this in the documentation / FAQ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBSEAM-3269) Fixate webservice URL in examples

by Marek Novotny (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-3269?page=com.atlassian.jira.pl... ] Marek Novotny resolved JBSEAM-3269. ----------------------------------- Fix Version/s: 2.2.1.CR2 Resolution: Duplicate Issue Assignee: Marek Novotny fixed in JBSEAM-4601, where I added jboss.xml configuration for webservices context root > Fixate webservice URL in examples > --------------------------------- > > Key: JBSEAM-3269 > URL: https://jira.jboss.org/jira/browse/JBSEAM-3269 > Project: Seam > Issue Type: Sub-task > Components: Examples > Affects Versions: 2.0.2.SP1 > Environment: JBoss 4.2.0.GA > JDK 1.5.0_01 > Reporter: Jan Hoeve > Assignee: Marek Novotny > Priority: Minor > Fix For: 2.2.1.CR2 > > > The session beans in the examples which are exposed as WebServices are difficult to call. > What I mean: The url for the webservices is changing very often (JBossWS?) , and thus it is very difficult to walk through the examples. > Easy fix: add an annotation @WebContext just below the @WebService in the beans. > Example: > @Stateless > @WebService(name = "AuctionService", serviceName = "AuctionService") > @WebContext(contextRoot ="auction-ws") > public class AuctionService implements AuctionServiceRemote > The webservice is now available under http://127.0.0.1:8080/auction-ws/AuctionService > This is easier than to find/google that it is available under AuctionServiceService. > Maybe it is also possible to mention this in the documentation / FAQ? -- 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, 9 months

1
0
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, 9 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, 9 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, 9 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, 9 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, 9 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4635) LdapIdentityStore is unsecure if anonymous LDAP bind is enabled at the LDAP server

by Flo Gle (JIRA)

LdapIdentityStore is unsecure if anonymous LDAP bind is enabled at the LDAP server ---------------------------------------------------------------------------------- Key: JBSEAM-4635 URL: https://jira.jboss.org/jira/browse/JBSEAM-4635 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.2.0.GA Environment: - Reporter: Flo Gle According to RFC 2829 section 5.1 a ldap server may accept a empty password as anonymous login and allow the bind. RFC 4513 section 5.1.2 establishes new rules for the anonymous bind, but it disallows not the old method. So if the ldap client sends a empty password string, the server can allow the bind. Using the LdapIdentityStore on a server that allows this binds results in a security problem: every username is accepted if the password is empty. Fix is easy. -- 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, 9 months

1
0
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, 9 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2010