REST API does not un-marshal XMLliterals

[amedranogil]

When REST API receives an event (for example) if the turtle serialization includes an XMLLiteral it will not unmarshall it.

Reproduce:

have CHe and RESTAPI installed,
send a CTXe with subject as XMLLliteral
querry CHe for context event,
You'll see the serialization of subject as subject, and not the URI.

Work arround:

have clients not send literals:

			//unliterilize everything
			event.unliteral();
			Iterator it = GraphIterator.getResourceIterator(event);
			while (it.hasNext()) {
				Resource r = (Resource) it.next();
				r.unliteral();
                        }

[Alfiva]

Do you mean when the event is sent from a REST client to the REST API? Or from uAAL instance towards the REST clients through their callbacks in REST Manager? (in other words: in which direction?)
Does this happen only when XMLliteral is the subject, or anywhere in the event?
Do you have any particular event you are using for testing?
Do you suggest that not sending literals is the way to go, or should we find a fix to allow them?
Will this happen as well with service calls that include XMLliterals?

[amedranogil]

Do you mean when the event is sent from a REST client to the REST API? Or from uAAL instance towards the REST clients through their callbacks in REST Manager? (in other words: in which direction?)

tested when client sends context event to REST API .

Does this happen only when XMLliteral is the subject, or anywhere in the event?

It happens with any member; I only noticed for subject and object; but I guess this happens with anything. The problem might not be so much on REST-API as CHe registering the litereals as ... literals (i.e. you can not querry anything within the object)

Do you have any particular event you are using for testing?

yes.
but due to privacy concerns I would have to clean up somewhat.

Do you suggest that not sending literals is the way to go, or should we find a fix to allow them?

the fact that the serialization included a literal might be an accident on my part, but this rises a good question about how to manage the literals and who should manage them. As said, the REST API seemed not to mind literal properties in an event, but the real problem rose when querrying the CHe for those events.

Will this happen as well with service calls that include XMLliterals?

I think the Service Strategy is smart enough to deal with liteals, but I do not know if this will happen in every situation.