November 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3946) LdapIdentityStore can not use backup server (failover)

by Raimund Hölle (JIRA)

LdapIdentityStore can not use backup server (failover) ------------------------------------------------------ Key: JBSEAM-3946 URL: https://jira.jboss.org/jira/browse/JBSEAM-3946 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1 Reporter: Raimund Hölle Since LdapIdentityStore assembles the provider URL internally, it is not possible to use extended URL's, e. g., a primary and a backup server like this: env.setProperty(Context.PROVIDER_URL, "ldap://srv01:389 ldap://srv02:389"); It would be nice if we would be able to set the providerUrl directly. For compatibility reasons, i suggest the following change: // new property settable from components.xml private String providerUrl = null; protected final InitialLdapContext initialiseContext(String principal, String credentials) throws NamingException { ... String url = providerUrl; if (url == null || url.equals("")) { url = String.format("ldap://%s:%d", getServerAddress(), getServerPort()); } env.setProperty(Context.PROVIDER_URL, url); ... Additionally it would be nice if initialiseContext() wouldn't be final so we are able to extend the class. Regards, Raimund -- 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

15 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3225) Seam Remoting JS memory leak in IE

by Joshua Davis (JIRA)

Seam Remoting JS memory leak in IE ---------------------------------- Key: JBSEAM-3225 URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: IE 6 Reporter: Joshua Davis Assignee: Shane Bryzak Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- 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

15 years, 2 months

2
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4096) Seam Remoting: connection hangs on IE 6 when the answer is fast

by Francesco Dandrea (JIRA)

Seam Remoting: connection hangs on IE 6 when the answer is fast --------------------------------------------------------------- Key: JBSEAM-4096 URL: https://jira.jboss.org/jira/browse/JBSEAM-4096 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.1.GA Reporter: Francesco Dandrea Assignee: Shane Bryzak Priority: Minor With IE when a remoting connection is fast, it hangs. In FF and Chrome it works. I did this following advice on: http://seamframework.org/Community/211GAIE7BugInRemotejs Since I didn't find the bug I opened this one. -- 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

15 years, 2 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4469) jpaidentity store null pointer when role collection is not initialezed. should throw exception.

by Eric Link (JIRA)

jpaidentity store null pointer when role collection is not initialezed. should throw exception. ----------------------------------------------------------------------------------------------- Key: JBSEAM-4469 URL: https://jira.jboss.org/jira/browse/JBSEAM-4469 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.2.0.GA Environment: jboss 5.1, linux x64, jdk 1.5 Reporter: Eric Link jpa identity store requires the roles collection to be initialezed, which is fine. if the collection is null, then a null pointer is thrown, but it is not clear _why_ w/o looking at the source. could add guard check and throw exception w/ explanaion Caused by: java.lang.NullPointerException at org.jboss.seam.security.management.JpaIdentityStore.grantRole(JpaIdentityStore.java:374) at org.jboss.seam.security.management.IdentityManager.grantRole(IdentityManager.java:136) if (xrefClass == null) { // If this is a Many-To-Many relationship, simply add the role if ( userRolesProperty.getValue(user) == null ) { //NEW throw new IllegalStateException("@UserRoles collection is nul, it must be initialized to grant rolesl"); //NEW } //NEW ((Collection) userRolesProperty.getValue(user)).add(roleToGrant); } else { // Otherwise we need to insert a cross-reference entity 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

15 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4467) Pages.XML fails to validate Correctly with options on begin/end conversation

by Cody Lerum (JIRA)

