JEditorPane and HyperlinkListener Problems

Question

Here's my code:
public class WizardHelpScreen extends JFrame implements HyperlinkListener {
private Image theIcon = new ImageIcon(getClass().getResource("icon.gif")).getImage();
private JEditorPane helpPane;
private JScrollPane helpScrollPane;
public WizardHelpScreen() {
     super("Help Documents");
     setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
        setIconImage(theIcon);       
        startHelp();
public void startHelp() {
     helpPane = new JEditorPane();
     helpScrollPane = new JScrollPane(helpPane);
     helpPane.setEditable(false);
            helpPane.addHyperlinkListener(this);
            getContentPane().add(helpPane);
           setLocation(230,230);
           setPreferredSize(new Dimension(640,480));
           pack();
        setVisible(true);
            try {
                  helpPane.setPage("file:///c:/japps/HelpTestTwo.html");
         } catch(IOException ex) {
                   JOptionPane.showMessageDialog(null,"Unable to load helpfile.","Error",JOptionPane.ERROR_MESSAGE);     
                   helpPane.setText("Error. Unable to load help file. Please reinstall the application or contact support.");
public void hyperlinkUpdate(HyperlinkEvent e) {
        if(e.getEventType() == HyperlinkEvent.EventType.ACTIVATED) {
             Document doc = helpPane.getDocument();
                try {
                    URL url = e.getURL();
                    helpPane.setPage(url);                    
                } catch (IOException io) {
                 JOptionPane.showMessageDialog(null, "Can't follow link","Invalid Input",JOptionPane.ERROR_MESSAGE);
                 helpPane.setDocument(doc);
}It opens the html document just fine, and even activates the hyperlink in the first html document. The problem is in the second document that is shown after clicking the link in the first document, the links in the second document don't work anymore. It's like the HyperlinkListener deactivated or something. What am I doing wrong?

Answer 1

Nevermind, there was a typo in my HTML that caused the problem.