I think all you need is the requires phrase.
On Sat, Aug 15, 2020 at 6:42 PM HRH <hrh...@yahoo.com> wrote:
> Thanks, that was the missing part that caused the error. Do I need to
> revise the statement that begins with the "opens" directive? I took the
> liberty and changed it. The module file looks as follow:
>
> module org.openjfx.fxmavenfxml {
> requires javafx.controls;
> requires javafx.fxml;
> requires javafx.base;
> requires javafx.graphics;
> requires java.base;
> requires javafx.web;
>
> // opens org.openjfx.fxmavenfxml to javafx.fxml;
> opens org.openjfx.fxmavenfxml to javafx.web;
> exports org.openjfx.fxmavenfxml;
> }
>
> Should I keep the new "opens org.openjfx.fxmavenfxml to javafx.web;"?
>
> Thanks again
> On Sunday, August 16, 2020, 12:49:46 AM GMT+4:30, Chuck Davis <
> cjgun...@gmail.com> wrote:
>
>
> Did you revise the module file?
>
> On Sat, Aug 15, 2020 at 11:34 AM HRH <hrh...@yahoo.com.invalid> wrote:
>
> Hi,
>
> I had an FXML file that was working fine until I added an UI component
> "WebView". The <?import javafx.scene.web.WebView?> in the FXML file
> marked as an error because somehow the javafx.web from the JavaFx\Lib is
> not seen. I have already modified the POM file to include this dependency
> as follow alas the FXMLLoader.load() failes to load the FXML file and it
> throws a runtime exception:
>
> <dependencies>
> <dependency>
> <groupId>org.openjfx</groupId>
> <artifactId>javafx-controls</artifactId>
> <version>14</version>
> </dependency>
> <dependency>
> <groupId>org.openjfx</groupId>
> <artifactId>javafx-fxml</artifactId>
> <version>14</version>
> </dependency>
> <dependency>
> <groupId>org.openjfx</groupId>
> <artifactId>javafx-web</artifactId>
> <version>14</version>
> </dependency>
> </dependencies>
>
> Any insight as why the <?import javafx.scene.web.WebView?> cause an error?
>
> Thanks in advance.
>
>
