August 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-769) Per view exception handling

by Peter Muir (JIRA)

Per view exception handling --------------------------- Key: JBSEAM-769 URL: http://jira.jboss.com/jira/browse/JBSEAM-769 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Reporter: Peter Muir Would be useful to be able to handle an exception differently depending on the current view id - especially for foo.page.xml style pages.xml -- 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, 4 months

6
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1898) EntityQuery hints map is defined as <String, String> instead of <String, Object>

by david castannon (JIRA)

EntityQuery hints map is defined as <String, String> instead of <String, Object> -------------------------------------------------------------------------------- Key: JBSEAM-1898 URL: http://jira.jboss.com/jira/browse/JBSEAM-1898 Project: JBoss Seam Issue Type: Bug Reporter: david castannon EntityQuery hints map field is defined as <String, String> instead of <String, Object> used at hibernate method setHint of QueryImpl. So, if you want to set, e.g., "org.hibernate.cacheMode" hint with CacheMode.REFRESH jboss throws exception. -- 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, 4 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4237) Support message-driven POJO's

by Nikolay Elenkov (JIRA)

Support message-driven POJO's ----------------------------- Key: JBSEAM-4237 URL: https://jira.jboss.org/jira/browse/JBSEAM-4237 Project: Seam Issue Type: Feature Request Components: Async Reporter: Nikolay Elenkov Currently, if you want to use JMS in a Seam project, you have to deploy it as an EAR in a JEE application server, and use MessageDriven beans. However, JMS messaging is sometimes required in web (WAR) projects as well, and changing the application to and EAR and/or the application server is not possible. Seam should make it easy to use message-driven POJO's (POJO's that act as asynchronous receivers for JMS messages) in a web project, supporting all Seam features (injection, transaction management, etc.). It could be implemented by integrating Jencks (http://jencks.codehaus.org/) for example or built on top of ActiveMQ. Cf. Spring support for message-driven POJO's: http://static.springframework.org/spring/docs/2.5.x/reference/jms.html#jm... -- 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, 4 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3349) LDAPIdentityStore generates invalid filter on listUsers method

by Vinicius Carvalho (JIRA)

LDAPIdentityStore generates invalid filter on listUsers method -------------------------------------------------------------- Key: JBSEAM-3349 URL: https://jira.jboss.org/jira/browse/JBSEAM-3349 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Vinicius Carvalho The Filter generated by the component is creating an invalid query, the format is this: (objectClass={0})(objectClass={1}) Where it should be: (&(objectClass={0})(objectClass={1})) We've fixed it by overriding the method with our own ldapidentitystore, below is just the minimal chage: StringBuilder userFilter = new StringBuilder(); userFilter.append("(&"); Object[] filterArgs = new Object[getUserObjectClasses().length]; for (int i = 0; i < getUserObjectClasses().length; i++) { userFilter.append("("); userFilter.append(getObjectClassAttribute()); userFilter.append("={"); userFilter.append(i); userFilter.append("})"); filterArgs[i] = getUserObjectClasses()[i]; } userFilter.append(")"); -- 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, 4 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3685) Add "rendered" attribute to s:decorate

by Chris Simons (JIRA)

Add "rendered" attribute to s:decorate -------------------------------------- Key: JBSEAM-3685 URL: https://jira.jboss.org/jira/browse/JBSEAM-3685 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.SP1, 2.1.0.GA, 2.1.0.CR1, 2.1.0.BETA1, 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA Reporter: Chris Simons Add an optional "rendered" attribute to s:decorate, if possible. If evaluated to false, this would preclude rendering of the template/component. I haven't seen a request like this in the past (I hope I didn't miss anything). -- 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, 4 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4349) Provide static injection option via @In

by asookazian (JIRA)

Provide static injection option via @In --------------------------------------- Key: JBSEAM-4349 URL: https://jira.jboss.org/jira/browse/JBSEAM-4349 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.2.0.GA Environment: n/a Reporter: asookazian Currently injection in Seam via @In is dynamic only. By dynamic, we mean that the instance variable that is associated with the @In annotation is refreshed with the latest value from the specified context every time a business method is invoked (specifically prior to the invocation). Request is to add a facility to allow developer to specify static injection only for that particular @In annotation instance. Add an optional element named "type" to @In. example: @In(type=static) private String foo; The default type or behavior will be dynamic. The purpose of this request is to support use case implementations that do not require dynamic injections but merely one-time static injections like Spring DI setter or constructor injections. This will help with performance as well as there will not be unnecessary "refreshing" of the instance variables via dynamic injection in those cases that are not needed. -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4344) testreport target does not pick up all test results on Windows

by Jozef Hartinger (JIRA)

testreport target does not pick up all test results on Windows -------------------------------------------------------------- Key: JBSEAM-4344 URL: https://jira.jboss.org/jira/browse/JBSEAM-4344 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.2.0.GA Environment: Windows Server 2003 R2 Ant 1.7.0 Reporter: Jozef Hartinger Assignee: Norman Richards Fix For: 2.2.1.CR1 1.) Run the testall target 2.) Run the test-report target The generated test report contains only 54 testcases however more 200 tests are run during the testsuite execution. For instance, all the unit tests are missing as well as dvdstore, etc The faster way to reproduce is to directly call "ant test" in examples/dvdstore and then test-report in {seam.dir} Looks like removing colons from the name of each test in testng.xml fixes the problem -- 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, 4 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2852) Scan for @WebRemote on extended Interfaces

by Alessandro Di Pasquale (JIRA)

Scan for @WebRemote on extended Interfaces ------------------------------------------- Key: JBSEAM-2852 URL: http://jira.jboss.com/jira/browse/JBSEAM-2852 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Environment: 2.0.1.GA Reporter: Alessandro Di Pasquale Assigned To: Shane Bryzak Priority: Minor Class org.jboss.seam.remoting.InterfaceGenerator does not scan for WebRemote.class-Annotation in extended Business-Interfaces -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4121) pages.xml not hot deploying in 2.1.1 GA

by Cody Lerum (JIRA)

pages.xml not hot deploying in 2.1.1 GA --------------------------------------- Key: JBSEAM-4121 URL: https://jira.jboss.org/jira/browse/JBSEAM-4121 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: JBAS 4.2.3 GA, Seam 2.1.1GA, JDK 6 Update 13 Reporter: Cody Lerum pages.xml do not seem to be getting hot deployed after a change. I have debug mode true and facelets.DEVELOPMENT=true. All my view pages are hot deploying fine but updating the navigation rules in pages.xml requires a server restart. -- 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, 4 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3666) Natural Conversations: conversation id evaluated to null

by Arron Ferguson (JIRA)

Natural Conversations: conversation id evaluated to null -------------------------------------------------------- Key: JBSEAM-3666 URL: https://jira.jboss.org/jira/browse/JBSEAM-3666 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Ubuntu/Linux 7.10, Tomcat 6.0.16 Reporter: Arron Ferguson This is a repost of https://jira.jboss.org/jira/browse/JBSEAM-3368 which was closed but not fixed. The following errors occur with natural conversations (based on the attached use case): If I'm at page 4 (http://localhost:8080/test/register4.html) and I type: http://localhost:8080/test/register2.html (i.e., without the natural conversation id appended at the end like this: http://localhost:8080/test/register1.html?memberID=2), I get the following evaluated to null error: conversation id evaluated to null: regmem The exception is spewed to the log file but shouldn't be and should use the rules in the pages.xml file for error handling (see attached project). However, even if I type http://localhost:8080/test/register1.html?memberID=2, this is still broken because the rules in the pages.xml file are not being honored. The pages.xml file specifies: <rule if="#{memberreg.acceptedInformation}"> <redirect view-id="/register3.xhtml"/> </rule> Which states that this state should cause a redirect which is not happening. So, to recap, The included test project includes the Ant build script, and in the third party directory a list of the jar files used. Note: you don't need the DA.jar file. The jboss-archive-browsing.jar file is not included in the JBoss Seam download and so I had to grab it from the JBoss site. The version of the jboss-archive-browsing.jar (according to the manifest in the jar) is: Implementation-Version: 2.0.2.Alpha As I mentioned in the previous version of this bug report that was closed, Shane mentioned that there was a little more "noise" in the file than needed. It was quickly discovered however that this project test file was useful for spotting other bugs (I believe he said it helped him find another bug) and so I'm hoping that the same perspective will be used this time around as well. This example project in particular can be used to test many of the use cases and ensure that natural conversation processing is robust. -- 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, 4 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2009