[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1271) setting onreadystatechange to null causing error in IE6
by Keith Naas (JIRA)
setting onreadystatechange to null causing error in IE6
-------------------------------------------------------
Key: JBSEAM-1271
URL: http://jira.jboss.com/jira/browse/JBSEAM-1271
Project: JBoss Seam
Issue Type: Bug
Components: Remoting
Environment: IE6
Reporter: Keith Naas
Assigned To: Shane Bryzak
Fix For: 1.2.1.GA
When testing remoting in IE6, we noticed a reoccurrence of the old IE remoting bug JBSEAM-267.
For a good explanation of how to workaround this, see: http://www.quirksmode.org/blog/archives/2005/09/xmlhttp_notes_a_1.html
Here is the patched remote.js
### 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.2
diff -u -r1.2 remote.js
--- src/remoting/org/jboss/seam/remoting/remote.js 24 Apr 2007 23:52:34 -0000 1.2
+++ src/remoting/org/jboss/seam/remoting/remote.js 30 Apr 2007 23:38:07 -0000
@@ -604,7 +604,7 @@
if (req.readyState == 4)
{
Seam.Remoting.hideLoadingMessage();
- req.onreadystatechange = null;
+ req.onreadystatechange = function() {};
if (req.status == 200)
{
--
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, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1231) Cannot pass empty parameters in *.page.xml
by Alan Fehr (JIRA)
Cannot pass empty parameters in *.page.xml
------------------------------------------
Key: JBSEAM-1231
URL: http://jira.jboss.com/jira/browse/JBSEAM-1231
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.1.GA
Reporter: Alan Fehr
When passing an empty parameter in a redirect in a *.page.xml, I get a NullPointerException. Empty parameters work when used on pages (with s:link and <f:param name="paramName" />) but when used as mentioned I get:
2007-04-23 16:31:13,437 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/zdb].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
java.lang.NullPointerException
at org.jboss.seam.pages.Param.getValueFromModel(Param.java:93)
at org.jboss.seam.pages.RedirectNavigationHandler.navigate(RedirectNavigationHandler.java:36)
at org.jboss.seam.pages.Rule.execute(Rule.java:91)
at org.jboss.seam.pages.Navigation.navigate(Navigation.java:65)
at org.jboss.seam.core.Pages.navigate(Pages.java:131)
at org.jboss.seam.jsf.SeamNavigationHandler.handleNavigation(SeamNavigationHandler.java:32)
at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
at javax.faces.component.UICommand.broadcast(UICommand.java:106)
at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)
--
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, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1259) Action annotated with @Begin(nested=true) does not actually execute within the nested conversation
by Michael Youngstrom (JIRA)
Action annotated with @Begin(nested=true) does not actually execute within the nested conversation
--------------------------------------------------------------------------------------------------
Key: JBSEAM-1259
URL: http://jira.jboss.com/jira/browse/JBSEAM-1259
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
If I have a method annotated with @Begin I would expect that method to be executed inside of the conversation it is beginning. This is the case for a top level conversation however if beginning a nested conversation "@Begin(nested=true)" the method is not executed within that nested conversation because the nested conversation is not started until after the method returns.
Conversations probably function this way because of the "ifOutcome" attribute. However, I believe it introduces unexpected behavior in the case of nested conversations. For example, I have an action that starts a nested conversation and loads data that I only want to be available for the scope of the current nested conversation. Any conversation variables I create in the action are actually created in the outer conversation and not in the new nested conversation because the nested conversation is not actually created until after my action executes.
Options:
Perhaps for nested conversations we can begin the conversation before calling invocation .proceed in the ConversationInterceptor and then end the conversation if "ifOutcome" is not satisfied?
Any other ideas?
Mike
--
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, 11 months