December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2528) More pdf controls using direct content in order to have more control on where things are placed in a PDF.

by Lewis Gass (JIRA)

More pdf controls using direct content in order to have more control on where things are placed in a PDF. --------------------------------------------------------------------------------------------------------- Key: JBSEAM-2528 URL: http://jira.jboss.com/jira/browse/JBSEAM-2528 Project: JBoss Seam Issue Type: Feature Request Components: PDF Environment: N/A Reporter: Lewis Gass Priority: Minor Using direct content provide more pdf controls for direct placement (specifying x, y for example) of text, lines, shapes, images, columns and so forth in order to build completely customizable documents or use existing pdf documents as templates and simply fill in certain parts of the pdf in question. -- 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
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4004) BypassInterceptors is not always found correctly

by Norman Richards (JIRA)

BypassInterceptors is not always found correctly ------------------------------------------------ Key: JBSEAM-4004 URL: https://jira.jboss.org/jira/browse/JBSEAM-4004 Project: Seam Issue Type: Bug Reporter: Norman Richards Assignee: Norman Richards RootInterceptor cannot always correctly determine the existence of @BypassInterceptors. I didn't have time to investigate the root cause, but I could easily demonstrate the problem by adding @BypassInterceptors to an overridden hashCode() method. A quick look in the code shows that RootInterceptor Method object references the java.lang.Object.hashCode() method rather than the overridden method, causing the annotation lookup to fail. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4148) Exception Filter Regression on Page Parameter Propagation

by Mark Torres (JIRA)

Exception Filter Regression on Page Parameter Propagation --------------------------------------------------------- Key: JBSEAM-4148 URL: https://jira.jboss.org/jira/browse/JBSEAM-4148 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.1.2.CR1 Environment: Ubuntu 8.04, Seam 2.1.2.CR1, JDK 1.6.0_07, JBoss App Server 4.2.3.GA Reporter: Mark Torres Page parameters bound to event -scoped components are not being propagated during redirects on the exception filter. -- 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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3377) iText's p:image ignores dpi

by arne anka (JIRA)

iText's p:image ignores dpi --------------------------- Key: JBSEAM-3377 URL: https://jira.jboss.org/jira/browse/JBSEAM-3377 Project: Seam Issue Type: Bug Components: PDF Affects Versions: 2.0.2.SP1 Environment: jboss 4.2.2.GA Reporter: arne anka i got a pdf with 600dpi and a size of 1427x1311px. according to simple math and gimp that means a physical size of 2.38x2.18in or 6x5.5cm, which would easily fit onto an A4 page. but the rendered A4 pdf shows only a part of the image since it does not fit. i append the image and the pdf. my xhtml is below, note that setting dpi="600 600" does make _no_ difference! <p:document xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:p="http://jboss.com/products/seam/pdf" pageSize="A4"> <p:image alignment="center" dpi="600 600" value="/img/foo.png" /> </p:document> i am strongly interested in a workaround. -- 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

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4408) Unable to easily replace asynchronous dispatchers because of package-private methods

by Reid Pinchback (JIRA)

Unable to easily replace asynchronous dispatchers because of package-private methods ------------------------------------------------------------------------------------ Key: JBSEAM-4408 URL: https://jira.jboss.org/jira/browse/JBSEAM-4408 Project: Seam Issue Type: Feature Request Components: Async Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1, 2.1.1.GA Reporter: Reid Pinchback One of the benefits of Seam is that you can install your open components to replace the built-in ones provided by Seam. I was attempting to replace the ThreadPoolDispatcher, when I encountered something that maybe should change in the Schedule and TimerSchedule API. Instances of those classes can be created, but the values in them cannot be accessed because their accessors are package-private. For example: public class Schedule implements Serializable { private Long duration; ... Long getDuration() { return duration; } ... } Since the member variables are private, you can't create subclasses of Schedule or TimerSchedule to get at them, and because the accessors are package-private, you can't get at them that way. Similarly any subclass of AbstractDispatcher in a different package can't access those values for determining the appropriate values for scheduled futures. The only work-arounds at present are pretty grungy - either creating a subclass of TimerSchedule that keeps shadow copies of the member variables, or placing the application-specific dispatcher code in a package whose name mimics the Seam package structure. Neither is a show-stopper, but not really a good solution for a framework that is intentionally attempting to make itself extensible. I'd recommend making the Schedule and TimerSchedule accessors public. -- 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

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2514) EntityQuery can't be used in PAGE Scope

