April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2914) PDF: Image inside a cell cannot be aligned properly

by Richard Leherpeur (JIRA)

PDF: Image inside a cell cannot be aligned properly --------------------------------------------------- Key: JBSEAM-2914 URL: http://jira.jboss.com/jira/browse/JBSEAM-2914 Project: Seam Issue Type: Bug Components: PDF Affects Versions: 2.0.1.GA Reporter: Richard Leherpeur I noticed that this is not possible to properly align an image inside a cell. I investigated a little and found out that one case is missing the UICell.handleAdd method. The actual method is implemented as: public void handleAdd(Object o) { if (o instanceof Phrase) { cell.setPhrase((Phrase) o); } else if (o instanceof Element) { // calling addElement negates setPhrase, etc... cell.addElement((Element) o); } else { throw new RuntimeException("Can't add " + o.getClass().getName() + " to cell"); } } The correct implementation should be: public void handleAdd(Object o) { if (o instanceof Phrase) { cell.setPhrase((Phrase) o); } else if (o instanceof Image) { // Allow proper control over image alignment cell.setImage((Image) o); } else if (o instanceof Element) { // calling addElement negates setPhrase, etc... cell.addElement((Element) o); } else { throw new RuntimeException("Can't add " + o.getClass().getName() + " to cell"); } } -- 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

17 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2816) Release new beta of documentation styles and upgrade branch to use them

by Pete Muir (JIRA)

Release new beta of documentation styles and upgrade branch to use them ----------------------------------------------------------------------- Key: JBSEAM-2816 URL: http://jira.jboss.com/jira/browse/JBSEAM-2816 Project: JBoss Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.0.2.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Blocker Fix For: 2.1.0.BETA1 -- 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

17 years, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2926) CLONE -Locking issue for ConversationEntry when using Conversation.instance().leave()

by Tomas Cerny (JIRA)

CLONE -Locking issue for ConversationEntry when using Conversation.instance().leave() ------------------------------------------------------------------------------------- Key: JBSEAM-2926 URL: http://jira.jboss.com/jira/browse/JBSEAM-2926 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Tomas Cerny Assigned To: Pete Muir Priority: Minor Fix For: 2.1.0.BETA1, 2.0.2.CR1 When using Conversation.instance().leave(), it seems that the ConversationEntry lock is not released. *Sometimes* it can be obtained when attempting to resume the conversation but other times it cannot. This results in the user being redirected to the no-conversation-view-id after the concurrent-request-timeout expires. This can be observed by placing Conversation.instance.leave() in an action that redirects to another page. Then simply use the back-button and resume the conversation by clicking a link on the page. You may have to try this several times to get the result. I will see if I can create a reliable test case and attach it. Manager.switchConversation() performs an unlock of the ConversationEntry prior to switching, which would also make sense in the case of leave (since it is really a switch to a temp conversation). The workaround is simply executing the following: Code: Conversation conversation = Conversation.instance(); ConversationEntry entry = ConversationEntries.instance().getConversationEntry(conversation.getId()); conversation.leave(); entry.unlock(); -- 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

17 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2922) Replace meldware with simple alternative

by Pete Muir (JIRA)

Replace meldware with simple alternative ---------------------------------------- Key: JBSEAM-2922 URL: http://jira.jboss.com/jira/browse/JBSEAM-2922 Project: Seam Issue Type: Task Components: Mail Affects Versions: 2.1.0.A1, 2.0.2.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.2.CR2, 2.1.0.BETA1 -- 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

17 years, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2920) Investigate using Maven version ranges with POMs

by Pete Muir (JIRA)

Investigate using Maven version ranges with POMs ------------------------------------------------ Key: JBSEAM-2920 URL: http://jira.jboss.com/jira/browse/JBSEAM-2920 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.0.2.CR1 Reporter: Pete Muir Assigned To: Pete Muir -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2925) Only one converter instance for JSF rendering

by Benjamin Graf (JIRA)

