zorba-coders team mailing list archive

[Matthias Brantner <matthias.brantner@xxxxxxxxxx>]

I agree with William. I think that we should make sure that the implementation
of the XQJ API does the cleanup automatically. Otherwise, our implementation
will not be conformant with others. For example, Zorba might raise an error
if Oxygen doesn't close the Connection.

On Jan 31, 2012, at 12:07 PM, William Candillon wrote:

> I was looking at this tutorial: http://www.xquery.com/tutorials/xqj_tutorial/
> Could point me to this mandatory close() thing?
> 
> -- 
> You received this bug notification because you are a member of Zorba
> Coders, which is the registrant for Zorba.
> https://bugs.launchpad.net/bugs/921628
> 
> Title:
>  Text serialization with XQJ
> 
> Status in Zorba - The XQuery Processor:
>  New
> 
> Bug description:
>  With the XQJ branch, the following program:
> 
>  		XQDataSource xqds = new XQDataSource();
>  		XQConnection xqc = xqds.getConnection();
>  		Properties serializationProps = new java.util.Properties();
>  		serializationProps.setProperty("method", "text");
>  		XQExpression xqe;
>  		XQSequence xqs;
>  		xqe = xqc.createExpression();
>  		xqs = xqe.executeQuery("(<foo />, <bar />)");
>  		int i = 1;
>  		while (xqs.next()) {
>  		  FileOutputStream file;
>  		  
>  		  xqs.writeItem(System.out, serializationProps);
>  		}
> 
>  Outputs:
> 
>  <foo/><bar/>i = 0 String file:/// is still in the pool
>  Zorba Internal Fatal Error in /Users/wcandillon/tmp/xqj/src/store/naive/string_pool.cpp:42:
>  "count == 0": condition failed: 1 strings remain in the string pool
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/zorba/+bug/921628/+subscriptions
> 
> -- 
> Mailing list: https://launchpad.net/~zorba-coders
> Post to     : zorba-coders@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zorba-coders
> More help   : https://help.launchpad.net/ListHelp