Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JDFUtilities mangles JMF translation of XJMF QueryResource response messages #14

Open
tfdonahue1 opened this issue Jul 15, 2022 · 2 comments

Comments

@tfdonahue1
Copy link

QueryResourceSubscribe_001_Response.zip

I am using the JDFUtilities library 1.7.5 library to translate XJMF QueryResource Response messages to JMF 1.7 and the resulting JMF is incorrect.

Attached are a set of simplified examples where the original XJMF contains only two Media resource entries.

Regardless of the number of Resource/Media entries are present in the XJMF response message, the resulting translated JMF data includes only a single and incorrect ResourceInfo/Media entry.

Working examples are provided in the attached zip file:

  1. QueryResourceSubscribe_001_Response_CIP4.xjmf – The XJMF QueryResource Response message to be translated to JMF.
  2. jmf_1.7QueryResourceSubscribe_001_Response_CIP4_EXPECTED.jmf – The expected result of the translation of the XJMF message to JMF.
  3. jmf_1.7QueryResourceSubscribe_001_Response_CIP4_ACTUAL.jmf – Actual translated result out of FixJDF showing the mangled JMF result message.

Please asses this issue and let me know if you have any questions.

THANKS,
-Tim Donahue

@MichelHartmann
Copy link
Member

Hi @tfdonahue1, thank you for reporting this issue. In order to ensure that we keep track of this issue, I also created a reference in the Jira board: https://cip4.atlassian.net/browse/IN-532. Please keep an eye on that ticket for further updates...

@tfdonahue1
Copy link
Author

Hi Michel,

Thank you for the quick response on this and creating the Jira board entry.

I'll be sure to keep an eye on this ticket.

-Tim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants