I'm using the Dialog Designer builtin date grammar to collect a date from the caller. After, I have the application confirm the date with the caller. Why, when the grammar returns an interpretation as [for example] '19500403' for the date, does the phrase read the date as 'nineteen million five hundred thousand four hundred three'. I've specified the 'Say-As' SSML tag, and set 'interpret-as' to "date", but still no success. When I export the project, I click the checkbox to enable SSML markup. The only way the date is read back correctly, is if I reformat the date to '04-03-1950', then the system say's "April third nineteen fifty" as it should. Why do I have to reformat the date to get it to be read correctly?

mdailous@infinitycti.com

I just sent you an email, too. :)

Thank you so much!!!
Michael

Also, if you have a CustomerManagerResult java object, could you include the source for that as well? I *could* just copy/paste the code and create the object manually... that *might* work as well.

Thank you again,
Michael

Thank you Dennis. I followed your recommendations, but when selecting the "Create Automatically" object, I still get a NullPointerException and the WSOP isn't created. I tried to create the simple variable manually and select it in the wizard, then check the "Use Java Object" option, and this worked fine... but when I override the requestBegin method, eclipse complains that it cannot resolve the CustomerManagerResult object. Is it possible for you to include a copy of your WSOP source for the VerifySSN object, as well as your IProjectVariables java file?

Also, I notice DD 4.1 is available for download, and I'm in the process of DL'ing it now, but do you know if it's 4.1.8 or an earlier version?

Thank you again.
Michael

I'm having issues trying to get the return value of a WSDL call assigned to a variable (any variable) in DD. Here's a complete synopsis of everything I've done so far:

1) I tried to assign the return value to the DD simple variable 'wsdlReturn'. When I test the application, an exception is thrown that states: "Cannot access simple variable as complex variable".

2) I created a complex variable in DD named "WSDL", with 3 fields (returnValue, returnType, returnReason - returnValue should contain the return, the other 2 fields are used elsewhere in the app depending on the return value). In the WSOP wizard, I can select the WSDL variable, and the returnValue field, but when I look at the WSDL in the WSOP Editor, there is no selection in the Variable Field drop down, AND the drop down is greyed out so I can't select anything. When I test the application, it runs fine, but I never get the return value.

3) I tried creating the WSOP using the wizard, and specifying to "Auto Create" the variable. This results in an eclipse dialog that states "NullPointerException". No other details are provided. The WSOP is *not* created, and I haven't been able to figure out how to get around this.

