Re: [Hypercontent-users] Problem with setting up dtd definition
Brought to you by:
alexvigdor
From: Philip R. <phi...@ya...> - 2005-05-13 12:49:36
|
Great, fixed that problem. Now, to the more interesting question. For our initial project, we wanted to use the docbook dtd, http:// www.oasis-open.org/docbook/xml/4.4/docbookx.dtd. However, it uses modules. Here's the question, I can upload the docbook.dtd file into the repository, it now sees it, but now throws errors because it doesn't know where the .mod files are. If I specify the oasis URL above, it causes the channel to time out, and I get nowhere. How would I go about using the docbook dtd, and have it find the included modules from the dtd? Philip On May 12, 2005, at 9:52 PM, Alex Vigdor wrote: > Philip, > Based on the error, it looks like the system was trying to > resolve the dtd location as a relative path - by default, it will > try and resolve relative paths to the working directory, which is > wherever you started the JVM - in other words, the uPortal > directory. This means that the file you're editing still is missing > the leading slash in its doctype - changing the doctype in the > project definition does not change the doctype of existing files, > it only affects files created after the change. > You can either delete the file and recreate it, or download it > and manually change the doctype to also add the leading slash (you > would need to enable the upload editor to upload your change). If > you have a number of files that need the change, you can use the > download zip function to download all the files to your local disk, > where you can use your favorite editor to do a global search and > replace. Zip the changes up and use upload zip to put them back in > the repository. > > Alex > > On May 12, 2005, at 9:28 PM, Philip Rinehart wrote: > > >> Thanks Alex, >> >> Tried that, didn't solve the problem. It seems as if what is >> happening is that the dtd reference is trying to refer to the root >> of the uPortal instance, *not* the dtd contained within the >> repository. Here's the snippet from the error log: >> >> org.jasig.portal.PortalException: PortalException has no ErrorID >> at >> edu.columbia.hypercontent.editors.EditorServant.setStaticData >> (EditorServant.java:90) >> at >> edu.columbia.hypercontent.contentmanager.commands.ChangeEditor.execut >> e(ChangeEditor.java:58) >> at >> edu.columbia.hypercontent.contentmanager.CContentManager.setRuntimeDa >> ta(CContentManager.java:192) >> at >> org.jasig.portal.MultithreadedChannelAdapter.setRuntimeData >> (MultithreadedChannelAdapter.java:61) >> at org.jasig.portal.ChannelRenderer$Worker.run >> (ChannelRenderer.java:417) >> at org.jasig.portal.utils.threading.Worker.run(Worker.java: >> 88) >> Caused by: edu.columbia.hypercontent.CMSException: There was an >> error while processing this directive; /home/local/ >> tomcat5_instances/dev/susan/dtd/docbook.dtd (No such file or >> directory) >> at >> edu.columbia.hypercontent.DocumentFactory.getDocumentFromStream >> (DocumentFactory.java:434) >> at >> edu.columbia.hypercontent.editors.xml.XmlEditor.startSession >> (XmlEditor.java:66) >> at >> edu.columbia.hypercontent.editors.EditorServant.setStaticData >> (EditorServant.java:86) >> ... 5 more >> >> >> This directory: /home/local/tomcat5_instances/dev/susan is the >> root of the uPortal instance. Shouldn't it be referring to the dtd? >> >> Philip >> >> On May 12, 2005, at 4:08 PM, Alex Vigdor wrote: >> >> >>> Hi Philip, >>> My first suggestion is to add the leading "/" on the dtd >>> location: "/dtd/docbook.dtd". You can check the portal log for >>> stack traces, which are handy. What version of uPortal are you >>> running? A doctype does not need to have any forms of output >>> associated with it, and if there is an error parsing the DTD or >>> XML it should display the parsing error. The root can be any >>> element in your DTD. >>> >>> The sitemap is optional - it's just a specific XML document type >>> that the system applies special processing to before it's >>> included, which you can use to set up templates for the site map >>> or navigation structures. You can have none of them, one of them, >>> or as many as you want. You can use your own custom includes & >>> xslt to set up navigation structures, in fact that was the only >>> way prior to version 1.4. The navigation document type was >>> specifically designed to make it easy to do manual sorting of >>> navigation elements in the drag & drop navigation editor, as well >>> as move the logic of sorting and labeling navigation elements out >>> of XSL. We actually use this document type to manage pushed >>> bookmarks channels at Columbia - it is displayed as a nested list >>> of bookmarks, which can be added, updated and re-ordered using >>> the same navigation editor by non-technical users. >>> >>> -Alex >>> >>> On May 12, 2005, at 2:49 PM, Philip Rinehart wrote: >>> >>> >>> >>>> I'm having a problem setting up the definition of a particular >>>> section of my test website. I've specified the dtd I want to >>>> use, which is in the repository, as well as the editor key. >>>> Here's what the line looks like: >>>> >>>> <xml-doctype definition="dtd/docbook.dtd" label="First >>>> Section" path="/*/index.xml" root="body"> >>>> <editor key="xml"/> >>>> </xml-doctype> >>>> >>>> However, when I attempt to do anything to the index.xml file I >>>> end up with the following error: >>>> >>>> Error performing changeEditor: PortalException has no ErrorID >>>> (org.jasig.portal.PortalException) > > >>>> >>>> >>> >>> >>> >>>> >>>> >>>> >>>> It's not clear to me why this is happening. Should I be using a >>>> different root? does it have to have a transform associated with >>>> it? Everything else makes sense to me, and I've been able to get >>>> resource directories working without issue, etc. >>>> >>>> Also, does every hypercontent site need a sitemap, or can that >>>> be omitted? >>>> >>>> Philip >>>> >>>> Philip Rinehart > > >>>> >>>> >>> >>> >>> >>>> >>>> Academic Media & Technology > > >>>> >>>> >>> >>> >>> >>>> >>>> Cluster Support Services > > >>>> >>>> >>> >>> >>> >>>> >>>> 203-432-6573 > > >>>> >>>> >>> >>> >>> >>>> >>>> clu...@ya... > > >>>> >>>> >>> >>> >>> >>>> >>>> phi...@ya... > > >>>> >>>> >>> >>> >>> >>>> >>>> >>>> >>>> >>>> >> >> Philip Rinehart > > >> >> Academic Media & Technology > > >> >> Cluster Support Services > > >> >> 203-432-6573 > > >> >> clu...@ya... > > >> >> phi...@ya... > > >> >> >> >> > Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 clu...@ya... phi...@ya... |