>>>>> Do you know why Fedora/Red Hat builds of xulrunner disables the >>>>> javaxpcom ? >>>> >>>> No, but you should ask Chris Aillon. He can give you the details. >>> Chris, do you know the answer ? >>> >>> Do you know why Fedora/Red Hat builds of xulrunner disables the >>> javaxpcom in their xulrunner ? > > It's not so much as disabling it (it's disabled by default). We just > haven't enabled it. AFAIK, it's not really that maintained by > upstream and when I've played with it in the past[*], it sometimes > would refuse to compile or link when doing version upgrades. Since > we need to push out security updates very quickly -- we've had two > critical firedrills in the past month alone where we needed to go > from issue reported to packages built, QE done, and errata shipped > live in a 24 hour span -- I am not very keen on adding additional > code that is prone to breaking. Thanks for the info. I don't have the resources to promise that the javaxpcom will work/be maintained so i guess for now we will just continue to bundle the eclipse/mozilla custom built one so any security issues is not exposed in the general browser but only in the development tooling where it is less of an issue since it is primarily used to access local sites. /max