June 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1324) javascript error in IE6 when remote call does not render anything to response.

by Keith Naas (JIRA)

javascript error in IE6 when remote call does not render anything to response. ------------------------------------------------------------------------------ Key: JBSEAM-1324 URL: http://jira.jboss.com/jira/browse/JBSEAM-1324 Project: JBoss Seam Issue Type: Bug Components: Remoting Reporter: Keith Naas Assigned To: Shane Bryzak If an exception occurs in the remote call, it is caught by the ExecutionHandler, logged, and the request is ended. Since nothing is written to the response, the document is empty. In IE6 this causes a javascript error. Something like this should get rid of the problem. ### Eclipse Workspace Patch 1.0 #P jboss-seam Index: src/remoting/org/jboss/seam/remoting/remote.js =================================================================== RCS file: /cvsroot/jboss/jboss-seam/src/remoting/org/jboss/seam/remoting/remote.js,v retrieving revision 1.3 diff -u -r1.3 remote.js --- src/remoting/org/jboss/seam/remoting/remote.js 1 May 2007 00:08:12 -0000 1.3 +++ src/remoting/org/jboss/seam/remoting/remote.js 15 May 2007 14:39:58 -0000 @@ -624,13 +624,16 @@ var bodyNode; var context = new Seam.Remoting.__Context; - for (var i = 0; i < doc.documentElement.childNodes.length; i++) + if (doc.documentElement) { - var node = doc.documentElement.childNodes.item(i); - if (node.tagName == "header") - headerNode = node; - else if (node.tagName == "body") - bodyNode = node; + for (var i = 0; i < doc.documentElement.childNodes.length; i++) + { + var node = doc.documentElement.childNodes.item(i); + if (node.tagName == "header") + headerNode = node; + else if (node.tagName == "body") + bodyNode = node; + } } if (headerNode) -- 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, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1333) Methods annotated with @Restrict("#{s:hasPermission cause uncaught Auth Exception

by Damian Harvey (JIRA)

Methods annotated with @Restrict("#{s:hasPermission cause uncaught Auth Exception --------------------------------------------------------------------------------- Key: JBSEAM-1333 URL: http://jira.jboss.com/jira/browse/JBSEAM-1333 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: JBoss 4.0.5GA Seam 1.2.1GA Reporter: Damian Harvey If I have a method annotated with a permission eg: @Restrict("#{s:hasPermission('vesselHome','persist',vesselHome.instance)}") and an unauthorised User tries to access this method then the resulting org.jboss.seam.security.AuthorizationException is not intercepted as per the entry in pages.xml and is propagated to the browser. pages.xml: <exception class="org.jboss.seam.security.AuthorizationException"> <redirect view-id="/secure/home.xhtml"> <message>#{messages['org.jboss.seam.security.AuthorizationException']}</message> </redirect> </exception> method: @Name("myObjectHome") public class MyObjectHome extends EntityHome<Vessel> { @Override @Transactional @Restrict("#{s:hasPermission('vesselHome','persist',vesselHome.instance)}") public String persist() { String status = super.persist(); return status; } } -- 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, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1005) Don't use conversationIsLongRunning by default

by Gavin King (JIRA)

Don't use conversationIsLongRunning by default ---------------------------------------------- Key: JBSEAM-1005 URL: http://jira.jboss.com/jira/browse/JBSEAM-1005 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA Now that we have conversation-required=true, conversationIsLongRunning is kinda superfluous. -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1392) Returning to parent conversation by redirect is broken

by Gavin King (JIRA)

Returning to parent conversation by redirect is broken ------------------------------------------------------ Key: JBSEAM-1392 URL: http://jira.jboss.com/jira/browse/JBSEAM-1392 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Reporter: Gavin King Assigned To: Gavin King Priority: Blocker Fix For: 1.3.0.ALPHA This broke when we introduced the "business" conversation ids" -- 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, 7 months

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

17 years, 7 months

2
19
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1086) Actions on navigation rules

by Gavin King (JIRA)

Actions on navigation rules --------------------------- Key: JBSEAM-1086 URL: http://jira.jboss.com/jira/browse/JBSEAM-1086 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA Christian wants to be able to add event listeners to rules, especially for handling redirection stuff, eg, see JBSEAM-906. -- 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, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1390) deprecate Seam.invalidateSession() and use a Seam component

by Gavin King (JIRA)

deprecate Seam.invalidateSession() and use a Seam component ----------------------------------------------------------- Key: JBSEAM-1390 URL: http://jira.jboss.com/jira/browse/JBSEAM-1390 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.ALPHA should have done this ages ago! -- 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, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1376) Document dispatcher strategies

by Gavin King (JIRA)

Document dispatcher strategies ------------------------------ Key: JBSEAM-1376 URL: http://jira.jboss.com/jira/browse/JBSEAM-1376 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.ALPHA Need to doc the new design for async dispatchers -- 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, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1386) Option for limit simultaneous logins for users

by Mariusz Smykula (JIRA)

Option for limit simultaneous logins for users ---------------------------------------------- Key: JBSEAM-1386 URL: http://jira.jboss.com/jira/browse/JBSEAM-1386 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.2.1.GA Reporter: Mariusz Smykula For example, If we limit logins for users to one, then only newest login should be valid (older should be invalidate). Or, if this is "won't fix", Please give me any advice how to do 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1357) Allow to set NamingStrategy in HibernateFactory (patch included)

by Przemyslaw Jaskierski (JIRA)

Allow to set NamingStrategy in HibernateFactory (patch included) ---------------------------------------------------------------- Key: JBSEAM-1357 URL: http://jira.jboss.com/jira/browse/JBSEAM-1357 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: Microcontainer Reporter: Przemyslaw Jaskierski Fix For: 1.3.0.ALPHA Attachments: HibernateFactory.diff.zip I cannot find any way to set my non-default NamingStrategy using microcontainer-instantiated HibernateFactory. My complex mapping cannot be instantiated. Following patch makes this possible. After applying, user can setup NamingStrategy using something like: <bean name="complexNamingStrategy"class="x.y.z.ComplexNamingStrategy"/> <bean name="hibernateSessionFactoryFactory" class="org.jboss.seam.microcontainer.HibernateFactory"> <property name="cfgResourceName">conf/hibernate/hibernate.cfg.xml</property> <property name="namingStrategy"> <inject bean="complexNamingStrategy"/> </property> </bean> -- 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, 7 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2007