February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2616) <s:transformImageSize> fills transparent areas with white background

by Manfred Gleirscher (JIRA)

<s:transformImageSize> fills transparent areas with white background -------------------------------------------------------------------- Key: JBSEAM-2616 URL: http://jira.jboss.com/jira/browse/JBSEAM-2616 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.0.GA Environment: Windows, Jboss 4.2.1, Facelets Reporter: Manfred Gleirscher Priority: Minor if a png-image containing transparent areas is scaled, the transparent areas get filled with white color. I created my own transformImageSize-component which works properly. Its applyTransformation method looks like that: <code> public void applyTransform(Image image) throws IOException { ........... BufferedImage in = image.getBufferedImage(); GraphicsConfiguration gc = in.createGraphics().getDeviceConfiguration(); BufferedImage out = gc.createCompatibleImage(scaledWidth, scaledHeight, Transparency.BITMASK); Graphics2D g2d = out.createGraphics(); g2d.setComposite(AlphaComposite.Src); g2d.setRenderingHint(RenderingHints.KEY_INTERPOLATION, RenderingHints.VALUE_INTERPOLATION_BICUBIC); g2d.drawImage(in, 0, 0, scaledWidth, scaledHeight, null); g2d.dispose(); image.setBufferedImage(out); } </code> -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3044) Seam and Google Guice Integration

by Pawel Wrzeszcz (JIRA)

Seam and Google Guice Integration --------------------------------- Key: JBSEAM-3044 URL: http://jira.jboss.com/jira/browse/JBSEAM-3044 Project: Seam Issue Type: Patch Affects Versions: 2.1.0.A1 Reporter: Pawel Wrzeszcz A patch contains implementation of Guice support for Seam. Basically, it allows use of Guice injection for all Seam components annotated with the @Guice annotation. I expect Guice may be useful to tie non-Seam parts of large or legacy applications together with Seam. Implementation is located in the src/guice directory and packaged as jboss-seam-guice.jar. I've provided an XML Schema for configuration and a really simple example application, together with a test case. Usage and documentation: http://wiki.jboss.org/wiki/LabsSeamGuice -- 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, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3944) Chatroom example - messages not delivered

by Jozef Hartinger (JIRA)

Chatroom example - messages not delivered ----------------------------------------- Key: JBSEAM-3944 URL: https://jira.jboss.org/jira/browse/JBSEAM-3944 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.2.CR1 Environment: JDK 5 update 16 JBoss AS 4.2.3 Firefox 3 Reporter: Jozef Hartinger Fix For: 2.1.2.CR1 Attachments: chatroom.txt Example loads. I can log in, however sent messages are not delivered. After sending a first message after connection, attached exception appears in the log. When connecting from second browser instance, I can see the current user as well as the first logged in user list but messages are still not delivered. -- 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, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3824) Chapter 29.10 should be updated being DeploymentHandler has been re-factored.

by Jay Balunas (JIRA)

Chapter 29.10 should be updated being DeploymentHandler has been re-factored. ----------------------------------------------------------------------------- Key: JBSEAM-3824 URL: https://jira.jboss.org/jira/browse/JBSEAM-3824 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.CR2 Reporter: Jay Balunas Fix For: 2.1.2.CR1 Since DeploymentHandler has been re-factored Chapter 29.10 should be updated. -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3711) openid docs and example

by Norman Richards (JIRA)

openid docs and example ----------------------- Key: JBSEAM-3711 URL: https://jira.jboss.org/jira/browse/JBSEAM-3711 Project: Seam Issue Type: Sub-task Reporter: Norman Richards Assignee: Norman Richards Fix For: 2.1.1.CR2 Need to update docs and create a sample app -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3412) .page.xml are only loaded for pages with .xhtml extesnion.

by Prashant Kadam (JIRA)

