September 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3941) IdentityMaanger: extend permission checks to allow user to modify his own password

by Raimund HÃÂ¶lle (JIRA)

IdentityMaanger: extend permission checks to allow user to modify his own password ---------------------------------------------------------------------------------- Key: JBSEAM-3941 URL: https://jira.jboss.org/jira/browse/JBSEAM-3941 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 Priority: Minor Because IdentityManager.changePassword() requires the permission ("seam.user", "update"), it is not possible to use that method to change the password of the authenticated user itself without granting that permission to him. But granting that means, the user is able to modify _any_ user. I'm suggest to add a new permission target (or maybe a new action) and extend the changePassword() method: public static final String OWNPASSWORD_PERMISSION_NAME = "seam.user.ownpassword"; public boolean changePassword(String name, String password) { Identity identity = Identity.instance(); try { identity.checkPermission(USER_PERMISSION_NAME, PERMISSION_UPDATE); } catch (AuthorizationException e) { if ( identity.isLoggedIn() && identity.getCredentials().getUsername().equals(name) ) { Identity.instance().checkPermission(OWNPASSWORD_PERMISSION_NAME, PERMISSION_UPDATE); } else { throw e; } } return identityStore.changePassword(name, password); } Or maybe a specialized method? Many 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

13 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2652) s:decorate does not respect prependId="false" on h:form

by Erik Magnusson (JIRA)

s:decorate does not respect prependId="false" on h:form ------------------------------------------------------- Key: JBSEAM-2652 URL: http://jira.jboss.com/jira/browse/JBSEAM-2652 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.GA Environment: JBoss Seam 2.0.1GA Reporter: Erik Magnusson Given the following code: <h:form id="login" prependId="false"> <s:validateAll> <f:facet name="afterInvalidField"> <s:label styleClass="error"> <s:message/> </s:label> </f:facet> <div class="labelinputcombo ilcblock"> <h:outputLabel for="username">User name:</h:outputLabel> <s:decorate> <h:inputText id="username" value="#{registrationService.newUser.userName}" required="true"/> </s:decorate> </div> </s:validateAll> <div> <h:commandButton value="Register" action="#{registrationService.registerUser}"/> </div> </h:form> One would expect that none of the generated <input> elements would have prepended IDs, since the h:form has prependId="false". However, since s:decorate insists on inserting a superfluous <div> with a generated ID around the <input> elements it surrounds, those <input> elements end up having prepended IDs from that <div>. The relevant generated HTML: <div class="labelinputcombo ilcblock"> <label for="j_id31:username">User name:</label><div id="j_id31"><input id="j_id31:username" type="text" name="j_id31:username" /></div> </div> I did not ask for either the <div> or it's ID (<div id="j_id31">), or its insertion into my <input> element's ID (id="j_id31:username"). Proposed solutions: 1. Remove the generated <div>. Is it really necessary for the functionality of s:decorate? If I want a div I can always add it myself. 2. If the <div> really is necessary, at least make s:decorate respect the prependId="false" attribute of the surrounding h:form. 3. If that is not possible, as a last resort, introduce a prependId attribute on the <s:decorate> tag so we can at least force this behaviour if we want it. On a more general note, I'm a really big fan of the JSF-Seam-EJB3 combo, but some of the design decisions in the frameworks are baffling. Why so many superfluous generated html tags? And who thought of the bright idea of prepending element id attributes using : (colon) as the delimeter?? This effectively cripples the ability to use CSS to style JSF-generated HTML elements with a simple CSS id selector (since : is a reserved symbol in CSS). -- 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

13 years, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4045) Add first class support for groups

by Shane Bryzak (JIRA)

Add first class support for groups ---------------------------------- Key: JBSEAM-4045 URL: https://jira.jboss.org/jira/browse/JBSEAM-4045 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Reporter: Shane Bryzak Assignee: Shane Bryzak We should add first class support for user groups - these are a separate from roles, and allow applications to group users by department, location, etc. -- 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

