Re: [Hypercontent-users] Problem with setting up dtd definition
Brought to you by:
alexvigdor
From: Alex V. <av...@co...> - 2005-05-13 01:52:18
|
Philip, Based on the error, it looks like the system was trying to = resolve the =20 dtd location as a relative path - by default, it will try and resolve =20= relative paths to the working directory, which is wherever you started =20= the JVM - in other words, the uPortal directory. This means that the =20 file you're editing still is missing the leading slash in its doctype - =20= changing the doctype in the project definition does not change the =20 doctype of existing files, it only affects files created after the =20 change. You can either delete the file and recreate it, or download it = and =20 manually change the doctype to also add the leading slash (you would =20 need to enable the upload editor to upload your change). If you have a =20= number of files that need the change, you can use the download zip =20 function to download all the files to your local disk, where you can =20 use your favorite editor to do a global search and replace. Zip the =20 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 = =20 > is that the dtd reference is trying to refer to the root of the =20 > uPortal instance, *not* the dtd contained within the repository. =20 > Here's the snippet from the error log: > > org.jasig.portal.PortalException: PortalException has no ErrorID > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.editors.EditorServant.setStaticData(EditorSer=20= > vant.java:90) > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.contentmanager.commands.ChangeEditor.execute(=20= > ChangeEditor.java:58) > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.contentmanager.CContentManager.setRuntimeData=20= > (CContentManager.java:192) > =A0 =A0 =A0 =A0 at =20 > = org.jasig.portal.MultithreadedChannelAdapter.setRuntimeData(Multithread=20= > edChannelAdapter.java:61) > =A0 =A0 =A0 =A0 at =20 > org.jasig.portal.ChannelRenderer$Worker.run(ChannelRenderer.java:417) > =A0 =A0 =A0 =A0 at = org.jasig.portal.utils.threading.Worker.run(Worker.java:88) > Caused by: edu.columbia.hypercontent.CMSException: There was an error =20= > while processing this directive; =20 > /home/local/tomcat5_instances/dev/susan/dtd/docbook.dtd (No such file =20= > or directory) > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.DocumentFactory.getDocumentFromStream(Documen=20= > tFactory.java:434) > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.editors.xml.XmlEditor.startSession(XmlEditor.=20= > java:66) > =A0 =A0 =A0 =A0 at =20 > = edu.columbia.hypercontent.editors.EditorServant.setStaticData(EditorSer=20= > vant.java:86) > =A0 =A0 =A0 =A0 ... 5 more > > > This directory:=A0/home/local/tomcat5_instances/dev/susan is the root = of =20 > 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, >> =A0 My first suggestion is to add the leading "/" on the dtd = location: =20 >> "/dtd/docbook.dtd". You can check the portal log for stack traces, =20= >> which are handy. What version of uPortal are you running? A doctype =20= >> does not need to have any forms of output associated with it, and if =20= >> there is an error parsing the DTD or XML it should display the =20 >> parsing error. The root can be any element in your DTD. >> >> The sitemap is optional - it's just a specific XML document type that = =20 >> the system applies special processing to before it's included, which =20= >> you can use to set up templates for the site map or navigation =20 >> structures. You can have none of them, one of them, or as many as you = =20 >> want. You can use your own custom includes & xslt to set up =20 >> navigation structures, in fact that was the only way prior to version = =20 >> 1.4. The navigation document type was specifically designed to make =20= >> it easy to do manual sorting of navigation elements in the drag & =20 >> drop navigation editor, as well as move the logic of sorting and =20 >> labeling navigation elements out of XSL. We actually use this =20 >> document type to manage pushed bookmarks channels at Columbia - it is = =20 >> displayed as a nested list of bookmarks, which can be added, updated =20= >> and re-ordered using the same navigation editor by non-technical =20 >> 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 =20 >>> section of my test website. I've specified the dtd I want to use, =20= >>> which is in the repository, as well as the editor key. Here's what =20= >>> the line looks like: >>> >>> =A0 <xml-doctype definition=3D"dtd/docbook.dtd" label=3D"First = Section" =20 >>> path=3D"/*/index.xml" root=3D"body"> >>> =A0 <editor key=3D"xml"/> >>> =A0 </xml-doctype> >>> >>> However, when I attempt to do anything to the index.xml file I end =20= >>> up with the following error: >>> >>> Error performing changeEditor: PortalException has no ErrorID =20 >>> (org.jasig.portal.PortalException) >> >> >>> >>> >>> >>> It's not clear to me why this is happening. Should I be using a =20 >>> different root? does it have to have a transform associated with it? = =20 >>> Everything else makes sense to me, and I've been able to get =20 >>> resource directories working without issue, etc. >>> >>> Also, does every hypercontent site need a sitemap, or can that be =20= >>> 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... > > > |