Actually, I found an underlying error: > [...@localhost ~]$ firefox > Java: [JavaPackage java], > file:///home/vik/.mozilla/firefox/whit7rdw.default/extensions/[email protected]/ > ICEDTEAPLUGIN_DEBUG = (null) > Initializing JVM... > classLoaderURL: > file:/home/vik/.mozilla/firefox/whit7rdw.default/extensions/[email protected]/components/lib/firefoxClassLoader.jar > bootstrapClassLoader: java.net.factoryurlclassloa...@1de498 > java.lang.NullPointerException > at > sun.applet.PluginAppletSecurityContext.checkPermission(PluginAppletSecurityContext.java:1002) > at > sun.applet.PluginAppletSecurityContext.handleMessage(PluginAppletSecurityContext.java:658) > at > sun.applet.AppletSecurityContextManager.handleMessage(AppletSecurityContextManager.java:31) > at > sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:248) > at > sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:34) > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at > sun.applet.PluginAppletSecurityContext$5.run(PluginAppletSecurityContext.java:597) > at java.security.AccessController.doPrivileged(Native Method) > at > sun.applet.PluginAppletSecurityContext.handleMessage(PluginAppletSecurityContext.java:594) > at > sun.applet.AppletSecurityContextManager.handleMessage(AppletSecurityContextManager.java:31) > at > sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:248) > at > sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:34) > Caused by: java.lang.SecurityException: Changing the SecurityManager is not > allowed. > at > net.sourceforge.jnlp.runtime.JNLPSecurityManager.checkPermission(JNLPSecurityManager.java:261) > at java.security.Policy.setPolicy(Policy.java:256) > ... 10 more > java.lang.SecurityException: Changing the SecurityManager is not > allowed.Can't bootstrap ClassLoader! > Enabling level: error > Enabling level: error
I am running Firefox 3.0.6 on Fedora 10. Regards Vik Vik Tara wrote: > Hi, > >>> This is because the module defaultstyle is located at >>> ..pub/defaultfiredocs/modules/defaultstyle.. but this path was not >>> included in local.build.properties. I inserted it at modules.root.dirs= >>> .. and after the build I could create a document and edit it with >>> firedocs. > > I've tried the same, and have created a page. Clicking on edit launches > firedocs, but it gets stuck at "Schema Loaded". > > Any ideas on how to debug this further? > > Regards > > > Vik > > > > > Rudolf Korhummel wrote: >> Hi Andreas, hi Vik, >> >> when I tried, I got the following error message: (source code view) >> ... >> <map:mount> - >> file:///home/lenya/lenya-2.0.x/build/lenya/webapp/sitemap.xmap:679:106org.apache.lenya.cms.module.ModuleException: >> The module [defaultstyle] is not registered!full exception chain >> stacktraceorg.apache.cocoon.ProcessingException: Sitemap: error when >> calling sub-sitemap >> ... >> This is because the module defaultstyle is located at >> ..pub/defaultfiredocs/modules/defaultstyle.. but this path was not >> included in local.build.properties. I inserted it at modules.root.dirs= >> .. and after the build I could create a document and edit it with >> firedocs. There are still some problems with this publicaiton. I.e. >> the logo is not shown and there is no content created at the first access. >> >> As far as I remember, the module defaultstyle was created to provide >> faster development without building (modules-copy= false). >> After we had finished developement of our publicaitons in Freiburg, we >> included the code inside the publication. Mabe we can do the same with >> the defaultstyle publication. >> >> WDYT ? >> >> Rudolf >> >> >> >> Am 07.04.2009 um 14:25 schrieb Andreas Hartmann: >> >>> Hi Vik, >>> >>> Vik Tara schrieb: >>>> Hi Andreas, >>>> I followed the instructions you posted, but it fails: >>>>> * >>>>> >>>>> Go to [WWW] >>>>> http://localhost:8888/defaultfiredocs/authoring/tutorial.html >>>>> * >>>>> >>>>> Launch the Firedocs editor using the icon in the top right >>>>> corner of the Firefox window >>>>> >>>> At this point the 'edit' in the firedocs icon is greyed out. I assume >>>> you mean login to the authoring area and then click the icon? >>> yes, exactly. >>> >>>> However on trying to login to the authoring area I get: >>>>> >>>>> An error occurred. >>>>> >>>>> Please contact your system administrator. >>> If you look at the page source of the error page, there should be a >>> stack trace. Does it contain a meaningful exception? >>> >>> -- Andreas >>> >>> >>>> Am I doing something wrong? >>>> Vik >>>> Vik Tara wrote: >>>>> I haven't tried it with the updated code yet - had just seen what was >>>>> going on via the list and also had a look at Firedocs. >>>>> >>>>> I'll try it out via the instructions today and post back comments. >>>>> >>>>> Vik >>>>> >>>>> Andreas Hartmann wrote: >>>>>> Hi Vik, >>>>>> >>>>>> Vik Tara schrieb: >>>>>>> Big thank you for this - it looks awesome! >>>>>> did you already try it? Did the installation instructions work for >>>>>> you? >>>>>> >>>>>> -- Andreas >>>>>> >>>>>> >>>>>>> Andreas Hartmann wrote: >>>>>>>> Hi Lenya devs, >>>>>>>> >>>>>>>> today Thomas Comiotto released the Firedocs extension for Apache >>>>>>>> Lenya >>>>>>>> 2.0.x. He kindly donated the code of this extension to the ASF. >>>>>>>> >>>>>>>> Firedocs is a WYSIWYG XML editor add-on for the Firefox browser. >>>>>>>> It is >>>>>>>> based on a generic XML editing platform. A plug-in concept allows to >>>>>>>> add special GUI elements etc. for editing particular XML document >>>>>>>> types. >>>>>>>> >>>>>>>> The editor was developed by Thomas for the University of Zurich >>>>>>>> and is >>>>>>>> used in production with Lenya 1.2.4 for about a year. >>>>>>>> >>>>>>>> In the course of upgrading their applications to Lenya 2.0.2, the >>>>>>>> Medical Center of the University of Freiburg assigned Thomas and me >>>>>>>> with the integration of the editor in the 2.0.x branch. We used this >>>>>>>> project to make the client-server communication protocol [1] more >>>>>>>> generic. >>>>>>>> >>>>>>>> I created a Wiki page with some instructions how to get started [2]. >>>>>>>> Technical details will follow as soon as I find the time. >>>>>>>> >>>>>>>> A big thank you to the Uni Zurich, the Medical Center of the Uni >>>>>>>> Freiburg and to Thomas Comiotto! >>>>>>>> >>>>>>>> [1] http://firedocs.org/development/docs/remote_editing >>>>>>>> [2] http://wiki.apache.org/lenya/HowToInstallFiredocs >>>>>>>> >>>>>>>> -- Andreas >>>>>>>> >>>>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>> >>> -- >>> Andreas Hartmann, CTO >>> BeCompany GmbH >>> http://www.becompany.ch >>> Tel.: +41 (0) 43 818 57 01 >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
