March 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4059) Better document the PersistentPermissionResolver section

by Samuel Mendenhall (JIRA)

Better document the PersistentPermissionResolver section -------------------------------------------------------- Key: JBSEAM-4059 URL: https://jira.jboss.org/jira/browse/JBSEAM-4059 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Samuel Mendenhall Priority: Minor The section "15.6.10. PersistentPermissionResolver" http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html_single/#d0e11931 needs to be better documented as right now there is just the explanation of the annotations and the configuration without a concrete example to tie it all together and to explain how to populate the permissions in the DB. -- 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

17 years

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4058) Add canned message to NotNull annotation

by Valerie Griffin (JIRA)

Add canned message to NotNull annotation ---------------------------------------- Key: JBSEAM-4058 URL: https://jira.jboss.org/jira/browse/JBSEAM-4058 Project: Seam Issue Type: Feature Request Reporter: Valerie Griffin The default validation message for unexpected null values doesn't provide much debug information, especially if it's from a cascaded record.... In my code, I've changed the annotation everywhere it occurs to code like: @NotNull(message = "MyTbl.fieldName must not be null") I didn't change GetPropertyAnnotation.ftl because I don't know how to refer to the table and field names there. -- 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

17 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4054) <s:enumItems /> tag

by Jakub Janczak (JIRA)

<s:enumItems /> tag ------------------- Key: JBSEAM-4054 URL: https://jira.jboss.org/jira/browse/JBSEAM-4054 Project: Seam Issue Type: Feature Request Components: JSF Controls Environment: all Reporter: Jakub Janczak Fix For: The future Create a taghandler that adds to it's parent all the enum values' selectItems of the desired class. Something like: <h:selectOneMenu value="#{value}"> <s:convertEnum /> <s:enumItems class="com.class.EnumClass" /> </h:selectOneMenu> we could even omit that the class attribute, but it would need us to acces the value of the select menu before it's rendered (what would be not desired). Can do it if you want. -- 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

17 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3091) Extend s:decorate by adding #{disabled} attribute

by Scott Bader (JIRA)

Extend s:decorate by adding #{disabled} attribute ------------------------------------------------- Key: JBSEAM-3091 URL: http://jira.jboss.com/jira/browse/JBSEAM-3091 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.2.GA Reporter: Scott Bader Desire is to conditionally format based on the disabled/enabled state of the component. Refer also to forum question: Is it possible to pass the 'disabled' attribute into s:decorate like #{required} and #{invalid} are? Has anyone figured out a nice workaround for this? http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115864 -- 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-4035) Calling getPage outside of a JSF request causes NPE

by V K (JIRA)

Calling getPage outside of a JSF request causes NPE --------------------------------------------------- Key: JBSEAM-4035 URL: https://jira.jboss.org/jira/browse/JBSEAM-4035 Project: Seam Issue Type: Bug Reporter: V K Please see https://jira.jboss.org/jira/browse/JBSEAM-1128 from early 2007. The issue is verified to be fixed with the given code being changed/removed, but 2.0.3.CR1 shows that exact piece of code as in the original bug report. The original reporter stated: "However calling getPage() outside of a JSF request throws NPE as Pages.getSuffix() calls FacesContext.getCurrentInstance().getExternalContext().getInitParameter(ViewHandler.DEFAULT_SUFFIX_PARAM_NAME);" Gavin King then said "Yep, the bug is fixed in current RI versions (from 03), so I removed this code." That code is not removed, however. -- 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

17 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3984) Problem while serialization of POJO components during session replication

by Marius Oancea (JIRA)

