icedtea-web JSObject

[Ao Qi]

On Mon, Mar 25, 2019 at 9:09 PM Jiri Vanek <jvanek at redhat.com> wrote:
>
> Yo-u have jre with fx bundled?
Yes.
> otherwise uninstall of javafx for a while should not be problem.
>
> Another opinion is to build witout plugin.jar and all it sdeps (rhino.jr and friends)  Do you really
> need javaws --html support?
>
> /me doubts :)

I am not an expert of icedtea-web. I will try your suggest tomorrow. Thank you.

Actually, we are not users of icedtea-web. We just build icedtea-web,
do some tests and provide rpm. We do not know how our users use it
very much:(

I think the error happened during a test, is it ok to just
comment/skip this test?

Thanks,
Ao Qi

>
> J.
> On 3/25/19 2:00 PM, Ao Qi wrote:
> > Hi Jiri,
> >
> > On Mon, Mar 25, 2019 at 8:23 PM Jiri Vanek <jvanek at redhat.com> wrote:
> >>
> >> Ths means, that you have javafx installed. Java fx have its own implementation of jsobject. If you
> >> remove it, all below should disappear.
> >>
> >
> > Yes, we solve this problem by removing jre/lib/ext/jfxrt.jar. However,
> > I wonder if there is a more elegant way? One problem of removing
> > jre/lib/ext/jfxrt.jar is that, when building srpm, it is not suitable
> > to removing jfxrt.jar of the system jdk.
> >
> > Thanks,
> > Ao Qi
> >
> >> J.
> >> On 3/25/19 3:28 AM, huangxg wrote:
> >>> When I "make check" on icedtea-web-1.7.1, there will be errors about JSObject, as follows:
> >>>
> >>> //icedtea-web-1.7/tests/netx/unit/sun/applet/MethodOverloadResolverTest.java:217: error: JSObject is
> >>> abstract; cannot be instantiated//
> >>> //        assertOverloadOrder(new JSObject(0L), JSObject.class, String.class);//
> >>> //                            ^//
> >>> ///icedtea-web-1.7/tests/netx/unit/sun/applet/MethodOverloadResolverTest.java:218: error: JSObject
> >>> is abstract; cannot be instantiated//
> >>> //        assertAmbiguousOverload(new JSObject(0L), Object[].class, String.class);/
> >>>
> >>> I see in the code that @Test has been commented out, but the code has no comment, so that the test
> >>> case will be compiled at compile time.
> >>>
> >>> /    // Turned off until JSObject is unit-testable (privilege problem)//
> >>> ////    @Test//
> >>> //    public void testJSObjectOverloading() {//
> >>> //        // based on http://jdk6.java.net/plugin2/liveconnect/#OVERLOADED_METHODS//
> >>> //        assertOverloadOrder(new JSObject(0L), JSObject.class, String.class);//
> >>> //        assertAmbiguousOverload(new JSObject(0L), Object[].class, String.class);//
> >>> //    }/
> >>>
> >>> Can you comment out all the code in this test case? Or is there a way around this mistake?
> >>>
> >>>
> >>
> >>
> >> --
> >> Jiri Vanek
> >> Senior QE engineer, OpenJDK QE lead, Mgr.
> >> Red Hat Czech
> >> jvanek at redhat.com    M: +420775390109
>
>
> --
> Jiri Vanek
> Senior QE engineer, OpenJDK QE lead, Mgr.
> Red Hat Czech
> jvanek at redhat.com    M: +420775390109