Runs on Windows 32/64-bit JDK/JRE 1.5.x and higher.
With the JExplorer API, you can download HTML pages, navigate through them or to other pages, set and get HTML content, prepare page for printing, work with advanced browser options, and many other things.
If you app need a custom context menu shown on a web page instead of a standard shown by the browser, you can easily set it.
JExplorer supports both persistent and session cookies. You are free to use them in a variety of ways: create, modify or delete, set and get their name, value, domain and other information. Learn more.
With JExplorer you can make a screenshot of a web page, either its visible part or the entire content. See example.
JExplorer provides 3 components: a visual browser object for embedding in a Swing UI, a “headless” browser for working with web pages without displaying them, and an Automation-based browser component which you can use without embedding in a Swing UI.
You can work with DOM of web pages in many ways: manage elements in a document, modify element attributes, apply element styles, fire an event on some element, manipulate data in the HTML form elements, etc.
JExplorer allows you to configure global proxy settings for ftp, http, https, gopher, socks as well as those available for a current process without affecting global proxy configuration. See example.
JExplorer provides support for native peers whereby you can work directly with COM interfaces of the Internet Explorer COM API to access functionality, which is not exposed explicitly by the library.
Robot class allows you to emulate mouse actions, keyboard input, set focus to HTML element, search for an element within a page, populate an input control with values, etc.
JExplorer is created to help Java developers resolve the following tasks:
By using our products or any related documentation, you accept the Terms and Conditions of the Product License Agreement.
JExplorer integrates with MS Internet Explorer 6.0 and higher on Windows XP, 7 and 8.
Compared to JxBrowser, JExplorer doesn’t deploy the native web browser engine binaries and integrates with installed MS IE. Since JExplorer integrates only with MS IE, it supports only Windows platform. JxBrowser is a cross-platform library based on Google Chromium engine.
Yes, JExplorer can be used in Java Applet and JWS applications. You can find more information about it in JExplorer Programmer’s Guide .
A: You can distribute unlimited number of copies of your product with our library enclosed. Please use Runtime License for distribution of your product.
A: Runtime License is provided free of charge.
A: Please take a look at the Product License Agreement.
A: Yes, you can purchase JExplorer Source Code License; it is provided on a per developer basis. Please contact our sales team if you are interested in this option.
A: Upon purchase of license you will receive a license archive. The archive will contain two JARs: development.jar and runtime.jar. Development.jar is the license that should be used in development process. Runtime.jar should be used to distribute your application to end users.
A: You may want to purchase a Project license, which is more cost-effective in case there are 3 and more developers on the team.
A: The best solution would be to purchase the Unlimited license, which covers any number developers and projects in one company.
No. The Project license is tied to one project only.
A: Yes, our licenses are tied to a company, not to a specific developer. You can transfer licenses to other developers provided that the number of developers, working on your team equals the number of licenses purchased.
John Michelsen, iTKO, Inc.In case you are wondering, why am I trying to get your product to do what I’ve already gotten other products to do? Answer: Your product is stable! And your support is superb.
Akquinet Agile, akquinet.deJExplorer is a really cool tool…
Scott Chan, Currenex Inc.My company, Currenex, ended up purchasing a JExplorer license. So far we are happy with it, we have used it to replace JDIC which was quite problematic for us. For us the JExplorer API was much richer than the JDIC API.