Hi all,
I’m having problems when using showFormInDialog in the webclient.
We use Servoy version 5.1.0 -build 956.
We are calling several showFormInDialogs from other showFormInDialogs. When enableAnchors is true, and we open several showFormDialogs in the browser, we receive this error message in the dialog:
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
We receive this error in a dialog which is not active. The dialog pops up on top of the active dialog.
The browser javascript error message is:
System error: -2146697204. Error processing resource ‘http://www.w3.org/TR/html4/loose.dtd’.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.1)
Timestamp: Mon, 15 Mar 2010 07:52:39 UTC
Message: System error: -2146697204.
Line: 0
Char: 0
Code: 0
URI: http://www.w3.org/TR/html4/loose.dtd
We want to use enableAnchors in our solution because the solution should be resized according to the browser size.
There are more strange things happening when opening a showFormDialog. (since updating to Servoy version 5.1.0) I think this is also caused by the setting enableAnchors. When opening a showFormDialog, sometimes the forms below the dialog disappear. And the background flickers.
Is anyone else experiencing this? Thanks for your reply.
can you open a case with a sample in our support system ? ( http://www.servoy.com/s )
We cannot reproduce the “The XML page cannot be displayed” error in a sample solution. Because we don’t know exactly what’s the cause of the error.
When we receive the error message in our live solution, we see the following error message in the Server Log. We cannot relate this error to our source code:
2010-04-02 11:49 http-80-7 ERROR com.servoy.j2db.util.Debug Error rendering the page settingUserMain
java.lang.NullPointerException
at com.servoy.j2db.server.headlessclient.Zjb.access$400(Zjb.java:9)
at com.servoy.j2db.server.headlessclient.Zqc.respond(Zqc.java:8)
at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:299)
at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119)
at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at com.servoy.j2db.server.servlets.Zk.doGet(Zk.java:5)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
at java.lang.Thread.run(Unknown Source)
2010-04-02 11:49 http-80-7 ERROR org.apache.wicket.RequestCycle null
java.lang.NullPointerException
at com.servoy.j2db.server.headlessclient.Zjb.access$400(Zjb.java:9)
at com.servoy.j2db.server.headlessclient.Zqc.respond(Zqc.java:8)
at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:299)
at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119)
at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at com.servoy.j2db.server.servlets.Zk.doGet(Zk.java:5)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
at java.lang.Thread.run(Unknown Source)
Is this stack from Servoy 5.1.0, build 956 ? Did you disable Ajax for your solution ?
Yes we use Servoy version 5.1.0 -build 956. And servoy.webclient.useAjax is true.
We have this problem in the dialogs when servoy.webclient.enableAnchors=true.
merijnp:
Yes we use Servoy version 5.1.0 -build 956. And servoy.webclient.useAjax is true.
We have this problem in the dialogs when servoy.webclient.enableAnchors=true.
Do you have a sample to illustrate this ? If so, please open a case with it.
We cannot reproduce this in a sample solution. Because we don’t know what causes the error. We cannot relate the error message from the Server Log to our source code. We tried to reproduce in a sample solution, but didn’t get the error. The error from the Server Log doesn’t ring a bell for you?
merijnp:
We cannot reproduce this in a sample solution. Because we don’t know what causes the error. We cannot relate the error message from the Server Log to our source code. We tried to reproduce in a sample solution, but didn’t get the error. The error from the Server Log doesn’t ring a bell for you?
Not sure what happens here, the stack doesn’t explain it. Do you also close some form in dialogs when this happen ? Can you post the code that triggers this behavior ?
We don’t close forms when this happens, we open a new form which should be on top. We added a case with id 284149, including a sample solution. This is another problem with showFormInDialog and enableAnchors. But maybe this problem is related to the “The XML page cannot be displayed” error message.
Did you have a look at our case?
We reproduced the error in our sample solution, see attached. [attachment=0]popupSolution_2.servoy[/attachment] Open the solution in IE7 or IE8. In this solution you can open several dialogs. When we open a dialog in IE, the content is loaded. Then the content disappears for a second (form is blank) and returns, it looks like something is reloaded. When we click a button before the dialog is “reloaded”, we receive the error message. For example: Open the sample solution. Click until you see the Third settings form. In this form, click one of the “open” buttons to open the fourth form. Click the button before the dialog is “reloaded”. You have to be fast, or have a slow network connection to get this behaviour. (and try a couple of times) In the server log, the same error message as posted above is logged. Maybe the setting enableAnchors has nothing to do with this behaviour.
popupSolution_2.servoy (53.1 KB)
I can also reproduce the problem in Google Chrome with the sample solution. In Chrome we receive an “Internal error” in the dialog. The same error in the eventlog. In Chrome I don’t see the dialog “reloading”.
I think enableAnchors does have something to do with this problem. enableAnchors needs to be true in our solution. This problem is causing a lot of trouble. At this moment we cannot test our solution in Internet Explorer, because every time we open a dialog, the content disappears. And when the error occurs, we have to restart the browser. We have a deadline at the end of this week. Hope you can help me soon, thanks!
merijnp:
We reproduced the error in our sample solution, see attached. [attachment=0]popupSolution_2.servoy[/attachment] Open the solution in IE7 or IE8. In this solution you can open several dialogs. When we open a dialog in IE, the content is loaded. Then the content disappears for a second (form is blank) and returns, it looks like something is reloaded. When we click a button before the dialog is “reloaded”, we receive the error message. For example: Open the sample solution. Click until you see the Third settings form. In this form, click one of the “open” buttons to open the fourth form. Click the button before the dialog is “reloaded”. You have to be fast, or have a slow network connection to get this behaviour. (and try a couple of times) In the server log, the same error message as posted above is logged. Maybe the setting enableAnchors has nothing to do with this behaviour.
ok, but then I guess this is related to first issue; when we fix the disappearence this issue will also be fixed …
We need to update our customers. But we cannot due to this problem. When will this be fixed?
merijnp:
We need to update our customers. But we cannot due to this problem. When will this be fixed?
This issue is not assigned to me. This is very tricky issue, caused by IE bug with iframes. Hope we can find a workaround.
We didn’t have this problem in version 4.1.2
Yesterday I added a url to our internal solution to the case mentioned in this post before.
Has that been received correctly?
(Support case didn’t have a submit button or something, so I’m in doubt if it has gone correctly).
Janssenjos:
Yesterday I added a url to our internal solution to the case mentioned in this post before.
Has that been received correctly?
(Support case didn’t have a submit button or something, so I’m in doubt if it has gone correctly).
Yes, it has been received.
How is this going?
Do we still have to keep our internal solutions exposed?
Thanks.