Re: [Exist-open] Problems: lang(), Xinclude, SOAP security

[Wolfgang M. <me...@if...>]

I reworked the SOAP interface to support user authentication, cleaned up the 
available methods and added additional parameters to handle the expansion of 
xinclude elements. You now have to create a session before calling any of the 
other methods. Method 

String connect(String username, String password);

returns a valid session id if the specified user exists in the database. The 
session id will remain valid for at least 60 minutes. All other methods 
expect a valid session id as first parameter. An exception is thrown if the 
passed session id is not registered or timed out. You can release a session 
by calling

void disconnect(String sessionId);

Further changes:

the getResource() and retrieve() methods now return the XML as string. This 
should not be a problem, since SOAP should use UTF-8 encoding for transport. 
Returning a string also seems faster than returning a base64 encoded byte 
array.

Also, retrieve() can now return more than one result from the result set 
(returned as String[]). This is faster than calling retrieve() for every 
single result.

All methods are documented in the corresponding interfaces: see 
org.exist.soap.Query.java and org.exist.soap.Admin.java.

> 1. Is the lang() function scheduled for inclusion in the XPath processor
> any time soon? This is a fundamental requirement of my project. As you
> will know, @xml:lang='en' is not the same as lang('en') ;-)

Ok, I will try to implement the function as soon as I have some spare time 
during the next days.

Wolfgang