Pages.XML fails to validate Correctly with options on begin/end conversation ---------------------------------------------------------------------------- Key: JBSEAM-4467 URL: https://jira.jboss.org/jira/browse/JBSEAM-4467 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Reporter: Cody Lerum I'm trying to get my pages.xml to validate and I'm running into two validation issues that I can't get past. These appear to be defined in the xsd http://www.jboss.com/products/seam/pages-2.2.xsd however they don't allow attributes to be defined such as root=true <page view-id="/admin/org_add.xhtml"> <description>Add Organization</description> <navigation from-action="#{organizationUtil.addOrg()}"> <rule if-outcome="true"> <redirect view-id="/admin/org_list.xhtml" /> <end-conversation before-redirect="true"/> </rule> </navigation> </page> Errors with cvc-complex-type.2.4.d: Invalid content was found starting with element 'end-conversation'. No child element is expected at this point. <page view-id="/admin/search/search.xhtml"> <description>Search Results</description> <action execute="#{search.doSearch}"> <begin-conversation/> </action> </page> Error: cvc-complex-type.2.1: Element 'action' must have no character or element information item [children], because the type's content type is empty. To reproduce add these to your pages.xml and validate the file in eclipse. -- 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

15 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4455) Seamspace -- incorrect viewIds lead to missing page parameter propagation

by Wolfgang Schwendt (JIRA)

Seamspace -- incorrect viewIds lead to missing page parameter propagation -------------------------------------------------------------------------- Key: JBSEAM-4455 URL: https://jira.jboss.org/jira/browse/JBSEAM-4455 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Environment: Seam 2.2 Rev. 11569 http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2 Reporter: Wolfgang Schwendt Priority: Trivial When s:link and s:button are used in the facelets view template files of the Seamspace example, the JSF viewId to link to is written incorrectly. Right now in the Seamspace example, the viewId to link to is written as follows: s:link view="/friendrequest.seam" value="Send a friend request" propagation="none"... Instead of using the suffix/extension ".seam", the viewId to link to must be correctly written with the suffix/extension ".xhtml": s:link view="/friendrequest.seam" value="Send a friend request" propagation="none"... If ".seam" is used rather than ".xhtml", it leads to the missing propagation of page parameters. When an s:link/s:button is rendered, UISeamCommandBase.getUrl() retrieves the set of page parameters from Pages.getStringValuesFromModel(). The Pages component holds metadata for pages defined in pages.xml, including page parameters. When the wrong viewId is used, Pages.getStringValuesFromModel() does not find the page parameters for the JSF view to link to, and therefore page parameters are omitted when rendering the link. For example, when the viewID is written with '.seam', the link for sending a friend request is rendered with the target URL http://127.0.0.1:8080/seamspace/friendrequest.seam, but it should be http://127.0.0.1:8080/seamspace/friendrequest.seam?name=shadowman -- 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

15 years, 2 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4463) Seam booking - outdated page footers

by Jozef Hartinger (JIRA)

Seam booking - outdated page footers ------------------------------------ Key: JBSEAM-4463 URL: https://jira.jboss.org/jira/browse/JBSEAM-4463 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Reporter: Jozef Hartinger Priority: Trivial Fix For: 2.2.1.CR1 Seam booking example and its derivates contain outdated page footers i.e. "Created with JBoss Seam 2.0, JBoss EJB 3.0, JSF 1.2, Hibernate 3 and Facelets" -- 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

15 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2292) Resources from resource servlet can't be re-rendered

by Christian Bauer (JIRA)

Resources from resource servlet can't be re-rendered ---------------------------------------------------- Key: JBSEAM-2292 URL: http://jira.jboss.com/jira/browse/JBSEAM-2292 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Christian Bauer Found this after using the captcha: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> This is a re-rendered s:decorate form field, so that onblur we get a new challenge (if the captcha repsonse was wrong). However, the graphicImage is not reloaded from the server, the browser caches it. To prevent browser caching, this is a quick hack: <div class="input"> <a:region> <s:validateAll> <h:graphicImage value="/seam/resource/captcha?nocache=#{wiki:generateRandomNumber()}" style="vertical-align:text-bottom;"/> <h:inputText tabindex="1" size="6" maxlength="6" required="true" id="verifyCaptcha" value="#{captcha.response}"> <a:support status="#{statusId}" event="onblur" reRender="verifyCaptchaEntry"/> </h:inputText> </s:validateAll> </a:region> </div> -- 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

15 years, 2 months

3
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 November 2009