May 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3349) LDAPIdentityStore generates invalid filter on listUsers method

by Vinicius Carvalho (JIRA)

LDAPIdentityStore generates invalid filter on listUsers method -------------------------------------------------------------- Key: JBSEAM-3349 URL: https://jira.jboss.org/jira/browse/JBSEAM-3349 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Vinicius Carvalho The Filter generated by the component is creating an invalid query, the format is this: (objectClass={0})(objectClass={1}) Where it should be: (&(objectClass={0})(objectClass={1})) We've fixed it by overriding the method with our own ldapidentitystore, below is just the minimal chage: StringBuilder userFilter = new StringBuilder(); userFilter.append("(&"); Object[] filterArgs = new Object[getUserObjectClasses().length]; for (int i = 0; i < getUserObjectClasses().length; i++) { userFilter.append("("); userFilter.append(getObjectClassAttribute()); userFilter.append("={"); userFilter.append(i); userFilter.append("})"); filterArgs[i] = getUserObjectClasses()[i]; } userFilter.append(")"); -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3685) Add "rendered" attribute to s:decorate

by Chris Simons (JIRA)

Add "rendered" attribute to s:decorate -------------------------------------- Key: JBSEAM-3685 URL: https://jira.jboss.org/jira/browse/JBSEAM-3685 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1, 2.1.0.GA, 2.1.0.CR1, 2.1.0.BETA1, 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA Reporter: Chris Simons Add an optional "rendered" attribute to s:decorate, if possible. If evaluated to false, this would preclude rendering of the template/component. I haven't seen a request like this in the past (I hope I didn't miss anything). -- 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

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2852) Scan for @WebRemote on extended Interfaces

by Alessandro Di Pasquale (JIRA)

Scan for @WebRemote on extended Interfaces ------------------------------------------- Key: JBSEAM-2852 URL: http://jira.jboss.com/jira/browse/JBSEAM-2852 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Environment: 2.0.1.GA Reporter: Alessandro Di Pasquale Assigned To: Shane Bryzak Priority: Minor Class org.jboss.seam.remoting.InterfaceGenerator does not scan for WebRemote.class-Annotation in extended Business-Interfaces -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4121) pages.xml not hot deploying in 2.1.1 GA

by Cody Lerum (JIRA)

pages.xml not hot deploying in 2.1.1 GA --------------------------------------- Key: JBSEAM-4121 URL: https://jira.jboss.org/jira/browse/JBSEAM-4121 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: JBAS 4.2.3 GA, Seam 2.1.1GA, JDK 6 Update 13 Reporter: Cody Lerum pages.xml do not seem to be getting hot deployed after a change. I have debug mode true and facelets.DEVELOPMENT=true. All my view pages are hot deploying fine but updating the navigation rules in pages.xml requires a server restart. -- 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

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3666) Natural Conversations: conversation id evaluated to null

by Arron Ferguson (JIRA)

Natural Conversations: conversation id evaluated to null -------------------------------------------------------- Key: JBSEAM-3666 URL: https://jira.jboss.org/jira/browse/JBSEAM-3666 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Ubuntu/Linux 7.10, Tomcat 6.0.16 Reporter: Arron Ferguson This is a repost of https://jira.jboss.org/jira/browse/JBSEAM-3368 which was closed but not fixed. The following errors occur with natural conversations (based on the attached use case): If I'm at page 4 (http://localhost:8080/test/register4.html) and I type: http://localhost:8080/test/register2.html (i.e., without the natural conversation id appended at the end like this: http://localhost:8080/test/register1.html?memberID=2), I get the following evaluated to null error: conversation id evaluated to null: regmem The exception is spewed to the log file but shouldn't be and should use the rules in the pages.xml file for error handling (see attached project). However, even if I type http://localhost:8080/test/register1.html?memberID=2, this is still broken because the rules in the pages.xml file are not being honored. The pages.xml file specifies: <rule if="#{memberreg.acceptedInformation}"> <redirect view-id="/register3.xhtml"/> </rule> Which states that this state should cause a redirect which is not happening. So, to recap, The included test project includes the Ant build script, and in the third party directory a list of the jar files used. Note: you don't need the DA.jar file. The jboss-archive-browsing.jar file is not included in the JBoss Seam download and so I had to grab it from the JBoss site. The version of the jboss-archive-browsing.jar (according to the manifest in the jar) is: Implementation-Version: 2.0.2.Alpha As I mentioned in the previous version of this bug report that was closed, Shane mentioned that there was a little more "noise" in the file than needed. It was quickly discovered however that this project test file was useful for spotting other bugs (I believe he said it helped him find another bug) and so I'm hoping that the same perspective will be used this time around as well. This example project in particular can be used to test many of the use cases and ensure that natural conversation processing is robust. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1592) <s:graphicImage> should accept raw byte[] without conversion

