I've been working with RDCs on the freshly released Voice Toolkit 6 for Rational Application Developer 6.

Focusing on the test jsps provided with the RDC disto, I'm finding mixed results. alpha-test, digit-test, ssn-test work fine. However select1-test.jsp fails immediately with the following error (seen from the Voice Server SystemOut.log):

[6/21/05 11:59:00:078 CDT] 2db4250d VXML E VoiceXML document fatal error::[EMAIL PROTECTED]:
Line  : 1
Column: 1
URI   : null
Msg   : Content is not allowed in prolog.
[6/21/05 11:59:00:078 CDT] 2db4250d VXML E VoiceXML application DOM::[EMAIL PROTECTED]:

[6/21/05 11:59:00:078 CDT] 2db4250d VXML E TRAS0014I: The following exception was logged com.ibm.vxi.intp.BrowserProcException: VXIContext::interpret:
        at com.ibm.vxi.intp.VXIContext.interpret(VXIContext.java:512)
        at com.ibm.vxi.intp.VoiceBrowser.run(VoiceBrowser.java:570)
at com.ibm.voice.server.vc.core.VContainer.dialogRun (VContainer.java:383) at com.ibm.voice.server.vxp.VXPRuntime$RunWorker.runWork (VXPRuntime.java:747)
        at com.ibm.voice.server.vxp.VXPWorker.run(VXPWorker.java:84)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
Caused by: error.badfetch:com.ibm.vxi.intp.CatchEvent: http:// localhost:9080/WebappKickstart_Web/rdc-test/select1-test.jsp:VXML Document error:
Line  : 1
Column: 1
URI   : null
Msg   : Content is not allowed in prolog.
at com.ibm.vxi.intp.VXIContext.parseDocument(VXIContext.java: 1546) at com.ibm.vxi.intp.VXIContext.getDocument(VXIContext.java: 1178) at com.ibm.vxi.intp.VXIContext.fetchDocument(VXIContext.java: 1062)
        at com.ibm.vxi.intp.VXIContext.interpret(VXIContext.java:327)
        ... 5 more
Caused by: com.ibm.vxi.intp.VXMLParserException: VXML Document error:
Line  : 1
Column: 1
URI   : null
Msg   : Content is not allowed in prolog.org.xml.sax.SAXException:
Line  : 1
Column: 1
URI   : null
Msg   : Content is not allowed in prolog.
        at com.ibm.vxi.intp.VXMLParser.parse(VXMLParser.java:258)
        at com.ibm.vxi.intp.VXMLParser.parse(VXMLParser.java:204)
at com.ibm.vxi.intp.VXIContext.parseDocument(VXIContext.java: 1472)
        ... 8 more
.
com.ibm.vxi.intp.BrowserProcException: VXIContext::interpret:
        at com.ibm.vxi.intp.VXIContext.interpret(VXIContext.java:512)
        at com.ibm.vxi.intp.VoiceBrowser.run(VoiceBrowser.java:570)
at com.ibm.voice.server.vc.core.VContainer.dialogRun (VContainer.java:383) at com.ibm.voice.server.vxp.VXPRuntime$RunWorker.runWork (VXPRuntime.java:747)
        at com.ibm.voice.server.vxp.VXPWorker.run(VXPWorker.java:84)
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
Caused by: error.badfetch:com.ibm.vxi.intp.CatchEvent: http:// localhost:9080/WebappKickstart_Web/rdc-test/select1-test.jsp:VXML Document error:
Line  : 1
Column: 1
URI   : null
Msg   : Content is not allowed in prolog.
at com.ibm.vxi.intp.VXIContext.parseDocument(VXIContext.java: 1546) at com.ibm.vxi.intp.VXIContext.getDocument(VXIContext.java: 1178) at com.ibm.vxi.intp.VXIContext.fetchDocument(VXIContext.java: 1062)
        at com.ibm.vxi.intp.VXIContext.interpret(VXIContext.java:327)
        ... 5 more


And so on...

I'd like to find out if others are seeing this problem, and figure out if it's an RDC issue or a IBM Voice Server issue.

I've looked at the voiceXML produced and I can't see the problem. I've also tried taking everything out of the top of the JSP before the <vxml... declaration, added an <?xml... declaration, and done other things I could think of. No matter what I get the same issue.

Any ideas?

Also, there's a bug in the Voice Toolkit 6 that makes the call simulator get stuck sometimes on a certain remote URL. So trying to hit a different URL always ends up sending the one it's stuck on. The only way I've found to get around this is to restart the whole environment. If anyone knows an easier way, please let me know. I've just opened a level 2 PMR on this issue, so hopefully we won't have to live with it for long.

Stu

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to