Skip to main content

Re: Issues in generating the help file using "Webworks ePublisher Pro"

1 reply [Last post]
Anonymous

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Amit S

Hi Jon,

Thanks a lot for your reply. The exception is coming as there are line break
characters ( ) in the index.xml file and while parsing the file
exception was coming.

After I removed these characters manually then no exception is coming and
JavaHelp browser is opening.

Now the question is how to avoid these line breaks which are coming from the
source document itself.

Also I rechecked the "jhm" map file and there are no 'topicalias' defined
and used by me in the file. I checked each and every target till the end of
the file.
So how to insert my topic IDs in the document.

Thanks and regards,
Amit

Jon Sanders wrote:
>
> Hi,
>
> We too will be upgrading to ePublisher Pro. At the moment we successfully
> use an older version of Webworks.
>
> I am not that familiar with ePublisher Pro, but I have done a couple of
> runs
> using it for generating JavaHelp.
>
> It would be worth checking the WWP group on yahoo:
>
> http://tech.groups.yahoo.com/group/wwp-users/
>
> Anyway, hopefully I can give you some pointers of where to look.
>
> Item 1 and Item 4
>
> Looks like the JavaHelp viewer is trying to load the Index XML file but
> cannot find it.
>
> I have found that if I am viewing a help set with the JavaHelp viewer and
> try to regenerate it with webworks publisher, the new help set will have
> file errors.
>
> Make sure the index XML file is there - take a look at the generated .hs
> file and make sure that the generated index XML file (if it exists) has
> the
> correct capitalization and the correct sort of content.
>
> Also there may be some check box somewhere that needs to be checked to
> generate the index XML file.
>
> If there are no particular settings in ePublisher Pro then some editing of
> the underlying XSLT files may be required.
>
> Item 2 and Item 3
>
> The following files only need to be in the folder where the JAR is
> created,
> in order to be able to view the JavaHelp with hsviewer:
>>a. hsviewer.jar
>>b. jh.jar
>>d. runJar.jar
>
> The following files are used to generate the search database and do not
> need
> to be in the the JAR
>>e. search.cfg
>>f. stopwords.cfg
>
> The following file is used to create the appropriate manifest file when
> all
> the JavaHelp files are JAR'ed up. A copy of it will end up in the
> META-INF/MANIFEST.MF file within the JAR file.
>>c. myProject.mft
>
> The following file is the default CSS style sheet, but there may be a new
> CSS file name for ePublisher pro. Open one of the generated HTML topics
> with
> a text editor to see what CSS file is used.
>>g. Document.css
>
>
> Item 5
>
> ePublisher Pro may use a different topic alias marker name in FrameMaker.
> Note that the topic aliases additions to the map file and may well be at
> the
> end of the map XML file.
>
> Hope that gives you some clue as where to look.
>
> Cheers
>
> Jon
>
> On Tue, 1 Jul 2008 02:06:30 -0700, Amit S
> wrote:
>
>>Hi,
>>
>>Earlier we had older version of Webworks and using that we were able to
>>generate the Sun JavaHelp properly.
>>
>>But now we upgraded to Webworks ePublisher Pro version and using this I am
>>getting following problems in generating the JavaHelp (using format Sun
>>Javahelp 1.1.3) -
>>
>>1. The executable jar file created is not loaded from my Java
Application
>>and giving exceptions like –
>>
>>java.lang.NullPointerException
>> at
>>javax.help.plaf.basic.BasicIndexNavigatorUI.reloadData(BasicIndexNavigatorUI.java:205)
>> at
>>javax.help.plaf.basic.BasicIndexNavigatorUI.installUI(BasicIndexNavigatorUI.java:132)
>> at javax.swing.JComponent.setUI(JComponent.java:449)
>> at javax.help.JHelpNavigator.setUI(JHelpNavigator.java:231)
>> at javax.help.JHelpNavigator.updateUI(JHelpNavigator.java:250)
>> at javax.help.JHelpNavigator.(JHelpNavigator.java:97)
>> at javax.help.JHelpIndexNavigator.(JHelpIndexNavigator.java:53)
>> at javax.help.IndexView.createNavigator(IndexView.java:96)
>> at javax.help.JHelp.setupNavigators(JHelp.java:113)
>> at javax.help.JHelp.(JHelp.java:91)
>> at javax.help.JHelp.(JHelp.java:63)
>> at javax.help.DefaultHelpBroker.createJHelp(DefaultHelpBroker.java:733)
>> at
>> javax.help.DefaultHelpBroker.setCurrentID(DefaultHelpBroker.java:446)
>> at javax.help.CSH$DisplayHelpFromFocus.actionPerformed(CSH.java:699)
>> at
>>javax.swing.JComponent$ActionStandin.actionPerformed(JComponent.java:2863)
>> at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1530)
>> at javax.swing.JComponent.processKeyBinding(JComponent.java:2438)
>> at javax.swing.JComponent.processKeyBindings(JComponent.java:2484)
>> at javax.swing.JComponent.processKeyEvent(JComponent.java:2401)
>> at pv.jfcx.JPVTree.processKeyEvent(Unknown Source)
>> at java.awt.Component.processEvent(Component.java:4909)
>> at java.awt.Container.processEvent(Container.java:1569)
>> at java.awt.Component.dispatchEventImpl(Component.java:3615)
>> at java.awt.Container.dispatchEventImpl(Container.java:1627)
>> at java.awt.Component.dispatchEvent(Component.java:3477)
>> at
>>java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1713)
>> at
>>java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:627)
>> at
>>java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:831)
>> at
>>java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:741)
>> at
>>java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:592)
>> at java.awt.Component.dispatchEventImpl(Component.java:3506)
>> at java.awt.Container.dispatchEventImpl(Container.java:1627)
>> at java.awt.Window.dispatchEventImpl(Window.java:1606)
>> at java.awt.Component.dispatchEvent(Component.java:3477)
>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
>> at
>>java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
>> at
>>java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
>> at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
>> at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
>>
>>2. When I compared the older executable Jar file with the newly
generated
>>one, I found that the following files were missing in the newly generated
>>jar
>>
>>a. hsviewer.jar
>>b. jh.jar
>>c. myProject.mft
>>d. runJar.jar
>>e. search.cfg
>>f. stopwords.cfg
>>g. Document.css
>>
>>3. When I created an executable jar file manually by including the
above
>>files into it, then my application started showing the Java Help browser.
>>4. So the first issue is that why the exception was coming and why
there
>>are some files missing from the project and I could not find out a setting
>>in Webworks through which I can include the missing files in the Help jar.
>>5. Also while looking at map file myProject.jhm, I found that it is not
>>containing the topicalias I specified in the Framemaker document. It has
>>auto generated the Target field instead of using my IDs which I created
>>using the Custom Marker “topicalias”.
>>6. So I think I will not be able to show the desired page on the help
>>window using the same ID in the Java Code.
>>
>>Please help me in resolving this issue.
>>
>>I am using - Webworks ePublisher Pro 9.2/Framemaker 7.2/ Sun JavaHelp
>>1.1.3/Windows XP / Java Swing based desktop application.
>>
>>
>>Thanks and regards,
>>Amit
>>
>>--
>>View this message in context:
> http://www.nabble.com/Issues-in-generating-the-help-file-using-%22Webwor...
>>Sent from the Sun - Javahelp-Interest mailing list archive at Nabble.com.
>>
>>********************************************************************************
>>
>>You may leave the list at any time by sending message with no subject and
>>"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
>>are available at
http://archives.java.sun.com/archives/javahelp-interest.html.
>>Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.
>
> ********************************************************************************
>
> You may leave the list at any time by sending message with no subject and
> "SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
> are available at
> http://archives.java.sun.com/archives/javahelp-interest.html.
> Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.
>
>

--
View this message in context: http://www.nabble.com/Issues-in-generating-the-help-file-using-%22Webwor...
Sent from the Sun - Javahelp-Interest mailing list archive at Nabble.com.

********************************************************************************

You may leave the list at any time by sending message with no subject and
"SIGNOFF JAVAHELP-INTEREST" in the body to LISTSERV@JAVA.SUN.COM. Archives
are available at http://archives.java.sun.com/archives/javahelp-interest.html.
Submit bug reports at http://java.sun.com/cgi-bin/bugreport.cgi.