September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2637) JIRA links

by Pete Muir (JIRA)

JIRA links ---------- Key: JBSEAM-2637 URL: http://jira.jboss.com/jira/browse/JBSEAM-2637 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Pete Muir Assigned To: Christian Bauer Priority: Optional Currently when you do [=>jbseam://1752] (which is a nice feature) it renders the link text the same, rather than the standard format of JBSEAM-1752 - is there anyway we can fix this? Or are we just going to use the newer format? -- 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

16 years, 6 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-769) Per view exception handling

by Peter Muir (JIRA)

Per view exception handling --------------------------- Key: JBSEAM-769 URL: http://jira.jboss.com/jira/browse/JBSEAM-769 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Reporter: Peter Muir Would be useful to be able to handle an exception differently depending on the current view id - especially for foo.page.xml style pages.xml -- 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

16 years, 6 months

6
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1898) EntityQuery hints map is defined as <String, String> instead of <String, Object>

by david castannon (JIRA)

EntityQuery hints map is defined as <String, String> instead of <String, Object> -------------------------------------------------------------------------------- Key: JBSEAM-1898 URL: http://jira.jboss.com/jira/browse/JBSEAM-1898 Project: JBoss Seam Issue Type: Bug Reporter: david castannon EntityQuery hints map field is defined as <String, String> instead of <String, Object> used at hibernate method setHint of QueryImpl. So, if you want to set, e.g., "org.hibernate.cacheMode" hint with CacheMode.REFRESH jboss throws exception. -- 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

16 years, 6 months

4
6
0 / 0

[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

16 years, 6 months

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

16 years, 6 months

3
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

16 years, 7 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

16 years, 7 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

16 years, 7 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

16 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly

by Andy Bosch (JIRA)

FacesMessages.instance().addToControl and Datatable do not work properly ------------------------------------------------------------------------ Key: JBSEAM-1855 URL: http://jira.jboss.com/jira/browse/JBSEAM-1855 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Andy Bosch It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id. With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work. Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index). My wish: Please change FacesMessages.instance().addToControl. for using with client-ids. -- 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

16 years, 7 months

10
17
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2008