Two things -- first, how recent are the bits you're using? I've been making
*lots* of changes through yesterday (a fun way to spend the commercials
while Oregon was whomping on Stanford :-), and the legacy implementation now
works for me. I've also checked in a test app (shale-test-dialog2-legacy)
into the sandbox. This webapp can be used manually to experiment (it even
has a split-screen mode so you can play with two active dialogs in two
different frames), plus it's got a basic system integration test (mvn
-Pitest clean install) to run a couple of simple scenarios automatically.
Next I'll see about doing something similar for the SCXML implementation.
Yeah I realized you had made changes but only after I tried to check
in and the file was no longer in SVN! No big deal, it was a minor
change and I just copied and pasted it into the new location. BTW,
I'm glad we renamed the Contexts interface - that was too confusing
having both Context and Contexts.
The second thing is that, at the moment, you have to explicitly declare your
dialog configuration files in web.xml:
<context-param>
<param-name>org.apache.shale.dialog2.legacy.CONFIGURATION</param-name>
<param-value>/WEB-INF/dialog-config.xml</param-value>
</context-param>
On my list of corrections is making it recognize this default location
automatically ... should be an easy fix.
Yes this was the problem. The param name was still configured for the
current dialog implementation.
Craig
Sean
