April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-757) Trinidad: Implementation of CollectionModel that is backed by EntityQuery

by Peter Muir (JIRA)

Trinidad: Implementation of CollectionModel that is backed by EntityQuery ------------------------------------------------------------------------- Key: JBSEAM-757 URL: http://jira.jboss.com/jira/browse/JBSEAM-757 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Peter Muir Priority: Minor A solid implementation of the Trinidad CollectionModel API, that could handle the following issues: (1) Page in data as necessary, automatically (2) Report good permanent row keys, so that adding/removing rows gets picked up without any off-by-one errors. (3) Perform sorting directly on the model -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1184) Exception documentation uses wrong Filter

by Mike Quilleash (JIRA)

Exception documentation uses wrong Filter ----------------------------------------- Key: JBSEAM-1184 URL: http://jira.jboss.com/jira/browse/JBSEAM-1184 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash In "5.3.2. Enabling Seam exception handling" the filter configuration described is this <filter> <filter-name>Seam Filter</filter-name> <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class> </filter> <filter-mapping> <filter-name>Seam Filter</filter-name> <url-pattern>*.seam</url-pattern> </filter-mapping> The filter class is incorrect should be "org.jboss.seam.web.SeamFilter" -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1134) I18N body must be native encoding

by Kay Arita (JIRA)

I18N body must be native encoding --------------------------------- Key: JBSEAM-1134 URL: http://jira.jboss.com/jira/browse/JBSEAM-1134 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 1.2.1.GA Reporter: Kay Arita Assigned To: Pete Muir Body part must be not ascii encoding but native encoding when text/plain specified. --- Return-Path: <do-not-reply(a)example.com> Delivered-To: kay@localhost Received: from localhost ([127.0.0.1]) by MacBookPro.local (JAMES SMTP Server 2.3.0) with SMTP ID 718 for <kay@localhost>; Sun, 1 Apr 2007 10:13:04 +0900 (JST) Date: Sun, 1 Apr 2007 10:13:04 +0900 (JST) From: =?ISO-2022-JP?B?GyRCNElNfTxUGyhC?= <do-not-reply(a)example.com> To: =?ISO-2022-JP?B?GyRCJDEkJBsoQg==?= <kay@localhost> Message-ID: <1586395.91175389984187.JavaMail.kazuho(a)MacBookPro.local> Subject: ようこそ MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_9_5186653.1175389984185" ------=_Part_9_5186653.1175389984185 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline こんにちは、けいさん こんにちは、世界 ------=_Part_9_5186653.1175389984185-- -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1133) Subject in I18N mail

by Kay Arita (JIRA)

Subject in I18N mail -------------------- Key: JBSEAM-1133 URL: http://jira.jboss.com/jira/browse/JBSEAM-1133 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 1.2.1.GA Environment: Mac OS X, JAVA1.5.0_07 Reporter: Kay Arita Assigned To: Pete Muir Subject in I18N must be encoded base64 as well as from and to field. --- From: =?ISO-2022-JP?B?GyRCNElNfTxUGyhC?= <do-not-reply(a)example.com> To: =?ISO-2022-JP?B?GyRCJDEkJBsoQg==?= <kay@localhost> Subject: ようこそ -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1152) problem with s:convertEntity and h:selectManyListbox

by Vitaly Masterov (JIRA)