by Gena Batalski (JIRA)

<s:graphicImage> should accept raw byte[] without conversion ------------------------------------------------------------ Key: JBSEAM-1592 URL: http://jira.jboss.com/jira/browse/JBSEAM-1592 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA Environment: latest from repo Reporter: Gena Batalski Priority: Minor It would be helpful to feed the <s:graphicImage> with raw byte[] (possible also ByteArray - stream) without converting it to BufferedImage or something else. Also the content type could be manually entered. Of course, its in the responsibility of the developer, to take care about the correctness of input. Optional attributes (forceContentType, forceImage or something else) could do this job on the UI side. Background of the request: if i comment out the byte[] handling in Image.class (line 404 method readImage()) as in a following snipplet, i get an expected quality. Otherwise, the image quality decreases significantly, especially for small images (icons, thumbnails). /* byte[] b = (byte[]) input; readImage(new ByteArrayInputStream(b)); */ output = (byte[]) input; I also would have some possibility, to prepare the image on demand. Currently i'm using two servlets: one SeamResource and one for my images. My servlet receives an URI and selects an image LOB from DB, because it isn't necessary to store the images in memory (they could be large) and the images could stay unrequested. What i need is some kind callback (converter?) which asks me for byte[] or stream representation of an image uri. Thanks Gena -- 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, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2429) converterId in Seam page param not recognised in EAR project structure

by Terry (JIRA)

converterId in Seam page param not recognised in EAR project structure ---------------------------------------------------------------------- Key: JBSEAM-2429 URL: http://jira.jboss.com/jira/browse/JBSEAM-2429 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Windows, Project Structure EAR, JBoss 4.2 EAP. Seam2+Sun JSF RI+Facelets+Richfaces. Reporter: Terry In a EAR project structure; assigning converterId in page parameter in .page.xml file is not recognised. Throws errors: javax.faces.FacesException: Expression Error: Named Object: org.jboss.seam.ui.converter.DateTimeConverter not found. <param name="settlementDateFrom" converterId="org.jboss.seam.ui.converter.DateTimeConverter" value="#{paymentReconciliation.settlementDateFrom}"/> See forum issue for more details. -- 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, 10 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3305) Seam testsuite skipping and failing many tests on windows XP machine

by Jay Balunas (JIRA)

Seam testsuite skipping and failing many tests on windows XP machine -------------------------------------------------------------------- Key: JBSEAM-3305 URL: https://jira.jboss.org/jira/browse/JBSEAM-3305 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.0.BETA1 Environment: windows XP JDK5 Reporter: Jay Balunas Fix For: 2.1.0.BETA2 When running "ant testall testreport" on windows XP there are many failures and skipped tests. It appears to be a timing or io conflict with an hsql localDB.lck file in the embedded server. When you "ant test" the same examples individually they work fine. -- 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, 10 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2759) Seam dist directory structure verification and comparison between releases.

by Jay Balunas (JIRA)

Seam dist directory structure verification and comparison between releases. ----------------------------------------------------------------------------- Key: JBSEAM-2759 URL: http://jira.jboss.com/jira/browse/JBSEAM-2759 Project: JBoss Seam Issue Type: Task Components: Build Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Seam release directory structure verification and comparison between releases. This can be done through existing tools, and ant scripts. It will provide a information on where risk has been added and also fine issues related structure between releases. May be integrated with CI if able. -- 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, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value

by Alexander Schwartz (JIRA)

e:cell formatting of date or number colum fails, if first value is a null value ------------------------------------------------------------------------------- Key: JBSEAM-3879 URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 Project: Seam Issue Type: Sub-task Components: Excel Affects Versions: 2.1.1.GA Environment: Seam 2.1.1.GA, Windows, Jetty Reporter: Alexander Schwartz The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. from JXLHelper.java: /** * Gets the cell type for a cell. Tries to look it up in a cache based on the * component id of the cell. If it's not found, it's created and cached. * * @param uiCell The cell to look up * @return The data type of a cell */ private CellType getCellDataType(UICell uiCell) { if (log.isTraceEnabled()) { log.trace("Getting cell data type from cache for #0", uiCell.getId()); } CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); if (cellDataType == null) { /* old code: cellDataType = uiCell.getDataType(); */ /* new code start */ CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); cellDataType = cellStyle.forceType != null ? CellType .valueOf(cellStyle.forceType) : uiCell.getDataType(); /* new code end */ cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); } return cellDataType; } -- 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, 10 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009