July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2369) Embedding custom fonts (TrueType, etc...) to the generated PDF file

by Victor Arabadzhiyski (JIRA)

Embedding custom fonts (TrueType, etc...) to the generated PDF file ------------------------------------------------------------------- Key: JBSEAM-2369 URL: http://jira.jboss.com/jira/browse/JBSEAM-2369 Project: JBoss Seam Issue Type: Feature Request Components: PDF Environment: jboss-4.2.0.GA Reporter: Victor Arabadzhiyski Using the information from the iText book and some forums I was able to generate PDF file with cyrillic content (by embedding the corresponding cyrillic-enabled font, because the default ones do not have such support). However, when I tried to generate the same PDF from JBoss Seam PDF, I found that there is no way to embed custom fonts in the PDF file from Seam and after PDF generation, the cyrillic content is simply missing (ignored?!) in the resulting PDF file. I think this will be nice multilingual feature for Seam -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3963) Reverse engineering Event database table results in Home class that will not compile

by Bruce Link (JIRA)

Reverse engineering Event database table results in Home class that will not compile ------------------------------------------------------------------------------------ Key: JBSEAM-3963 URL: https://jira.jboss.org/jira/browse/JBSEAM-3963 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: WIndows XP, MYSQL 5 database Reporter: Bruce Link Database has tables XUSER and EVENT. EVENT has a foreign key to XUSER. seam generate-entities generates a XuserHome.java file with accessor public List<Event> getEvents(); resulting in compiler error: [javac] c:\apps\projects\infosys211\src\hot\ca\bcit\infosys\session\XuserHome.java:54: getEvents() in ca.bcit.infosys.session.XuserHome cannot override getEvents() in org.jboss.seam.framework.Controller; attempting to use incompatible return type [javac] found : java.util.List<ca.bcit.infosys.model.Event> [javac] required: org.jboss.seam.core.Events [javac] public List<Event> getEvents() { [javac] ^ -- 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-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

15 years, 2 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back

by Paul Chan (JIRA)

Seam Remoting Callback not set before server response comes back ---------------------------------------------------------------- Key: JBSEAM-3721 URL: https://jira.jboss.org/jira/browse/JBSEAM-3721 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.0.SP1, 2.1.0.GA Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+ Reporter: Paul Chan Assignee: Shane Bryzak Original Issue =========== I tracked the issue down to one line of javascript code in remote.js req.onreadystatechange = function() {}; The following thread discusses the problem is with an old version of the JScript.dll 5.6.0.8820 which is the same version I've got on a laptop here. http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69... One solution is to upgrade JScript.dll to 5.6.0.8831 http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx Or we can do what they did in GWT which is to move the req.onreadystatechange out of the scope of the current function window.setTimeout(function() { req.onreadystatechange = function() {}; }, 0 ); Problem found with the above fix ============================ I have found a bug in this fix. If the server response comes back before the "window.setTimeout(xxx,0) expires, it will drop it. >From reading the javascript specs, the minimum timeout value is actually around 25ms. Anything smaller than that, it gets rounded up. Also, using timer to set response callback are inherently flawed IMO. There's always going to be some sort of race condition. This problem seems to happen on internet explorer, and safari. Firebox doesn't seem to have a problem with it though. I discovered this problem when I set a break point on the incoming request processing code on the server. If the breakpoint is inserted, everything is good. But when I removed the breakpoint, the problem appears again. -- 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

6
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4208) Debug view causes trinidad error

by Stephane Epardaud (JIRA)

Debug view causes trinidad error -------------------------------- Key: JBSEAM-4208 URL: https://jira.jboss.org/jira/browse/JBSEAM-4208 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Stephane Epardaud Using Trinidad 1.2.6 + Richfaces 3.1.3.GA + Seam 2.1.1.GA, the debug.seam view causes an exception in debug.xhtml inside the h:form element at SeamDebugPhaseListener line 56. The logs show org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit createResponseWriter SEVERE: No RenderingContext has been created. The exception is thrown in org.apache.myfaces.trinidad.render.CoreRenderer.encodeBegin How can I debug this? We got this exception right after upgrading from Seam 2.0 to 2.1 -- 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-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

15 years, 2 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

15 years, 3 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4237) Support message-driven POJO's

by Nikolay Elenkov (JIRA)

Support message-driven POJO's ----------------------------- Key: JBSEAM-4237 URL: https://jira.jboss.org/jira/browse/JBSEAM-4237 Project: Seam Issue Type: Feature Request Components: Async Reporter: Nikolay Elenkov Currently, if you want to use JMS in a Seam project, you have to deploy it as an EAR in a JEE application server, and use MessageDriven beans. However, JMS messaging is sometimes required in web (WAR) projects as well, and changing the application to and EAR and/or the application server is not possible. Seam should make it easy to use message-driven POJO's (POJO's that act as asynchronous receivers for JMS messages) in a web project, supporting all Seam features (injection, transaction management, etc.). It could be implemented by integrating Jencks (http://jencks.codehaus.org/) for example or built on top of ActiveMQ. Cf. Spring support for message-driven POJO's: http://static.springframework.org/spring/docs/2.5.x/reference/jms.html#jm... -- 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, 3 months

2
9
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

15 years, 3 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

15 years, 3 months

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009