|
A nice post bellow and http://www.theserverside.com/home/thread.jsp?thread_id=20383&article_count=43#89471 .V -------- Original Message --------
Hi, Kevin A. Burton (of Apache Jetspeed and NewsMonster fame) has uncovered a gem titled "LiveConnect requirements for Applications Developed with the XUL Tookit" stashed away in a bugzilla attachment in his PeerFear blog. If I may quote from the paper: We are implementing around 8 different applications using Mozilla's GRE / XUL Toolkit to perform various Back Office tasks that will be rolled out to approx. 1000 desktops. More apps will follow over the next few years. Our impression of LiveConnect is that generally it is an excellent piece of software. It allows us to integrate _javascript_ -> Java communications within our XUL applications pretty transparently / seemlessly with the minimal amount of "red-tape" (explicit calls to LiveConnect to enable use of Java). We wish this to continue. All of these applications form the client-tier of an n-tier architecture. They can communicate with different line-of-business servers in different departments via one or more of the following: 1) Java RMI <-> EJBs 2) SOAP (using Apache Axis) <-> Web Services 3) JMS <-> MQ Series In addition, the ability to embed 3rd party applets / beans directly into the XUL screens may also be required in the future. A user may run multiple instances of the same XUL application and / or instances of different XUL applications simultaneously. Different XUL applications will require different JVM settings, including specification of different Java Extension directories and classpaths. Furthermore, we are using WebSphere app client 4.0 to communicate with the EJBs via RMI. As you might be aware there is an incompatibility between WebSphere app client 4.0 and Sun JRE 1.4.x. In general, we cannot rely on simply using the last JRE to be installed. We need to ensure the applications do not break other Java plug-in users and that they do not break our applications. Hence, we need the ability to specify the Java Runtime Environment for LiveConnect to use in each application (e.g. as you can with the "type='application/x-java-applet;jpi version=1.3.1'" in the case of applets). We have tried using Java components more generally within the XUL applications (e.g. the implementation of a state machine), but cannot get the Java -> _javascript_ communications (via netscape._javascript_.JSObject) working. The call to JSObject.call() completes without exceptions, but we do not seem to be able to access the _javascript_ object's properties - we get always get 'undefined' back. Also, even though we have tried digitally signing both the XUL application (chrome) archives and Java JAR files, we cannot get LiveConnect to run the Java code outside of the sandbox. Currently we install a modified java.policy file that grants the necessary permissions to use RMI. However, this is not satisfactory and we would like to see the XUL / LiveConnect security more integrated and LiveConnect able to run trusted code outside the sandbox. Full story @ http://bugzilla.mozilla.org/attachment.cgi?id=127732&action=""> - Gerald --------------------------------------- XUL News Wire - Subscribe/Unsubscribe @ http://lists.sourceforge.net/lists/listinfo/xul-announce --------------------------------------- ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ xul-announce mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-announce |