Following is the WSDL descriptor. The method I'm calling is the VerifySSN method.

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.consumerinfo.com" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://www.consumerinfo.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:types>
      <s:schema elementFormDefault="qualified" targetNamespace="http://www.consumerinfo.com">
         <s:element name="VerifySSN">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="SSN" type="s:string"/>
                  <s:element minOccurs="0" maxOccurs="1" name="VDN" type="s:string"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="VerifySSNResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="1" maxOccurs="1" name="VerifySSNResult" type="tns:CustomerManagerResult"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:simpleType name="CustomerManagerResult">
            <s:restriction base="s:string">
               <s:enumeration value="VRU_NotProcessed"/>
               <s:enumeration value="VRU_SSN_Invalid"/>
               <s:enumeration value="VRU_SSN_Not_Found"/>
               <s:enumeration value="VRU_SSN_Valid_Multiple_Accounts"/>
               <s:enumeration value="VRU_SSN_Valid_Account_Locked"/>
               <s:enumeration value="VRU_DOB_Invalid"/>
               <s:enumeration value="VRU_DOB_Not_Matched"/>
               <s:enumeration value="VRU_ZIP_Invalid"/>
               <s:enumeration value="VRU_ZIP_Not_Matched"/>
               <s:enumeration value="VRU_SSN_Valid"/>
               <s:enumeration value="VRU_DOB_Valid"/>
               <s:enumeration value="VRU_ZIP_Valid"/>
               <s:enumeration value="VRU_Password_Reset_Complete"/>
               <s:enumeration value="VRU_Exception_Occured"/>
            </s:restriction>
         </s:simpleType>
         <s:element name="VerifyDOB">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="1" maxOccurs="1" name="DOB" type="s:dateTime"/>
                  <s:element minOccurs="0" maxOccurs="1" name="SSN" type="s:string"/>
                  <s:element minOccurs="0" maxOccurs="1" name="VDN" type="s:string"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="VerifyDOBResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="1" maxOccurs="1" name="VerifyDOBResult" type="tns:CustomerManagerResult"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="VerifyZIP">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="ZIP" type="s:string"/>
                  <s:element minOccurs="1" maxOccurs="1" name="DOB" type="s:dateTime"/>
                  <s:element minOccurs="0" maxOccurs="1" name="SSN" type="s:string"/>
                  <s:element minOccurs="0" maxOccurs="1" name="VDN" type="s:string"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="VerifyZIPResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="1" maxOccurs="1" name="VerifyZIPResult" type="tns:CustomerManagerResult"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="ResetPassword">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="ZIP" type="s:string"/>
                  <s:element minOccurs="1" maxOccurs="1" name="DOB" type="s:dateTime"/>
                  <s:element minOccurs="0" maxOccurs="1" name="SSN" type="s:string"/>
                  <s:element minOccurs="0" maxOccurs="1" name="VDN" type="s:string"/>
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="ResetPasswordResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="1" maxOccurs="1" name="ResetPasswordResult" type="tns:CustomerManagerResult"/>
               </s:sequence>
            </s:complexType>
         </s:element>
      </s:schema>
   </wsdl:types>
   <wsdl:message name="VerifySSNSoapIn">
      <wsdl:part name="parameters" element="tns:VerifySSN"/>
   </wsdl:message>
   <wsdl:message name="VerifySSNSoapOut">
      <wsdl:part name="parameters" element="tns:VerifySSNResponse"/>
   </wsdl:message>
   <wsdl:message name="VerifyDOBSoapIn">
      <wsdl:part name="parameters" element="tns:VerifyDOB"/>
   </wsdl:message>
   <wsdl:message name="VerifyDOBSoapOut">
      <wsdl:part name="parameters" element="tns:VerifyDOBResponse"/>
   </wsdl:message>
   <wsdl:message name="VerifyZIPSoapIn">
      <wsdl:part name="parameters" element="tns:VerifyZIP"/>
   </wsdl:message>
   <wsdl:message name="VerifyZIPSoapOut">
      <wsdl:part name="parameters" element="tns:VerifyZIPResponse"/>
   </wsdl:message>
   <wsdl:message name="ResetPasswordSoapIn">
      <wsdl:part name="parameters" element="tns:ResetPassword"/>
   </wsdl:message>
   <wsdl:message name="ResetPasswordSoapOut">
      <wsdl:part name="parameters" element="tns:ResetPasswordResponse"/>
   </wsdl:message>
   <wsdl:portType name="CustomerManagerSoap">
      <wsdl:operation name="VerifySSN">
         <wsdl:input message="tns:VerifySSNSoapIn"/>
         <wsdl:output message="tns:VerifySSNSoapOut"/>
      </wsdl:operation>
      <wsdl:operation name="VerifyDOB">
         <wsdl:input message="tns:VerifyDOBSoapIn"/>
         <wsdl:output message="tns:VerifyDOBSoapOut"/>
      </wsdl:operation>
      <wsdl:operation name="VerifyZIP">
         <wsdl:input message="tns:VerifyZIPSoapIn"/>
         <wsdl:output message="tns:VerifyZIPSoapOut"/>
      </wsdl:operation>
      <wsdl:operation name="ResetPassword">
         <wsdl:input message="tns:ResetPasswordSoapIn"/>
         <wsdl:output message="tns:ResetPasswordSoapOut"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="CustomerManagerSoap" type="tns:CustomerManagerSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
      <wsdl:operation name="VerifySSN">
         <soap:operation soapAction="http://www.consumerinfo.com/VerifySSN" style="document"/>
         <wsdl:input>
            <soap:body use="literal"/>
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal"/>
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="VerifyDOB">
         <soap:operation soapAction="http://www.consumerinfo.com/VerifyDOB" style="document"/>
         <wsdl:input>
            <soap:body use="literal"/>
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal"/>
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="VerifyZIP">
         <soap:operation soapAction="http://www.consumerinfo.com/VerifyZIP" style="document"/>
         <wsdl:input>
            <soap:body use="literal"/>
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal"/>
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="ResetPassword">
         <soap:operation soapAction="http://www.consumerinfo.com/ResetPassword" style="document"/>
         <wsdl:input>
            <soap:body use="literal"/>
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="CustomerManager">
      <documentation xmlns="http://schemas.xmlsoap.org/wsdl/"/>
      <wsdl:port name="CustomerManagerSoap" binding="tns:CustomerManagerSoap">
         <soap:address location="http://localhost/ECD.WebService.VRU.ProxyB/CustomerManager.asmx"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Any help or advise would be greatly appreciated.
TIA - Michael

Thank you, that's exactly what I was looking for.

I was missing the "getServletContext()" in my long running line of code (see original request). I like the mySession.getParameter(...) option better, though.. it's shorter and cleaner.

Thanks again. :)
Michael

Thank Samaresh,

I'm already working in the corresponding Java file. Your response doesn't tell me how to access the context-param values in the web.xml.

So, how do I access the context-param values in the web.xml.

Thanks,
Michael

How can I access the web.xml context-param values from within my com.avaya.sce.runtime.connectivity.ws2.CallService class?

We need to perform some customizations to a set of Axis 2 WS operations. I have tried the following, and all that seems to happen is the HTTP session gets invalidated:

((com.avaya.sce.runtimecommon.SCESession)mySession).getServlet().getInitParameter("my_context_param_name");

Thank you,
Michael

I have a servlet that is suppose to turn tracing on/off, depending on the value of the passed in variable "debug". My servlet implementation method is as follows:

	public void servletImplementation(com.avaya.sce.runtimecommon.SCESession mySession) {

		try {

			boolean debug = mySession.getVariableField(IProjectVariables.DEBUG).getBooleanValue();

			mySession.getTraceOutput().writeln(ITraceInfo.TRACE_LEVEL_INFO, String.format("Using variable [%s] value [%b] to enable/disable tracing", new VariableName(IProjectVariables.DEBUG), debug));

			mySession.setTraceOn(debug);

			mySession.getTraceOutput().writeln(ITraceInfo.TRACE_LEVEL_INFO, String.format("Tracing is now enabled [%b]", mySession.isAppTraceEnabled()));

		} catch (Exception ignore) { 

			mySession.getTraceOutput().writeln(ITraceInfo.TRACE_LEVEL_INFO, String.format("Error: [%s]", ignore.getMessage()));

			ignore.printStackTrace();

		}



	}

When I look at the trace.log file, I see the following entries:

20/02/2014 16:17:57:932  INFO - 002641C28FA43081ED25E16F13BEB887:/CallCampaignDNC : Using variable [debug] value [false] to enable/disable tracing

20/02/2014 16:17:57:932  INFO - 002641C28FA43081ED25E16F13BEB887:/CallCampaignDNC : Tracing is now enabled [true]

As you can see, the value of variable debug is "false", but the call to the setTraceOn(...) method doesn't seem to be turning off tracing. Is there a misunderstanding on my part?

Thanks for the help,
Michael

We have a CCXML application that is executed using the LaunchVXML web service method. In the EP, this application is configured as a CCXML/VXML application. The VXML application utilizes VP Configurable Variables for part of the configuration of the application.

How can the CCXML application set or change the VP Configurable variables that are used by the VXML application?

Michael

Worked beautifully. Thanks Neil.

Sorry for the confusion. We are using the Axis2 web services, I should have said after we delete the original .wsop file, which deletes the corresponding .java source file, we then create a new Web Service Operation with the same name as the original.

It's during the new web service operation wizard that the original .wsdl and .java files that were previously created in the package are deleted. Unfortunately, this process also deletes all the .wsdl and .java files in any subdirectories.

Just to clarify... I would issue a launchvxml request *from* my ccxml application? Or are you saying I should use the launchvxml request *instead of* the launchccxml request, and the ccxml associated with the application would be launched first, which would provide the "avaya.launchvxml" transition?

Michael

We use several web services in an application. Some use the java output package as "connectivity.ws.beans.aep", and others use the java output package "connectivity.ws.beans". When we regenerate the WSDL in connectivity.ws.beans, the WSDL information for connectivity.ws.beans.aep is also deleted. Why is the Avaya process deleting all files in subdirectories as well? The directory connectivity/ws/beans/aep is never removed, only the files within it.

Michael

Orchestration Designer 6.0.13.01

I just emailed both the CCXMl and the VXML CXI logs to you. :) Thank you Neil.