October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3502) Make org.jboss.seam.security.management.JpaIdentityStore.generatePasswordHash() protected instead of private.

by Stephan Kleine (JIRA)

Make org.jboss.seam.security.management.JpaIdentityStore.generatePasswordHash() protected instead of private. ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3502 URL: https://jira.jboss.org/jira/browse/JBSEAM-3502 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.CR1 Reporter: Stephan Kleine I really like the updated security model and would love to use your JpaIdentityStore implementation but since I use Jasypt ( http://www.jasypt.org/ ) to handle my passwords I have to adapt it a bit. As far as I can see the easiest way would be to subclass your JpaIdentityStore implementation and override generatePasswordHash() and authenticate() - the rest should work just fine out of the box. But, since generatePasswordHash() is private, I would have to override more methods just to redirect the generatePasswordHash() calls which I would like to avoid. So please make org.jboss.seam.security.management.JpaIdentityStore.generatePasswordHash() protected because it makes the security model more customizable, like for situations described above, without compromising security. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3512) Fix ConcurrentModificationException in ServerConversationContext.flush()

by Shane Bryzak (JIRA)

Fix ConcurrentModificationException in ServerConversationContext.flush() ------------------------------------------------------------------------ Key: JBSEAM-3512 URL: https://jira.jboss.org/jira/browse/JBSEAM-3512 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.CR1 Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 2.1.0.GA During ServerConversationContext.flush(), it is possible for further additions to the conversation context to be added during the passivation phase. Specifically, the call to PersistenceContexts.instance() within PassivatedEntity.passivateEntity() can cause an extra attribute to be added to the conversation context, causing a ConcurrentModificationException. -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3508) Generic Transform for s:graphicImage

by Daniel Roth (JIRA)

Generic Transform for s:graphicImage ------------------------------------ Key: JBSEAM-3508 URL: https://jira.jboss.org/jira/browse/JBSEAM-3508 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.1.0.CR1, 2.0.3.CR1 Reporter: Daniel Roth Assignee: Daniel Roth Priority: Minor Image transforms for s:graphicImage is a really neat feature. However, there are quite a few reqests for features and additions and I think it will really hard to satisfy all at the same time. Therefore it would be great if one could define one's own image transformer. The tag would essentially delegate the transformation to a defined class: public abstract class UITransformImageGeneric extends UIComponentBase implements ImageTransform { public void applyTransform(Image image) throws IOException { ImageTransform transform = null; Class transformClass = null; try { transformClass = Class.forName(getImplementation()); transform = (ImageTransform) transformClass.newInstance(); } catch (Exception e) { throw new IllegalArgumentException("Cannot instanciate class: " + getImplementation(), e); } transform.applyTransform(image); } public abstract String getImplementation(); public abstract void setImplementation(String implementation); } To be able to pass paramaters one could use the f:param tag: <s:graphicImage ...> <s:genericTransformImage implementation="org.foo.bar.MyTransform"> <f:param name="myParam" value="#{myBean.someValue}"/> </s:genericTransformImage> </s:graphicImage> What would then be the easiest way to pass those values to the delegate? 1) By reflection on the delegate? 2) Resolve the values and put them in a <String,Object> map and pass along with the applyTransform? 3) Other suggestions? -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3495) getResultList() throwing arrayindexoutof bounds exception on empty result

by kanwar sangha (JIRA)

getResultList() throwing arrayindexoutof bounds exception on empty result ------------------------------------------------------------------------- Key: JBSEAM-3495 URL: https://jira.jboss.org/jira/browse/JBSEAM-3495 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.CR1 Environment: All Reporter: kanwar sangha We are extending EntityQuery and overriding @Override public List getResultList() { edList = super.getResultList(); return edList; } Sun-appserver 9.1 mysql version - 6.0 Seam - 2.1.0.CR1 exception Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:546) at java.util.ArrayList.get(ArrayList.java:321) at org.jboss.seam.framework.Query.getRenderedEjbql(Query.java:240) at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:175) at org.jboss.seam.framework.EntityQuery.initResultList(EntityQuery.java:73) at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:65) at com.prod.sps.session.EventdefinitionList.getResultList(EventdefinitionList.java:44) To Reproduce - Just do a seam-gen on a table try to pull up the "entitylist.xhtml" page with no data in the table. -- 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-3390) Documentation does not describe quartz config yet it's required

by Stuart Robertson (JIRA)

