I do have the dialog.xml file under WEB-INF but it's empty right now as
shown below.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dialogs PUBLIC
"-//Apache Software Foundation//DTD Shale Dialog Configuration
1.0//EN"
"http://shale.apache.org/dtds/dialog-config_1_0.dtd";>
<dialogs>
</dialogs>
Also, I have this configuration in my web.xml:
<context-param>
<param-name>org.apache.shale.dialog.CONFIGURATION</param-name>
<param-value>/WEB-INF/dialog-config.xml</param-value>
</context-param>
The error stems from a connection time out. Could this be related to a
firewall issue?
Good luck at the Conference!
-----Original Message-----
From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 10:39 AM
To: user@shale.apache.org
Subject: Re: Startup Error
On 1/17/07, Reynolds, James <[EMAIL PROTECTED]> wrote:
> My app isn't starting and I think it's due to the dialog
configuration.
> I don't have any dialogs set up, but the error messages seem to relate
> to this feature. I've googled the error without success. Any
> suggestions on this one? I'm using Shale 1.0.4, Tomcat 5.5.17 & I'm
> trying to use Facelets as the view handler.
>
<snip/>
In all likelihood (about to demo at an unconference so can't dig into
the trace right now), it means one of the dialog configuration files
listed is not found (the default is WEB-INF/dialog-config.xml). Can
you please check that? Details for the Commons SCXML dialog impl are
here [1].
A fatal error is probably appropriate in the above scenario as the
application will be missing a bunch of functionality at that point. We
could definitely improve the stack trace to include the name of the
missing configuration file. If you want to file a JIRA ticket [2] for
that improvement, that'll ensure it stays on the radar. Thanks!
-Rahul
[1] http://shale.apache.org/shale-dialog-scxml/index.html
[2] http://issues.apache.org/struts/browse/SHALE
E-Mail messages may contain viruses, worms, or other malicious code. By reading
the message and opening any attachments, the recipient accepts full
responsibility for taking protective action against such code. Sender is not
liable for any loss or damage arising from this message.
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee(s). Access to this e-mail by anyone
else is unauthorized.
