September 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1773) Document jar versions bundled with Seam

by steve tynor (JIRA)

Document jar versions bundled with Seam --------------------------------------- Key: JBSEAM-1773 URL: http://jira.jboss.com/jira/browse/JBSEAM-1773 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: steve tynor I am running into a bug which from googling may be fixed in a newer hibernate or ejb3 release, but I can't be sure -- I can't tell from the jboss-seam-1.2.1-GA.zip file just what versions of various jars are bundled. The Seam 2.0-BETA distribution does not appear to be any better documented. Before te next release, please update the lib/readme.txt to include details of each jar file's version and/or change their filenames (e.g., from hibernate-all.jar to hibernate-all.x.y.z.jar) so we can know what versions we're using. If I'm just blind and not looking in the right place, my apologies, and please just point me to the docs. -- 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

18 years, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1976) Add org.jboss.seam.security.Identity.getRoleNames()

by jarkko Lietolahti (JIRA)

Add org.jboss.seam.security.Identity.getRoleNames() --------------------------------------------------- Key: JBSEAM-1976 URL: http://jira.jboss.com/jira/browse/JBSEAM-1976 Project: JBoss Seam Issue Type: Patch Components: Security Affects Versions: 1.2.1.GA Reporter: jarkko Lietolahti Add new method (e.g.) getRoleNames which returns a list of role names (or either Group.classes). This is because I need to check if the current user has any roles at all. And currently I need to write: Set roles = Identity.instance().getSubject().getPrincipals(Group.class); if (roles.isEmpty()) { return null; // user without any roles } And I'd like to be able to write: Identity.instance().getRoleNames().isEmpty(); -- 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

18 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1812) date format specified doesn't always match short type

by Pierre Raoul (JIRA)

date format specified doesn't always match short type ----------------------------------------------------- Key: JBSEAM-1812 URL: http://jira.jboss.com/jira/browse/JBSEAM-1812 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Reporter: Pierre Raoul In InterpolatorTest.java, the test with "{0,date,short}" can fail with some locales. The pattern "M/d/y" is not always equivalent to DateFormat.SHORT. With Assert.assertEquals(DateFormat.getDateInstance(DateFormat.SHORT).format(date), interpolator.interpolate("{0,date,short}", date)); it's ok. -- 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

18 years, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1495) Add option to overide ImageCaptchaService service in CaptchaImage

by Mariusz Smykula (JIRA)

Add option to overide ImageCaptchaService service in CaptchaImage ----------------------------------------------------------------- Key: JBSEAM-1495 URL: http://jira.jboss.com/jira/browse/JBSEAM-1495 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.3.0.ALPHA Reporter: Mariusz Smykula This is necessary to extend this class and make my own implementation (simpler than default). Making service protected or adding setter can help. I need to implement my own create() method. If there is other solution, please give me advice. @Create public void create() { // service = new DefaultManageableImageCaptchaService(); SimpleListImageCaptchaEngine engine = new SimpleListImageCaptchaEngine(); engine .addFactory(new GimpyFactory(new RandomWordGenerator( "ABCDEFGHIJKLMNOPQRSTUVWXYZ"), new ComposedWordToImage( new RandomFontGenerator(new Integer(12), new Integer(16)), new FunkyBackgroundGenerator( new Integer(200), new Integer(100)), new RandomTextPaster(new Integer(6), new Integer(10), Color.BLACK)))); service = new DefaultManageableImageCaptchaService( new FastHashMapCaptchaStore(), engine, 180, 100000, 75000); } -- 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

18 years, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1293) Page parameters not working

by Chris Rudd (JIRA)

Page parameters not working --------------------------- Key: JBSEAM-1293 URL: http://jira.jboss.com/jira/browse/JBSEAM-1293 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Reporter: Chris Rudd Im attempting to use the Page parameter feature detailed in section 5.1.1.1 of the documentation. <pages> <page view-id="/edit.xhtml"> <param name="id" value="#{editor.id}"/> </page> </pages> based on my understanding of the functiuonality if i go the url /edit.xhtml?id=foobar then editor.id should be set to 'foobar'. This is not occuring. After tracing the code it seems like this is where the magic should happen: AbstractSeamPhaseListener.java : 70 //apply page parameters to the model if ( facesContext.getRenderResponse() ) { Pages.instance().applyRequestParameterValues(facesContext); } else { Pages.instance().applyViewRootValues(facesContext); } Im using myfaces 1.1.4 with server side view state. What appears to be happening is that myfaces will restore the saved view state (im not sure it should be, as its a GET request). When this happends facesContext.renderResponse is never called. Thus when it gets to the above code, the page parameters are restored from the wrong location. -- 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

18 years, 5 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1647) Document concept of disinjection

by Matt Drees (JIRA)

Document concept of disinjection -------------------------------- Key: JBSEAM-1647 URL: http://jira.jboss.com/jira/browse/JBSEAM-1647 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor The documentation doesn't talk about disinjection. It surprised me quite a bit when I read the source code for BijectionInterceptor to find that all @In attributes get nulled after method invocation. -- 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

18 years, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1816) Testing and test environment improvments

by Christian Bauer (JIRA)

Testing and test environment improvments ---------------------------------------- Key: JBSEAM-1816 URL: http://jira.jboss.com/jira/browse/JBSEAM-1816 Project: JBoss Seam Issue Type: Task Reporter: Christian Bauer Assigned To: Pete Muir Priority: Blocker 1. Reduce the log level for 'ant testall' so that you actually see which tests fail. I recommend ERROR for everything. -- 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

18 years, 6 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1833) Integration testing for Seam Mail

by Pete Muir (JIRA)

Integration testing for Seam Mail --------------------------------- Key: JBSEAM-1833 URL: http://jira.jboss.com/jira/browse/JBSEAM-1833 Project: JBoss Seam Issue Type: Feature Request Components: Mail, Test Harness Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.0.CR1 Currently you can't integration test Seam mail as we don't provide mocked out mail Session. -- 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

18 years, 6 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1644) DBUnit integration for SeamTest

by Christian Bauer (JIRA)

DBUnit integration for SeamTest ------------------------------- Key: JBSEAM-1644 URL: http://jira.jboss.com/jira/browse/JBSEAM-1644 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Reporter: Christian Bauer Attached a class I wrote to handle my unit tests which require some baseline data in the database. If we want a compile-time dependency on DBUnit in Seam, we should add it to the Seam distribution. -- 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

18 years, 6 months

2
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1959) Wildcard page view-id (*) in pages.xml file with login-required="true" cause error.

by Francisco Ant?ônio (JIRA)

Wildcard page view-id (*) in pages.xml file with login-required="true" cause error. ----------------------------------------------------------------------------------- Key: JBSEAM-1959 URL: http://jira.jboss.com/jira/browse/JBSEAM-1959 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Environment: Windows XP Pro SP2 JBoss AS 4.2.0.GA JBoss Seam 2.0.0.CR1 Reporter: Francisco Ant?ônio The use of <page view-id="*" login-required="true" > in pages.xml file causes the following errors: a) ERROR [ResourceLifecycle] Exception in PhaseListener, render view : beforePhase java.lang.IllegalStateException: No active application scope and b) ERROR [ResourceLifecycle] Exception in PhaseListener, render view : beforePhase java.lang.IllegalStateException: No application context active If login-required="true" is just removed the above errors disappear. -- 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

18 years, 6 months

3
17
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 September 2007