Only one converter instance for JSF rendering --------------------------------------------- Key: JBSEAM-2925 URL: http://jira.jboss.com/jira/browse/JBSEAM-2925 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.1.GA Reporter: Benjamin Graf If you use a @Converter annotated class as an JSF converter together with a facelets taglib definition you'll get a buggy behaviour. Since @Converter annotated classes have to be seam components only one instance per conversation could be created. If you use that converter several times on the same page you will get the same instance for every object to render. Since taglibs are written to use converters with different parameters this behaviour leads to wrong rendered HTML pages. -- 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

17 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2775) package-info.java should be optional:"convention over configuration"

by E. Jung (JIRA)

package-info.java should be optional:"convention over configuration" -------------------------------------------------------------------- Key: JBSEAM-2775 URL: http://jira.jboss.com/jira/browse/JBSEAM-2775 Project: JBoss Seam Issue Type: Feature Request Reporter: E. Jung Currently, package-info.java is required when referring to custom Seam components in components.xml. However, to further align Seam with the "convention over configuration" philosophy, this file can be optional by making some assumptions: 1. In the absence of package-info.java , the XML namespace in components.xml for custom components has a well-defined mapping to a Java package 2. This mapping can be defined as: a. The XML namespace must be parsable by java.net.URL, otherwise automatic mapping is aborted a. Protocol (scheme), the www/ subdomain, port, query parameters, anchors (references), and userInfo are ignored, if present. b. The top-level domain becomes the root Java package c. Subdomains become Java packages under the root package, applied in right-to-left order as specified in the URI. d. The path, as returned by URL.getPath(), is mapped to further Java packages such that each path element becomes another Java package appended in left-to-right order Examples: http://www.company.com/department/product ==> com.company.department.product https://company.com/department/product ==> com.company.department.product ftp://www.company.org/department/product ==> org.company.department.product abc://company.org/department/product ==> org.company.department.product company.net/foo/bar/baz ==> net.company.foo.bar.baz http://ericjung:password@www.company.com:8080/foo/bar/baz#anchor?param1=3... ==> com.company.foo.bar.baz -- 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

17 years, 11 months

4
21
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2763) DVD store Synchronize ProcessDefinitionSwitcher

by Martin Trummer (JIRA)

DVD store Synchronize ProcessDefinitionSwitcher ----------------------------------------------- Key: JBSEAM-2763 URL: http://jira.jboss.com/jira/browse/JBSEAM-2763 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.1.GA Reporter: Martin Trummer ProcessDefinitionSwitcher in DVD store example should be synchronized -- 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

17 years, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-683) Allow components.xml XSDs to be packaged in the jar with the components.

by Gavin King (JIRA)

Allow components.xml XSDs to be packaged in the jar with the components. ------------------------------------------------------------------------- Key: JBSEAM-683 URL: http://jira.jboss.com/jira/browse/JBSEAM-683 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Norman Richards Priority: Blocker Fix For: 1.1.5.GA Currently seam resolves XSDs in the path org/jboss/seam. But it would be better if the XSD for org.jboss.seam.core was located in the org/jboss/seam/core directory. This issue shows up with the mail stuff.... -- 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

17 years, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2918) Booking Example uses #{hotel.name} where it should use #{hotel.price}

by Richard Kennard (JIRA)

Booking Example uses #{hotel.name} where it should use #{hotel.price} --------------------------------------------------------------------- Key: JBSEAM-2918 URL: http://jira.jboss.com/jira/browse/JBSEAM-2918 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.1.GA Environment: Booking Example Reporter: Richard Kennard Priority: Trivial In the booking example, hotelview.xhtml incorrectly maps 'Nightly rate' to #{hotel.name}. This field should be mapped to #{hotel.price}. I discovered this while working on this blog entry for Metawidget... http://kennardconsulting.blogspot.com/2008/04/using-metawidget-with-seam-... ...so you might want to take a look at how Metawidget can solve it for you :) -- 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

17 years, 11 months

2
1
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 April 2008