.page.xml are only loaded for pages with .xhtml extesnion. ---------------------------------------------------------- Key: JBSEAM-3412 URL: https://jira.jboss.org/jira/browse/JBSEAM-3412 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Environment: JBoss Reporter: Prashant Kadam I have a facelete pages with '.jspx' extension. It seems that pages with only .xhtml extensions are mapped for page orchestration. Here's the code from org.jboss.seam.navigation.Pages.java file : private void parsePages(Set<String> ...fileNames) { Set<String> mergedFileNames = new HashSet<String>(); for (Set<String> f : fileNames) { mergedFileNames.addAll(f); } for (String fileName: mergedFileNames) { String viewId = "/" + fileName.substring(0,fileName.length()-".page.xml".length()) + ".xhtml"; // needs more here InputStream stream = ResourceLoader.instance().getResourceAsStream(fileName); if (stream==null) { log.info("no pages.xml file found: " + fileName); } else { log.debug("reading pages.xml file: " + fileName); parse(stream,viewId); } } } -- 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, 8 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3743) Renderer gets confuesed when sending of email throws exception

by Alexander Sparkowsky (JIRA)

Renderer gets confuesed when sending of email throws exception -------------------------------------------------------------- Key: JBSEAM-3743 URL: https://jira.jboss.org/jira/browse/JBSEAM-3743 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1, 2.1.0.GA Environment: Mac OS X 10.5.5, Java 5, JBoss 4.0.5 modified for seam 2.x Reporter: Alexander Sparkowsky Assignee: Pete Muir Attachments: emailtest.xhtml When sending of an email fails and an exception is thrown (i.e. mail server not available) the renderer seems to get into a wrong state. <s:link> present on the page get the application context "project". So "/myseamapp/foo/bar" becomes "/project/foo/bar". If the action that is trying to send the mail is called by <s:link> this link gets the path of the email view itself (including the "project" application context). I've attached a Bean sending the email, the email template (/test.xhtml) and a simple view. This is the mail session configuration from components.xml <mail:mail-session host="localhost" port="2525" username="test" password="test" /> -- 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, 8 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3449) Upgrade to latest RestEasy beta

by Scott Olcott (JIRA)

Upgrade to latest RestEasy beta ------------------------------- Key: JBSEAM-3449 URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Scott Olcott The latest beta os beta-8 -- 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, 8 months

10
29
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3300) ICEfaces <ice:dataTable> should use <ice:dataPaginator>

by Valerie Griffin (JIRA)

ICEfaces <ice:dataTable> should use <ice:dataPaginator> ------------------------------------------------------- Key: JBSEAM-3300 URL: https://jira.jboss.org/jira/browse/JBSEAM-3300 Project: Seam Issue Type: Bug Components: ICE Faces Integration, Tools Affects Versions: 2.0.3.CR1 Environment: ICEfaces Reporter: Valerie Griffin Assignee: Gregory Dick The ICEfaces integration creates an <ice:dataTable> component for data display but does not create <ice:dataPaginator> components to control that display. Note that <ice:dataPaginator> components must be inside a form. Note, also, that the paginator won't work if the generated TblList.java code contains the override of maxResults. -- 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, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3599) Seam-gen : Icefaces war project throws IllegalStateException

by Jozef Hartinger (JIRA)

Seam-gen : Icefaces war project throws IllegalStateException ------------------------------------------------------------ Key: JBSEAM-3599 URL: https://jira.jboss.org/jira/browse/JBSEAM-3599 Project: Seam Issue Type: Bug Components: ICE Faces Integration, Tools Affects Versions: 2.1.0.GA Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Assignee: judy guglielmin Attachments: seam-gen-ice-ear-edit.txt 1.) Create new Icefaces EAR project 2.) Generate entities from database using standard vehicle and person tables (release-process.txt) 3.) Deploy project 4.) Create person 5.) After new person is created, click to view user details 6.) Click edit button - after this I am getting the attached exception -- 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, 8 months

4
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009