13 years, 11 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2275) Document on Seam iText charting

by Joshua Partogi (JIRA)

Document on Seam iText charting ------------------------------- Key: JBSEAM-2275 URL: http://jira.jboss.com/jira/browse/JBSEAM-2275 Project: JBoss Seam Issue Type: Patch Affects Versions: 2.0.0.GA Environment: JBoss 4.2.1.GA Reporter: Joshua Partogi Fix For: 2.0.1.GA Point 16.2 1. Write in doc to use the charting support, we need to add the jfreechart.jar and jcommon-*.jar in the project classpath. We can also add this is our build.xml 2. The key attribute is needed upon p:data component usage otherwise it will throw this exception java.lang.IllegalArgumentException: Null 'key' argument. at org.jfree.data.DefaultKeyedValues.setValue(DefaultKeyedValues.java:239) at org.jfree.data.DefaultKeyedValues2D.setValue(DefaultKeyedValues2D.java:337) at org.jfree.data.DefaultKeyedValues2D.addValue(DefaultKeyedValues2D.java:303). In examples, it is used in (the ones below are the fixed value): Barchart, Linechart, Series PieChart 1. Attributes: title — The chart title text. legend — A boolean value indicating whether or not the chart should include a legend. Default value is true is3D - A boolean value indicating that the chart should be rendered in 3D instead of 2D. labelLinkMargin - The link margin labelLinkPaint - The paint used for the label linking lines. labelLinkStroke - The stroke used for the label linking lines. labelLinksVisible - A flag that controls whether or not the label links are drawn. labelOutlinePaint - The paint used to draw the outline of the section labels labelOutlineStroke - The stroke used to draw the outline of the section labels labelShadowPaint - The paint used to draw the shadow for the section labels labelPaint - The color used to draw the section labels labelGap - The gap between the labels and the plot as a percentage of the plot width. labelBackgroundPaint - The color used to draw the background of the section labels. If this is null, the background is not filled. startAngle - The starting angle circular - A boolean value indicating whether whether to draw an ellipse or a perfect circle. direction - The direction for the pie segments. If value is not set "anticlockwise" then by default it is clockwise. sectionOutlinePaint - The outline paint for ALL sections (overrides list). sectionOutlineStroke - The outline stroke for ALL sections (overrides list). sectionOutlinesVisible - A flag that controls whether or not an outline is drawn for each section in the plot. baseSectionOutlinePaint - The base section outline paint baseSectionPaint - The base section paint baseSectionOutlineStroke - The base section outline stroke 2. Usage: <p:document xmlns:p="http://jboss.com/products/seam/pdf"> <p:piechart title="Pie Chart" circular="false" direction="anticlockwise" startAngle="30" labelGap="0.1" labelLinkPaint="red"> <p:series key="Prices"> <p:data key="2003" columnKey="2003" value="7.36" /> <p:data key="2004" columnKey="2004" value="11.50" /> <p:data key="2005" columnKey="2005" value="34.625" /> <p:data key="2006" columnKey="2006" value="76.30" /> <p:data key="2007" columnKey="2007" value="85.05" /> </p:series> </p:piechart> </p:document> -- 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

13 years, 11 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3917) NPE in Image.getImage() for images with unsupported content type

by Daniel Wiell (JIRA)

NPE in Image.getImage() for images with unsupported content type ---------------------------------------------------------------- Key: JBSEAM-3917 URL: https://jira.jboss.org/jira/browse/JBSEAM-3917 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Daniel Wiell Image.readImage(InputStream) sets contentType to null if the type of the image is unknown (say a bmp). When invoking Image.getImage(), a NPE is thrown: java.lang.NullPointerException at org.jboss.seam.ui.graphicImage.Image.getImage(Image.java:154) ImageIO.write(bufferedImage, getContentType().getImageFormatName(), outputStream); getContentType() returns null. -- 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

13 years, 11 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3347) change column width in tables of pdf doc in security chapter

