Currently, if the value of the RDC attributes specifying config or option files doesn't resolve to a valid XML file, a crypic exception is thrown. It would be better if the RDC gave an error message indicating the problem, and specifying the value of the attribute it failed to find. I may take a swing at fixing this one, but wanted to get this into bugilla. org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseInputSource(Unknown Source) at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseInputSourceWithFilter(Unknown Source) at org.apache.taglibs.standard.tag.common.xml.ParseSupport.parseReaderWithFilter(Unknown Source) at org.apache.taglibs.standard.tag.common.xml.ParseSupport.doEndTag(Unknown Source) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._configure._jspx_meth_x_parse_0(_configure.java:216) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._configure._jspx_meth_c_import_0(_configure.java:265) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._configure._jspx_meth_c_otherwise_0(_configure.java:303) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._configure._jspx_meth_c_choose_0(_configure.java:335) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._configure.doTag(_configure.java:99) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._ssn._jspx_meth_rdc_configure_0(_ssn.java:494) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._ssn._jspx_meth_c_when_0(_ssn.java:608) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._ssn._jspx_meth_c_choose_0(_ssn.java:708) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._ssn.doTag(_ssn.java:220) at com.ibm._jsp._member_2D_enter_2D_ssn$_member_2D_enter_2D_ssnHelper.invoke0(_member_2D_enter_2D_ssn.java:207) at com.ibm._jsp._member_2D_enter_2D_ssn$_member_2D_enter_2D_ssnHelper.invoke(_member_2D_enter_2D_ssn.java:226) at com.ibm.ws.jsp.tagfile.taglibs_2D_rdc.rdc._task.doTag(_task.java:77)
I've made a couple of changes based on your feedback -- client-side, a prompt will play indicating the file name that was not found/parsed and the ID of the RDC that was looking for the file, followed by a VoiceXML <exit/> with the error message as the expr attribute; and server-side, a marginally better error message will appear in the logs. Thanks for the feedback.