Documentation does not describe quartz config yet it's required --------------------------------------------------------------- Key: JBSEAM-3390 URL: https://jira.jboss.org/jira/browse/JBSEAM-3390 Project: Seam Issue Type: Bug Components: Async Affects Versions: 2.1.0.BETA1, 2.0.2.SP1 Environment: n/a Reporter: Stuart Robertson Priority: Minor The Seam documentation describes how to use annotations to setup quartz-scheduled recurring events. Following these instructions doesn't produce the desired results - nothing is scheduled in quartz. See the referenced forum post, which helped me resolve the issue. It's simply a matter of setting up seam.quartz.properties. But that isn't mentioned in the docs for 2.0.2 or the pending 2.1.0 release. I think anyone trying to use this portion of seam will have the same issue. It should be in the docs. -- 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-3446) Update documentation for new Entity Security with JPA behaviour

by Mike Pettypiece (JIRA)

Update documentation for new Entity Security with JPA behaviour --------------------------------------------------------------- Key: JBSEAM-3446 URL: https://jira.jboss.org/jira/browse/JBSEAM-3446 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.0.BETA1 Reporter: Mike Pettypiece I've noticed that the behaviour of Entity security with JPA has changed in Seam 2.1. Previously in Seam 2.0 the following Rule could be used: rule CheckUserPermission when c: PermissionCheck( target == "user" ) Role( name == "admin" ) then c.grant(); end; However in Seam 2.1 "target" is the actual entity instance rather than the Seam component name of the entity so the rule needs to be updated as follows: rule CheckUserPermission when user: User() c: PermissionCheck( target == user ) Role( name == "admin" ) then c.grant(); end; The documentation should be updated to note this. -- 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
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3375) Refactor excel and pdf document servlet config to a common place now that the DocumentServlet/Store is common

by Nicklas Karlsson (JIRA)

Refactor excel and pdf document servlet config to a common place now that the DocumentServlet/Store is common ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3375 URL: https://jira.jboss.org/jira/browse/JBSEAM-3375 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.0.BETA1 Reporter: Nicklas Karlsson Priority: Minor Both the IText and Excel sections deal with configuring the DocumentServlet to serve files with proper extensions. This section could be moved out since the component itself was refactored out of pdf to support both file types. In addition, is there a namespace error in the pdf-section:? <components xmlns="http://jboss.com/products/seam/document" xmlns:pdf="http://jboss.com/products/seam/document"> <document:document-store use-extensions="true" /> </components> Should it be just one xmlns:document="http://jboss.com/products/seam/document" ? -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2444) Create a common "Extending Your seam-gen Application" chapter for the reference guide

by Jay Balunas (JIRA)

Create a common "Extending Your seam-gen Application" chapter for the reference guide ------------------------------------------------------------------------------------- Key: JBSEAM-2444 URL: http://jira.jboss.com/jira/browse/JBSEAM-2444 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Jay Balunas Create a common "Extending Your seam-gen Application" chapter. This will be used for common changes and upgrades for the basic seam-gen application. It should be written as container agnostic where possible. The individual container chapters will document any specific changes needed. This will allow the container specific chapters to reference this chapter rather than each document this. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1262) Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes)

by Nathaniel Stoddard (JIRA)

Should be able to customize Hibernate validation messages based on context (by page, or role like Seam component scopes) ------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1262 URL: http://jira.jboss.com/jira/browse/JBSEAM-1262 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard Currently, each validation specified a single message resource to be used as the error message. It would be helpful if there was some way to customize the error messages to be used such that in one case "Contact address is required." is displayed, while in others "Billing address is required", for example. Annotating model classes with validation rules limits the reuse of those classes since the validation messages offer limited flexibility. Since validated fields in the domain classes aren't necessarily associated with a UIInput on a page, it would be helpful to have more flexible annotations, such as: @MaxLength(messages = {@Message(role='contactForm', value='contact.too_long'), @Message(role='billingForm', value='billing.too_long')}) private String field; Also needed would be some way of indicated to the UIView which 'role' should be used when validation takes place. -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2364) Resource-bundle from different modules bug

by Pierre Ingmansson (JIRA)

Resource-bundle from different modules bug ------------------------------------------ Key: JBSEAM-2364 URL: http://jira.jboss.com/jira/browse/JBSEAM-2364 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Windows XP, Eclipse, Seam running in a Tomcat 5.5.25 Reporter: Pierre Ingmansson We have a application that consists of several modules. Each module has it's own resource-bundle and therefore we created several "components.xml", one per module. In every "components.xml" we have the following (the name of the bundle varies per module off course..): <core:resource-loader> <core:bundle-names> <value>mymodule_messages</value> </core:bundle-names> </core:resource-loader> In a perfect world you would expect this to work, but it doesn't. Only the resource-bundle declared in the "components.xml" that was loaded last, is loaded into the ResourceLoader. My guess is that Seam stores all "component.xml"-parameters in some property during load, and when a new "components.xml" is loaded the settings are overwritten. Only the settings in the last "component.xml" is loaded.. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2008