problem with s:convertEntity and h:selectManyListbox ---------------------------------------------------- Key: JBSEAM-1152 URL: http://jira.jboss.com/jira/browse/JBSEAM-1152 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: Fedora Core 5, JBoss AS 4.0.5.GA, JBoss Seam 1.2.1.GA, JSF RI 1.2_04P01 Reporter: Vitaly Masterov have trouble with <s:convertEntity/>. On my display appear error message: "Conversion Error setting value '1 2' for '#{resourceCatalog.resources}'." My env: JBoss 4.0.5 JBoss Seam 1.2.1.GA Sun RI 1.2_04 I have two entity bean: Resource and ResourceCatalog: Code: @javax.persistence.Entity @javax.persistence.Table(name = "RESOURCE_CATALOG") @javax.persistence.NamedQuery(name = "ResourceCatalog.findAll", query = "select resourceCatalog from ResourceCatalog AS resourceCatalog") public class ResourceCatalog implements java.io.Serializable, Comparable<ResourceCatalog> { private static final long serialVersionUID = 4982628439420436925L; // ----------- Attribute Definitions ------------ private java.lang.String name; private java.lang.String description; private java.lang.Long id; // --------- Relationship Definitions ----------- private java.util.Set<my.model.resource.Resource> resources = new java.util.TreeSet<my.model.Resource>(); @javax.persistence.Column(name = "NAME", nullable = false, insertable = true, updatable = true) public java.lang.String getName() { return name; } public void setName(java.lang.String value) { this.name = value; } @javax.persistence.Column(name = "DESCRIPTION", nullable = false, insertable = true, updatable = true) public java.lang.String getDescription() { return description; } public void setDescription(java.lang.String value) { this.description = value; } @javax.persistence.Id @javax.persistence.GeneratedValue(strategy = javax.persistence.GenerationType.AUTO) @javax.persistence.Column(name = "ID", nullable = false, insertable = true, updatable = true) public java.lang.Long getId() { return id; } public void setId(java.lang.Long value) { this.id = value; } @javax.persistence.ManyToMany() @javax.persistence.JoinTable ( name = "RESOURCE_CATALOGS2RESOURCES", joinColumns = {(a)javax.persistence.JoinColumn(name = "RESOURCE_CATALOG_IDC", referencedColumnName = "ID")}, inverseJoinColumns = {(a)javax.persistence.JoinColumn(name = "RESOURCE_IDC", referencedColumnName = "ID")} ) public java.util.Set<my.model.resource.Resource> getResources() { return this.resources; } /** * Set the resources * * @param resources */ public void setResources (my.model.resource.Resource> resources) { this.resources = resources; } ...................... } Code: @javax.persistence.Entity @javax.persistence.Table(name = "RESOURCE") @javax.persistence.Inheritance(strategy = javax.persistence.InheritanceType.JOINED) @javax.persistence.NamedQuery(name = "Resource.findAll", query = "select resource from Resource AS resource") public class Resource implements java.io.Serializable, Comparable<Resource> { private static final long serialVersionUID = 265906204510520252L; private java.lang.String name; private java.lang.String description; private java.lang.Long id; private java.util.Set<my.model.ResourceCatalog> resourceCatalogs = new java.util.TreeSet<my.model.ResourceCatalog>(); @javax.persistence.Column(name = "NAME", nullable = false, insertable = true, updatable = true) public java.lang.String getName() { return name; } public void setName(java.lang.String value) { this.name = value; } @javax.persistence.Column(name = "DESCRIPTION", nullable = false, insertable = true, updatable = true) public java.lang.String getDescription() { return description; } public void setDescription(java.lang.String value) { this.description = value; } @javax.persistence.Id @javax.persistence.GeneratedValue(strategy = javax.persistence.GenerationType.AUTO) @javax.persistence.Column(name = "ID", nullable = false, insertable = true, updatable = true) public java.lang.Long getId() { return id; } public void setId(java.lang.Long value) { this.id = value; } @javax.persistence.ManyToMany(mappedBy = "resources") public java.util.Set<my.model.resource.ResourceCatalog> getResourceCatalogs() { return this.resourceCatalogs; } public void setResourceCatalogs (java.util.Set<my.model.resource.ResourceCatalog> resourceCatalogs) { this.resourceCatalogs = resourceCatalogs; } ................................. } Snippet from components.xml: Code: <factory name="resource" value="#{resourceHome.instance}" /> <fwk:entity-home name="resourceHome" entity-class="my.model.resource.Resource" entity-manager="#{entityManager}"> </fwk:entity-home> <fwk:entity-query name="resourceCollection" ejbql="from Resource" /> <factory name="resourceCatalog" value="#{resourceCatalogHome.instance}" /> <fwk:entity-home name="resourceCatalogHome" entity-class="my.model.resource.ResourceCatalog" entity-manager="#{entityManager}"> </fwk:entity-home> <fwk:entity-query name="resourceCatalogCollection" ejbql="from ResourceCatalog" /> Snippet from edit page: Code: <h:selectManyListbox value="#{resourceCatalog.resources}"> <s:selectItems var="field" label="#{field.name}" value="#{resourceCollection.resultList}" /> <s:convertEntity/> </h:selectManyListbox> I get validation error message when i try submit entity ResourceCatalog. I start seam-ui from examples folders on my system configuration and it start successful. I do not see different between these applications. Also, I have success result when I use h:selectOneMenu and ManyToOne association. -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1100) s:convertEnum doesn't throw exception if setter is missing

