Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] LSResponse's have &gt; and &lt; instead of '>' and '<'

Subject: perfsonar development work

List archive

Re: [pS-dev] LSResponse's have &gt; and &lt; instead of '>' and '<'


Chronological Thread 
  • From: Maciej Glowiak <>
  • To:
  • Cc: "Jeff W. Boote" <>, "" <>
  • Subject: Re: [pS-dev] LSResponse's have &gt; and &lt; instead of '>' and '<'
  • Date: Mon, 11 Sep 2006 09:20:34 +0200
  • Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA CXBIWXMAAEU1AABFNQF8gVf5AAAAB3RJTUUH1QYQDjo6uEWvwgAAAM5JREFUGNNN0LFqAkEUheGj KRZsfATrvENgYyH4APabxwgWGUUQC99BsNDCInUq7VImbbDZ0kayxBXMuN7jvTuKVh//mZlmQKZ1 EhQ8GAVgZECspEBdWQHRjR70KlgFKkoUaCw3ijSYQ4n5HfBK4a4jDcdDQPol/80Sr9BxZOOL4Fmr Jq8VBx7eopaSPvWGOm67fqol3j1q0XNs7Nk2cs6MU6gPNzf+ZGKQX4Ek8H6rAnFZnXB2vJxJcv8g C2P+WzL4tD+Txc4KydrIkh+eAdo01QbjQ84vAAAAAElFTkSuQmCC
  • Organization: Poznan Supercomputing and Networking Center

Hi Jason and Jeff,

Decided for using XML database and XQuery as query language for LS we also decided to have XML as a response, but we hadn't defined it in schema classes. So, there were a couple of solutions:

- send XML response as text (converted < > to XML entities)
or
- modify schema classes to handle it (convert to DOM/text)

I chose the first option because it let us avoid modification of schema classes and I could do it on LS level of application. But of course we may re-think it and implement the second solution.

Maciej

Jason Zurawski wrote:
Jeff;



In any case, the responses from the 'test' scripts have malformed XML. For some reason '>' and '<' are replaced with the escape codes. Has anyone seen this? Is this something I have misconfigured in tomcat?



I had a direct e-mail exchange with Maciej on this back during the release phase:

Jason Zurawski napisa?(a):
Maciej;

I am testing the LS right now, and I am getting a response with some funny markup (attached) do you know what could cause this?

-jason
Yes, it's XML inside XML. The result of XQuery expression may be anything -- in our specific case any XML content.

In some cases this XML content will be NMWG XML but it doesn't have to. So I decided to convert XML into "string" with &lt; &gt; entities. We had quite long discussion about it months ago (I needed some changes in schema classes).

So, in other words, our response is:

=========================================================================
<?xml version="1.0" encoding="UTF-8"?>
<nmwg:message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; id="localhost.-7f6d9204:10baf4475ff:-7ffe" type="LSQueryResponse">
<nmwg:metadata id="LSQueryResponseMetadata_0" />
<nmwg:data id="LSQueryResponseData_0" metadataIdRef="LSQueryResponseMetadata_0">
<psservice:datum xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/";>

-------------------------------------------------------------------------
then the XQuery result comes
-------------------------------------------------------------------------

</psservice:datum>
</nmwg:data>
</nmwg:message>
=========================================================================


-jason




--

--------------------------------------------------------------------
| Maciej Glowiak Network Research and Development ||
|

Poznan Supercomputing and Networking Center ||
| (+48 61) 858 2024 http://monstera.man.poznan.pl/ ||
====================================================================



Archive powered by MHonArc 2.6.16.

Top of Page