February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-542) Migrate back to seperate microcontainer/lib and embedded-ejb/lib distribution and create an ant/lib dir

by Gavin King (JIRA)

Migrate back to seperate microcontainer/lib and embedded-ejb/lib distribution and create an ant/lib dir ------------------------------------------------------------------------------------------------------- Key: JBSEAM-542 URL: http://jira.jboss.com/jira/browse/JBSEAM-542 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.0.BETA1 we should consider splitting this stuff back out again -- 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, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-952) Automatically search for unknown wiki links

by Christian Bauer (JIRA)

Automatically search for unknown wiki links ------------------------------------------- Key: JBSEAM-952 URL: http://jira.jboss.com/jira/browse/JBSEAM-952 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Don't bail out on /wiki/SomeUnknownWikiName or /wiki/someunknownwikiname but do a document search for 'unknownwikiname' instead. Similar to how http://www.php.net/searchforthis works. -- 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, 10 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-953) Don't create HttpSession until we *really* need it

by Gavin King (JIRA)

Don't create HttpSession until we *really* need it -------------------------------------------------- Key: JBSEAM-953 URL: http://jira.jboss.com/jira/browse/JBSEAM-953 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA This requires a thorough code audit. -- 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, 10 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-906) Support redirect component for navigation out of conversational scope

by Christian Bauer (JIRA)

Support redirect component for navigation out of conversational scope --------------------------------------------------------------------- Key: JBSEAM-906 URL: http://jira.jboss.com/jira/browse/JBSEAM-906 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor It's about my favorite subject, the "history" or "cancel" button. Assume the following (RC == Root Conversation, NC == Nested Conversation): RC(1) -> NC(2) -> NC(3) I can render a Cancel button on each page in NC 2 and 3 with the action=#{conversation.endAndRedirect()} to get back to any parent NC or RC. I can not render a Cancel button on each page in RC, because there is no "parent view-id" we could redirect to. So my Cancel button on these pages has to call some logic I've written on my RC backing component. I propose to extend the Conversation.endAndRedirect() method with the following logic: - If called in a NC, do what it currently does. - If called in a RC, check if the 'redirect' component is present in RC, if yes, call 'redirect.execute()' If this would be available, I could completely control conversation navigation and the navigation history through nesting conversations (with s:link or pages.xml) and by ensuring that a RC has a prepared 'redirect' component when it is started. All Cancel buttons would be able to use action="#{conversation.endAndRedirect()}" and would either get the user "one up" in the conversation stack or "out" of conversational scope. -- 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, 10 months

2
19
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-743) HTTP BASIC and DIGEST authentication

by Gavin King (JIRA)

HTTP BASIC and DIGEST authentication ------------------------------------ Key: JBSEAM-743 URL: http://jira.jboss.com/jira/browse/JBSEAM-743 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Priority: Minor Fix For: 1.1.5.GA Find some way to support these awful things. Probably have to parse headers ourselves. Just copy paste some code from Tomcat or Acegi or whatever (whichever is the least obfuscated and over-designed). -- 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, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-802) Support for code coverage (emma) in Seam-gen projects

by Mariusz Smykula (JIRA)

Support for code coverage (emma) in Seam-gen projects ----------------------------------------------------- Key: JBSEAM-802 URL: http://jira.jboss.com/jira/browse/JBSEAM-802 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Mariusz Smykula This can be very helpful for developers using seam-gen :) -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-718) Make exception object available in redirected/rendered view

by Peter Muir (JIRA)

Make exception object available in redirected/rendered view ----------------------------------------------------------- Key: JBSEAM-718 URL: http://jira.jboss.com/jira/browse/JBSEAM-718 Project: JBoss Seam Issue Type: Feature Request Reporter: Peter Muir -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-898) s:hasRole, etc in EL in pages.xml and other places

by Gavin King (JIRA)

s:hasRole, etc in EL in pages.xml and other places -------------------------------------------------- Key: JBSEAM-898 URL: http://jira.jboss.com/jira/browse/JBSEAM-898 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.7.GA Because of MyFaces inability to implement the JSF spec correctly, EL functions are not supported in lots of places they are useful. We need to find a better way. -- 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, 10 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-842) s:hasRole() in jBPM EL.

by Gavin King (JIRA)

s:hasRole() in jBPM EL. ----------------------- Key: JBSEAM-842 URL: http://jira.jboss.com/jira/browse/JBSEAM-842 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical Currently, jBPM uses its own forked EL (which is a problem to begin with....). This means that it can't see the s: functions. We need to fix this problem ASAP. -- 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, 10 months

3
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-668) method bindings with a parameter don't work in facelets tag source files

by Guy Veraghtert (JIRA)

method bindings with a parameter don't work in facelets tag source files ------------------------------------------------------------------------ Key: JBSEAM-668 URL: http://jira.jboss.com/jira/browse/JBSEAM-668 Project: JBoss Seam Issue Type: Bug Reporter: Guy Veraghtert Attachments: seam-bug-method-parameter.zip Method bindings with a parameter on a parameterized target bean don't work in a facelets tag source file. java.lang.NullPointerException at org.jboss.seam.ui.facelet.MethodExpressionHelper.findParamTypes(MethodExpressionHelper.java:146) at org.jboss.seam.ui.facelet.MethodExpressionHelper.invokeTheExpression(MethodExpressionHelper.java:98) at org.jboss.seam.ui.facelet.ParamMethodExpression.invoke(ParamMethodExpression.java:62) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96) -- 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, 10 months

5
7
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 February 2007