TeamDev Support: Message List - JExplorer Demo & Samples

Hi Vladimir,

Not sure if it has to do with the certificate issue. I use the same code for both IE and Mozilla except of course for the line:  browser = BrowserFactory.createBrowser(BrowserType.IE); and it works just fine for Mozilla. I will give it another try once the certificate issues related to IE are resolved.

Thanks,

Navin

Hi Navin,

We have tried to reproduce this issue with opening a new window but without success. The NewWindowManager.evaluateWindow method is always invoked.

Please note that in JxBrowser 2.0 API NewWindowManager functionality is quite different than in JExplorer. When you register a NewWindowManager it means that you set a global NewWindowManager for all Browser instances (IE, Mozilla, Safari). You don't need to register a NewWindowManager for each Browser instance anymore.

Regards,

Vladimir Ikryanov

Hi Navin,

I will try to reproduce this issue with NewWindowHandler and let you know the results.

Regards,

Vladimir Ikryanov

Vladimir,

I have to build a test example for you to test the security issue. I will to do it soon. As far as new window manager goes I do exactly what you have in the sample code. It works for Mozilla but when I switch to IE as window type the same code does not even get executed. I put a breakpoint in insertBrowser(...) code and it never gets there in case of IE while it case of Mozilla it does.

Thanks,

Navin

Hi Navin,

Thanks for clarification regarding security issue. I will try to reproduce this behavior. It would be great if you provide me a link to a web page on which you can reproduce security issue.

> I was testing the IE version of it and noticed that the methods of implemented NewWindowManager do not get executed. It seems to works in case of Mozilla.

You mean that NewWindowManager.evaluateWindow method is never invoked? That's weird. Could you please provide me steps to reproduce this issue?

Regards,

Vladimir Ikryanov

Vladimir,

A couple of things regarding security issue:

1. When I choose to use IE as BrowserType, I don't get any warning at all in case of certificate problems and I did not put any code to ignore security warning. This should not happen. Default IE IE behavior is to show warning dialog. It works perfectly in JExplorer.

2. In case of Mozilla I did put the code you suggested and I ran it in debug mode to make sure that the SecurityHandler is set is used but the page still throws exception saying invalid security certificate.

I was testing the IE version of it and noticed that the methods of implemented NewWindowManager do not get executed. It seems to works in case of Mozilla.

Thanks,

Navin

Hi Navin,

> In JExplorer I didn't have to write any code for handling security. It simply poped up a warning dailog in case it couldn't verify the certificate. Shouldn't the behavior be similiar?

You may see by default the certificate popup warning dialog in JExplorer because this is default behavior when certificate problems occur in Internet Explorer engine. But Mozilla engine in this case just displays a web page with warning message, this is default behavior for Mozilla engine. I agree that behavior should be similar, this is why we provide HttpSecurityHandler that allows processing security problems in the same maner for different engines.

Please note that for different engines could be different secrutity problem reasons. Please try to register HttpSecurityHandler that allows ignoring all security problems. For example:

    browser.setHttpSecurityHandler(new HttpSecurityHandler() {
        public HttpSecurityAction onSecurityProblem(Set problems) {
            return HttpSecurityAction.CONTINUE;
        }
    });

> Also in case of JExplorer I had to call Browser.close() before I could remove the browser panel from the window containing it. All this was done because the browser window would not be disposed otherwise. Is this still the case?

Yes, to dispose Browser instance you should invoke the Browser.dispose method (Browser.close analog in JExplorer).

Regards,

Vladimir Ikryanov

Hi Vladimir,

In JExplorer I didn't have to write any code for handling security. It simply poped up a warning dailog in case it couldn't verify the certificate. Shouldn't the behavior be similiar?

Also in case of JExplorer I had to call Browser.close() before I could remove the browser panel from the window containing it. All this was done because the browser window would not be disposed otherwise. Is this still the case?

Thanks for the sample.

I used the following code for security when I was testing:

browser.setHttpSecurityHandler(new HttpSecurityHandler() {
            public HttpSecurityAction onSecurityProblem(Set problems) {
                // when the problem in invalid certificate, then just ignore it
                if (problems.contains(SecurityProblem.NOT_TRUSTED_CERTIFICATE) || (problems.contains(SecurityProblem.MOVING_FROM_HTTP_TO_HTTPS))) {
                    return HttpSecurityAction.CONTINUE;
                }
                return HttpSecurityAction.ABORT;
            }
        });

When I run in debug mode I see that "return HttpSecurityAction.CONTINUE" gets execute but it still throws the exception dialog.

Regards,

Navin

Hi Navin,

Thanks for your feedback.

1. JxBrowser allows working only with its own XULRunner and doesn't provide functionality that allows running with installed FireFox. Maybe in one of the next version of JxBrowser we will add such ability, but right now we don't have such plans.

2. As for the SSL security issue - JxBrowser 2.0 API provides functionality that allows handling all SSL security issues. Please see the HandleSecurityProblemsSample sample from JxBrowser 2.0 EAP distribution package that demonstrates how to do this.

3. In JxBrowser 2.0 we changed API for handling/listening opening a new window. Please see the PopupBrowserSample from distribution package or you can find it in attachment.

Regards,

Vladimir Ikryanov

Hi Navin,

I found several issues with the "Call wa rejected by callee" fix so I disabled this fix until found a new solution. I have implemented several improvements for this fix today and published the updated build on our ftp: ftp://ftp.teamdev.com/updates/jexplorer-2.2.32.zip

The issue that the "Call wa rejected by callee" fix causes in Browser.close functionality. When you dispose Browser instance with this fix, sometimes you may see exception. But with the latest update I wasn't able to reproduce this issue with our tests.

Please try this updated build and let me know the results.

Regards,

Vladimir Ikryanov