Thanks for the detailed response Rahul. Congrats on the beta release.
Ahh, I figured out what happened with the ExpandTag. I didn't have the commons EL jar in the classpath, and I ran "organize imports" in RAD to get rid of warnings from unused imports. It resolved it to the Sun version, which is there from the WAS libs. My fault, but it might make it easier if the distribution lists non-included required dependency jars. The two that I bumped into were this and the xml/xslt jars.
Thanks for the instructions on pointing the voice browser to a URL. I've spent a good bit of time in the online help, and couldn't find that. I'll give that a try tomorrow. As for an open source way of running VUIs, that'd be a really useful thing to make a post on. Particularly since the RDC is slick and free, and itself runs in Tomcat, a browser is the missing link for an open source dev environment. I wonder if the Voice Tools project in Eclipse will eventually include one. Right now it looks to be mostly about source file editors.
Anyway, thanks again for the responses. I think I have enough now to get things running.
Stu
On Apr 24, 2005, at 9:29 PM, Rahul P Akolkar wrote:
Stu -- Please find my replies below, enclosed in <reply> tags. Happy to answer more - Rahul
On 4/22/05, Stuart D. Robertson II <[EMAIL PROTECTED]> wrote:Thanks Rahul. Another issue with RDC and WAS 6 test environment is the com.sun.faces.el.impl.ExpressionEvaluatorImpl class. It's included in the WebSphere runtime (in ws-jsf.jar), so it's there, but several of the tags reference a no-arg constructor and an evaluate method signature not present in WAS 6. ExpandTag.java is an example.
<reply>
Thats not what <rdc:expand> is looking for, it looks for the commons el
impl (there should be no need for a JSP 2.0 taglib to have a JSF related
dependency). The issue probably is WAS doesn't have implicit access to the
classes in commons-el.jar, which, OTOH, is available in the commons/lib on
Tomcat. You can get commons el here (maybe I should pack it in the
examples war in the future):
http://jakarta.apache.org/commons/el/
</reply>
I have the mortgage app working under Tomcat, so your suggestion worked for me. I did have to download and add the xalan jars to the rdc-examples/WEB-INF/lib dir though, since the tomcat version I got (5.0.30b) didn't come with xalan, and some of the tags are using xslt.
<reply>
xalan is one of those things ;-) It probably has to do with more than just
your TC version. I have the IBM JVM and that also plays into it.
</reply>
Two more questions :=). First, what are some ways I can test out the VUI? I know how to launch a .vxml file using the call simulator in RAD 6 Voice Toolkit, but I don't see any way to have it hit a url in a webapp. Are there other voice browsers you'd recommend for development?
<reply>
Availability of voice browsers, or the lack thereof, is clearly something
that affects most of us. I'd say that the RAD 6.0 Voice Toolkit you have
is the best option. I'll ask around, and let you know if I find any
alternatives (barring commercially available ones).
Loading the response from a URI using the Voice Toolkit on RAD is
possible. I have an older version of the voice toolkit, but I don't think
the menu has changed all that much; here is what I do:
0) I prefer the "voice" perspective for grammar tools, authoring etc. and
the "debug" perspective for running/debugging
1) Choose the "Run" (main) menu
2) Choose the "Run..." or "Debug..." option
3) In the Run/Debug dialog:
3a) Expand "VoiceXML Application" in the "Configurations" tree on the left
3b) Choose New_configuration
3c) Choose the "Remote VoiceXML URL" radio button in the "Main" tab
3d) Enter the complete URI (for the RDC based application)
3e) Hit "Run"/"Debug"
</reply>
Second, I saw that RDC moved into beta recently. Would you consider the APIs to be stable/frozen and the impl production-ready, or is this still too early?
<reply>
I expect any changes to the APIs in the future to be completely
transparent to the users of the RDC taglib, which is one of the reasons
the recent release was declared as the first RDC taglib beta. I can pretty
much guarantee that as taglib users, there will no "backward
compatibility" issues with the future releases.
About production readiness, I want to say two things:
1) We are continually identifying performance optimizations and I think
most have been identified, if not implemented (which is why we're still
beta ;-) We also are beginning to perform load tests on the RDC framework,
but I have no numbers yet.
And, maybe more importantly:
2) Being a JSP 2.0 taglib, speech / multi-channel applications developed
using the RDC framework can be deployed just like a web / gui application,
which has more than a few advantages. The one most relevant to this
discussion is that we can benefit from the tremendous existing expertise
from this (i.e. taglibs) and other communities, such as tomcat, websphere
forums etc. when its comes to load testing, clustering, performance
issues, optimizations, profiling and so on. I believe this is a large
value-add for RDC-based authoring.
</reply>
Thanks again for your help,
Stu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
