Skip to content

Fix invalid XML message with nested CDATA section causes in ut_realtime_reporter #1074

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.

Sign up for GitHub

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

Closed
wants to merge 3 commits into from
Closed

Fix invalid XML message with nested CDATA section causes in ut_realtime_reporter #1074

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0dd978f
grant privileges to debug via UT3_USER
PhilippSalvisberg Jun 4, 2020
9ea6ab4
add test case to reproduce bug #1073
PhilippSalvisberg Jun 4, 2020
bfe94cd
handle nested CDATA sections to fix bug #1073
PhilippSalvisberg Jun 4, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
handle nested CDATA sections to fix bug #1073
  • Loading branch information
@PhilippSalvisberg
PhilippSalvisberg committed Jun 4, 2020
commit bfe94cd6abe68ee50d54f51e2ee624f1ba1c939c
2 changes: 1 addition & 1 deletion source/reporters/ut_realtime_reporter.tpb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ create or replace type body ut_realtime_reporter is
) is
begin
if a_content is not null then
self.print_xml_fragment('<' || a_name || '><![CDATA[' || a_content || ']]></' || a_name || '>');
self.print_xml_fragment('<' || a_name || '><![CDATA[' || ut_utils.to_cdata(a_content) || ']]></' || a_name || '>');
end if;
end print_cdata_node;

Expand Down
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy