Custom element error logs http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=8529571 2013-06-19T21:38:32Z 2013-06-19T21:38:32Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8533461 2012-11-13T19:39:18Z 2012-11-13T19:37:08Z

Yeah, I looked into it more, and what happended was just a stupid mistake on my part. I was unfamiliar with how java compiled classes. I had my ant build file set to auto copy the class file into call studio, and when I started adding subclasses to the main class, I did not realize that the subclasses would be in seperate files. I figured that since they were part of the main class, they would be in the same class file. Oops.

Asher Schweigart 2012-11-13T19:37:08Z Hemal Mehta http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8534368 2012-11-13T19:31:48Z 2012-11-13T19:31:48Z

I have seen cases where it does not show with class and works with jar. Good it worked for you. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, November 13, 2012 1:17 PM To: cdicuser@developer.cisco.com Subject: New Message from Asher Schweigart in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Custom element error logs Asher Schweigart has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Thank you both, both ways showed the info I needed. Error was caused because it could not find my custom classes, which I wrote as subclasses of the element class. I was using the compiled class file, i switched to using a jar, and that fixed it. Seems I need to work on my ant build file to get this working right! -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/8533271 or simply reply to this email.

Hemal Mehta 2012-11-13T19:31:48Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8533271 2012-11-13T19:17:05Z 2012-11-13T19:17:05Z

Thank you both, both ways showed the info I needed. Error was caused because it could not find my custom classes, which I wrote as subclasses of the element class. I was using the compiled class file, i switched to using a jar, and that fixed it. Seems I need to work on my ant build file to get this working right!

Asher Schweigart 2012-11-13T19:17:05Z Janine Graves http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8532743 2012-11-13T18:38:08Z 2012-11-13T18:38:08Z

Asher, If the element doesn't show up in studio, you should be able to go to Window > Show View > Call Studio Error Log.  

Janine Graves 2012-11-13T18:38:08Z Hemal Mehta http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8530772 2012-11-13T17:47:48Z 2012-11-13T17:47:48Z

Are you adding this as a class file or bundling it a jar and then adding it ? Do one thing, call this code from action element within studio and see what if it give you an error. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, November 13, 2012 11:33 AM To: cdicuser@developer.cisco.com Subject: New Message from Asher Schweigart in Customer Voice Portal (CVP) - General Discussion - All Versions: Custom element error logs Asher Schweigart has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- I have a custom element that I can't get to load in call studio. I have found the issue in the element, it is a single line fo code that it must not like, because when I comment it out the element loads fine. Is there a place I can look to see what error is causing the element not to load? I checked workspace/.metadata/.log, but I'm not seeing anything in there, and I don't know where else to look. Here is the offending code in case anyone can help on that end: URL url = new URL(<http://someXmlFile.xml); URLConnection conn = url.openConnection(); conn.setRequestProperty("Authorization", "Basic "+cred); conn.connect(); InputStream sn = conn.getInputStream(); SaxTicketReader ticketReader = new SaxTicketReader(); SAXParserFactory factory = SAXParserFactory.newInstance(); try { SAXParser parser = factory.newSAXParser(); parser.parse(new InputSource(sn), ticketReader); <------- this is the line that is causing the issue. } catch.... This code works fine when I test it outside of call studio. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/8529570 or simply reply to this email.

Hemal Mehta 2012-11-13T17:47:48Z Asher Schweigart http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=8529570 2012-11-13T17:33:17Z 2012-11-13T17:00:50Z

[color=#525252]I have a custom element that I can't get to load in call studio. I have found the issue in the element, it is a single line fo code that it must not like, because when I comment it out the element loads fine. [/color] [color=#525252]Is there a place I can look to see what error is causing the element not to load? I checked workspace/.metadata/.log, but I'm not seeing anything in there, and I don't know where else to look.[/color] [color=#525252] [/color] [color=#525252]Here is the offending code in case anyone can help on that end:[/color] [color=#525252]    URL url = new URL(<http://someXmlFile.xml);[/color] [color=#525252] [/color] [color=#525252]    URLConnection conn = url.openConnection();[/color] [color=#525252]    conn.setRequestProperty("Authorization", "Basic "+cred);[/color] [color=#525252]    conn.connect();[/color] [color=#525252]    InputStream sn = conn.getInputStream();[/color] [color=#525252] [/color] [color=#525252]    SaxTicketReader ticketReader = new SaxTicketReader();[/color] [color=#525252]    SAXParserFactory factory = SAXParserFactory.newInstance();[/color] [color=#525252]    try {[/color] [color=#525252]        SAXParser parser = factory.newSAXParser();[/color] [color=#525252]        parser.parse(new InputSource(sn), ticketReader);  <------- this is the line that is causing the issue.[/color] [color=#525252]    } catch....[/color] [color=#525252] [/color] [color=#525252] [/color] [color=#525252]This code works fine when I test it outside of call studio.[/color]

Asher Schweigart 2012-11-13T17:00:50Z