Problem while serialization of POJO components during session replication ------------------------------------------------------------------------- Key: JBSEAM-3984 URL: https://jira.jboss.org/jira/browse/JBSEAM-3984 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows Reporter: Marius Oancea On replication of conversation scoped seam components referencing an stateless EJB you get: 14:23:01,480 ERROR [JBossCacheService] externalizeSession(): exception occurred externalizing session SessionBasedClusteredSession[id: yQ8dwYuawaXaMRejYNyIWA**. node1 lastAccessedTime: 1236169379964 version: 46 lastOutdated: 0] java.io.NotSerializableException: java.lang.reflect.Method at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) at java.util.HashMap.writeObject(HashMap.java:984) at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:89 0) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13 33) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav a:1284) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java :1369) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13 41) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav a:1284) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) at java.util.ArrayList.writeObject(ArrayList.java:569) at sun.reflect.GeneratedMethodAccessor154.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:89 0) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13 33) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav a:1284) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java :1369) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13 41) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav a:1284) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap. Cluster was composed of 2 nodes. Each node on a different machine. I have tryed to follow the hints of http://markmail.org/message/lhf5tsnwczsonp7e#query:Seam%20TransactionMeta... so that i made userTransactionas transient but i get the same results. -- 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

17 years

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4044) Security NullPointerException regarding @RoleGroups

by Grzegorz Matuszewski (JIRA)

Security NullPointerException regarding @RoleGroups --------------------------------------------------- Key: JBSEAM-4044 URL: https://jira.jboss.org/jira/browse/JBSEAM-4044 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.1.GA Reporter: Grzegorz Matuszewski Using roles without role groups may lead to NullPointerException in JpaIdentityStore class. Methods getRoleGroups and listRoleMembers validate existence od role groups with test: if (roleGroupsProperty != null) { ... } but should by if (roleGroupsProperty.isSet()) { ... } because roleGroupProperty is always instantiated when using roles. See forum reference. -- 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

17 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4027) http://jboss.com/products/seam/pageflow-2.1.xsd has binding="last" attribute on wrong element

by David Schlotfeldt (JIRA)

http://jboss.com/products/seam/pageflow-2.1.xsd has binding="last" attribute on wrong element --------------------------------------------------------------------------------------------- Key: JBSEAM-4027 URL: https://jira.jboss.org/jira/browse/JBSEAM-4027 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: David Schlotfeldt This is the newest xsd file for pageflow I can find. (its what is used in the user guide too) http://jboss.com/products/seam/pageflow-2.1.xsd Anyways, I think its the newest but it has a mistake. It has the "binding" attribute is on <process-state> but is suppose to be on the <sub-process> element. I checked jpdl's java source and tested the use of the attribute on the two tags. With the binding attribute on sub-process it works (of course.. to make it work the xsd file can't be referenced by the xml file sine the xml file isn't then valid according to the xsd file.) Please fix the xsd file. -- 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

17 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4032) Vague exception when using a factory on a page-scoped component

by Matthew Lieder (JIRA)

Vague exception when using a factory on a page-scoped component --------------------------------------------------------------- Key: JBSEAM-4032 URL: https://jira.jboss.org/jira/browse/JBSEAM-4032 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Matthew Lieder The following code will cause an unhelpful NPE to be thrown by JSF when the factory is accessed: @Name("someComponent") @Scope(ScopeType.PAGE) public class SomeComponent implements Serializable { @Factory("someVar") public String getSomeVar() { return null; } } While I believe I remember reading that using that particular type of factory method on a page-scoped component isn't supported (supported by the fact that removing the @Scope makes it work), the exception should at least be somewhat helpful in debugging the problem. NPE's with no messages are about as unfriendly as one can get. -- 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

17 years

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4041) debug page fails for applications using prefix based servlet mapping

by Norman Richards (JIRA)

debug page fails for applications using prefix based servlet mapping -------------------------------------------------------------------- Key: JBSEAM-4041 URL: https://jira.jboss.org/jira/browse/JBSEAM-4041 Project: Seam Issue Type: Bug Reporter: Norman Richards Assignee: Norman Richards Fix For: 2.1.2.CR1 JBSEAM-3426 removes the servletPath from URLs generated by MockViewHandler. This is incorrect and causes failures apps, like the blog app, that use a servlet mapping like /seam/*. -- 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

17 years

1
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 March 2009