cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
54
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 19-09-2003 04:25:02 AM
I have two elements that basically are identical. They are URI decision elements that simply pull session variables (already set prior to both these elements and I know exist) and set an exit state to Yes or No.

The quirky thing is that the second one always fails although if pulled directly in a browser loads fine. Feeling desperate, I decided to switch the places of these elements so that the second one is called first. It worked.

Any ideas on why this could be happening?

Thanks,
Tracey

Subject: RE: element issues
Replied by: null on 22-09-2003 09:53:21 PM
Hi Tracey,

Without knowing more about what the elements do and what the application looks like, I can't off the top of my head say why you are seeing that behavior.

The things that could be causing it are if the decision element overwrites or deletes one of the session variables so that the other one encounters an error when trying to access them.

Subject: Element errors
Replied by: null on 22-09-2003 09:59:13 PM
I think I have found one issue. It appears that if I clear a session variable, ie. <session variable="data1"></session> in the first element, it creates a problem with the second. Is the Audium server accepting this as a valid session variable but when it tries to pass back to the next element, it creates an error?

Is this not an acceptable code?(<session variable="data1"></session>)

Let me know.

Thanks,
Tracey

Subject: RE: Element errors
Replied by: null on 23-09-2003 01:06:50 AM
Hi Tracey,

After performing some testing, it seems that an error will be thrown if you try to reset session data that already exists when using the XML API. Normally, the XML code you entered would be acceptable, but this bug prevents any value from being entered, even a legitimate value.

This is defenitely a bug in the Audium system and I've logged it in our bug tracking system.

Unfortunately, the only way I see to avoid this is to never reset session variables and use new ones.

Another option is I could write a simple action element that would allow you to reset session data. This would use the Java API, which does not seem to have this bug.

I appologize for any inconvenience this may have caused you.

Subject: Element issues
Replied by: null on 23-09-2003 05:36:15 PM
Thanks for looking into it. I will let you know if I need your element. For now, when I need to initialize, I have been setting these variables to zero.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links