by Martin Hoffmann (JIRA)

EntityQuery can't be used in PAGE Scope --------------------------------------- Key: JBSEAM-2514 URL: http://jira.jboss.com/jira/browse/JBSEAM-2514 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.GA Environment: Seam 2.0.0.GA, JBoss AS 4.2.2.GA Reporter: Martin Hoffmann Priority: Optional The EntityHome is not able to operate in PAGE scope and the documentation says nothing about compatible scopes and framework classes. It throws an exeption: aused by: javax.el.ELException: /client/claim_list.xhtml @16,52 value="#{testList.dataModel}": Error reading 'dataModel' on type de.iseki.garantieext.card.Test List_$$_javassist_0 at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.ja va:76) at javax.faces.component.UIOutput.getValue(UIOutput.java:173) ... 69 more Caused by: java.lang.IllegalStateException: EntityManager is closed at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java :42) -- 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

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2301) JBoss EL bug handling overloaded methods with varargs mixed in

by Matthew Lieder (JIRA)

JBoss EL bug handling overloaded methods with varargs mixed in -------------------------------------------------------------- Key: JBSEAM-2301 URL: http://jira.jboss.com/jira/browse/JBSEAM-2301 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 2.0.0.GA Reporter: Matthew Lieder Doing facesMessages.add("Message") from an EL expression doesn't work, complaining about the String class not being compatible with the FacesMessage class. The problem is caused by a combination of two things: 1. There are two FacesMessages.add(...) that can accept one parameter: add(FacesMessage facesMessage) and add(String messageTemplate, Object... params) 2. The FacesMessages.add(...) that accepts a String as the first parameter can optionally accept additional parameters through a vararg If only one of those was the case, it'd work fine. However, having both at the same time triggers the error. -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message

by Norman Richards (JIRA)

observing events in the same component the raised one results in interceptors not being run on the observer message ------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3095 URL: http://jira.jboss.com/jira/browse/JBSEAM-3095 Project: Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Fix For: 2.0.3.GA, 2.1.0.BETA1 This is due to the MethodContextInterceptor imposing the unproxied object on the user. I think the fix is to make sure that events happen in a distinct method context. I've tested this with javabean components, but session beans might be trickier. -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2872) Duplicate command in the directory browser or be able to set creation time to Now

by Max Andersen (JIRA)

Duplicate command in the directory browser or be able to set creation time to Now --------------------------------------------------------------------------------- Key: JBSEAM-2872 URL: http://jira.jboss.com/jira/browse/JBSEAM-2872 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Max Andersen Assigned To: Christian Bauer My problem was that I created 2 blogs A and B and published B first then A later. On the feed it looked correct, but on the front page B was listed before A because the sort is based on creation times. Christian suggested to have a duplicate command... What I would like is a way to either sort based on the first publish time or be able to set the create timestamp to now so I don't have to affect the feeds and risk publishing the same entry twice. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3132) Seam text parser produces newline when HTML is used beginning of a line

by Christian Bauer (JIRA)

Seam text parser produces newline when HTML is used beginning of a line ----------------------------------------------------------------------- Key: JBSEAM-3132 URL: http://jira.jboss.com/jira/browse/JBSEAM-3132 Project: Seam Issue Type: Bug Components: Seam Text Reporter: Christian Bauer Assigned To: Christian Bauer foobar is rendered as foo bar This seems to affect all HTML tags that are at beginning of line, not inside a paragraph. -- 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
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009