by Carsten Hoehne (JIRA)

change column width in tables of pdf doc in security chapter ------------------------------------------------------------ Key: JBSEAM-3347 URL: https://jira.jboss.org/jira/browse/JBSEAM-3347 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Carsten Hoehne Please try to adapt the column width of tables in the security chapter. As an example see table 15.4 Identity Management API in chapter 15.4.6 Please make the columnb Description a little bit wider and try to not overwrite strings in column Returns with strings in column Method Thanks in advance -- 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

13 years, 12 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4375) ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation

by Darryl Smith (JIRA)

ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4375 URL: https://jira.jboss.org/jira/browse/JBSEAM-4375 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: Darryl Smith setup: Parent (cid1) -> First Nested (cid2) ----> Second Nested (cid3) cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false); FacesManager's redirect method tries to encode the page parameters of the parent view, which accesses a component created in cid2 the conversation we are returning to. This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which switches the current conversation to cid2 after ManagedEntityWrapper wraps the component ManagedEntityWrapper's restorePreviousConversationContextIfNecessary method is called with oldCid = cid3 which triggers Contexts.getConversationContext().flush(); When flush is invoke the conversation (cid2) isn't long running, so flush removes all components created in cid2 -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3251) ValidateAllRendererBase not robust enough for dynamic components

by Richard Kennard (JIRA)

ValidateAllRendererBase not robust enough for dynamic components ---------------------------------------------------------------- Key: JBSEAM-3251 URL: https://jira.jboss.org/jira/browse/JBSEAM-3251 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1 Environment: Any Reporter: Richard Kennard Priority: Minor org.jboss.seam.ui.renderkit.ValidateAllRendererBase has two minor problems (with easy fixes) that stop it working with highly dynamic components: 1. doEncodeChildren attaches its ModelValidators before calling renderChildren. This misses any subcomponents the children may themselves dynamically create during their encodeBegin phase. Moving renderChildren down fixes this 2. A ModelValidator is only attached if the component has no existing Validators. This seems a bit of a blunt instrument. Presumably the idea is to stop attaching multiple ModelValidators. If the component happens to have, say, a LengthValidator that shouldn't stop ModelValidator entirely. I have attached an updated ValidateAllRendererBase. It does not break any existing unit tests. Disclaimer: my vested interest in this is because of Metawidget (http://www.metawidget.org). -- 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
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3770) MockHttpServletRequest.getHeaders(String) breaks for nonexistent headers

by Matt Drees (JIRA)

MockHttpServletRequest.getHeaders(String) breaks for nonexistent headers ------------------------------------------------------------------------ Key: JBSEAM-3770 URL: https://jira.jboss.org/jira/browse/JBSEAM-3770 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.1.CR1, 2.0.3.CR1 Reporter: Matt Drees Assignee: Matt Drees Priority: Minor Checked against 2.0.3.CR1 java.lang.NullPointerException at java.util.Arrays$ArrayList.<init>(Arrays.java:3357) at java.util.Arrays.asList(Arrays.java:3343) at org.jboss.seam.mock.MockHttpServletRequest.getHeaders(MockHttpServletRequest.java:100) at org.uscm.crs.filter.MojarraBugWorkaroundFilter.doFilter(MojarraBugWorkaroundFilter.java:60) ... I didn't check against trunk, but from a glance over the source code, it looks like it'll break there too. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-827) ICEfaces components are rendering during non RENDER_RESPONSE phase

by Gregory Dick (JIRA)

ICEfaces components are rendering during non RENDER_RESPONSE phase ------------------------------------------------------------------- Key: JBSEAM-827 URL: http://jira.jboss.com/jira/browse/JBSEAM-827 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Environment: SEAM+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick During the INVOKE_APPLICATION phase of application operations that are printing to PDF, SEAM is directly rendering facelets output, and ICEfaces components are mistakenly rendering at this time. -- 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

5
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 September 2009