by Christian Bauer (JIRA)

s:convertEnum doesn't throw exception if setter is missing ---------------------------------------------------------- Key: JBSEAM-1100 URL: http://jira.jboss.com/jira/browse/JBSEAM-1100 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Christian Bauer Assigned To: Pete Muir Priority: Minor <h:selectOneMenu value="#{a.attribute.visibility}"> <s:convertEnum/> <s:enumItem enumValue="SYSTEM" label="Only System" /> <s:enumItem enumValue="USER" label="Allow user override" /> <s:enumItem enumValue="NODE" label="Allow per-node override" /> </h:selectOneMenu> 'attribute' is a class that was missing the setVisibility(enum) method. I did not get any exception and spent some time tracking down the problem. My request was just skipping the INVOKE APPLICATION phase and doing RENDER RESPONSE. No faces message either. -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-944) Parallel root conversations with dynamic conversation entries

by Christian Bauer (JIRA)

Parallel root conversations with dynamic conversation entries ------------------------------------------------------------- Key: JBSEAM-944 URL: http://jira.jboss.com/jira/browse/JBSEAM-944 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor The use case here is two navigation links are visible on all pages and they are supposed to start new root conversations whenever they are clicked (not nest, not join). Navigation via conversation list/switcher. <s:link action="doFoo" propagation="none"/> <s:link action="doBar" propagation="none"/> Mapping: <page view-id="/mypage.xhtml"> <rule if-outcome="foo"> <begin-conversation flush-mode="MANUAL"/> <redirect view-id="/fooConversation.xhtml"/> </rule> <rule if-outcome="bar"> <begin-conversation flush-mode="MANUAL"/> <redirect view-id="/barConversation.xhtml"/> </rule> <page> <page view-id="/fooConversation.xhtml"> My Name is #{fooBackingBean.name} </page> <page view-id="/barConversation.xhtml"> My Name is #{barBackingBean.name} </page> The issue is how page descriptions in conversation entries are stored, in the SeamPhaseListener after RENDER RESPONSE. Sequence: 1. Call /mypage.xhtml and click on 'foo', a conversation is created and /fooConversation.xhtml is rendered 2. Click on 'doBar', a request is send to /fooConversation.xhtml?actionOutcome=doBar - no conversation is propagated 3. The navigation rule kicks in and does the redirect, before that happens, AFTER RENDER RESPONSE is executed and the prepareBackswitch() stores the conversation entries, /barConversation.xhtml is rendered 4. Click on 'doFoo', a request is send to /barConversation.xhtml?actionOutcome=doFoo - no conversation is propagated 5. The navigation rule kicks in and does the redirect, before that happens, AFTER RENDER RESPONSE is executed and the prepareBackswitch() stores the conversation entries, I GET EXCEPTIONS in the log because "My name is #{fooBackingBean.name}' triggers create() of fooBackingBean which can't be created without the right request parameters - the interesting part is that I still get the name from somewhere, I see it in the conversation switcher So this could either be a bug (because visually it's working, I see the correct conversation description in the switcher UI) that involves resolving of view-id descriptions or I need a different approach to get new root conversations in parallel on every click. -- 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, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1138) propagation=none defined in the target page

by Leo Baschy (JIRA)

propagation=none defined in the target page ------------------------------------------- Key: JBSEAM-1138 URL: http://jira.jboss.com/jira/browse/JBSEAM-1138 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: all Reporter: Leo Baschy There should be a way to write something into a my.page.xml so that when coming into that page from no matter where there will be a new conversation. As usual, temporary unless requested to be long running. But new and empty. That should work no matter whether arriving with or without a conversation. Point is to allow from anywhere to go to certain pages (main, home, index kind of pages) and be sure there is no "old" state in conversations. Like: "Ok, you've been in the sub pages, have done browsing and clicking, we don't know whether our coders got it all right or where you've been, but when you come back here, everything is clean." -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2007