exist-development — eXist Developer's List

Re: [Exist-development] Lazy node sequences

[José M. F. G. <jm...@us...>]

I see, I think I'm going to follow that path. Sequence interface has some methods focused only on permanent storage, and other ones with no documentation. I have also seen that there is a method called toNodeSet(), which returns an instance of a class which implements NodeSet, but I think that in my implementation it should return nothing because it is there for permanent storage, am I right?

On 28/01/11 18:54, Dmitriy Shabanov wrote:
> You will need to implement Sequence interface for your xquery module function return. If you give move details it'll possible to give deeper answer :-)
>
> 2011/1/28 José María Fernández González <jm...@us... <mailto:jm...@us...>>
>
>     Hi everybody,
>             I want to write an XQuery module (I have already written other XQuery modules in Java) with a function which reads either a local text file or a local binary text resource, line by line, and which returns a lazy evaluated sequence of text lines. My idea is to use the sequence in FLOWR expressions, but I don't want the whole sequence to materialize in memory, because I want to use it in applications which can involve huge files/resources (several GB).
>
>             So, is it possible to do that? And if it is so, which interfaces or classes from eXist core should I use?
>
>             Best Regards,
>                     José María
>     --
>     "La violencia es el último recurso del incompetente"
>             - Salvor Hardin en "La Fundación" de Isaac Asimov
>     "Premature optimization is the root of all evil." - Donald Knuth
>
>     José María Fernández González
>     e-mail: jos...@gm... <mailto:jos...@gm...>
>
>     ------------------------------------------------------------------------------
>     Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>     Finally, a world-class log management solution at an even better price-free!
>     Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>     February 28th, so secure your free ArcSight Logger TODAY!
>     http://p.sf.net/sfu/arcsight-sfd2d
>     _______________________________________________
>     Exist-development mailing list
>     Exi...@li... <mailto:Exi...@li...>
>     https://lists.sourceforge.net/lists/listinfo/exist-development
>
>
>
>
> --
> Dmitriy Shabanov

-- 
"La violencia es el último recurso del incompetente"
	- Salvor Hardin en "La Fundación" de Isaac Asimov
"Premature optimization is the root of all evil." - Donald Knuth

José María Fernández González
e-mail: jos...@gm...

Re: [Exist-development] Lazy node sequences

[Dmitriy S. <sha...@gm...>]

You will need to implement Sequence interface for your xquery module
function return. If you give move details it'll possible to give deeper
answer :-)

2011/1/28 José María Fernández González <jm...@us...>

> Hi everybody,
>        I want to write an XQuery module (I have already written other
> XQuery modules in Java) with a function which reads either a local text file
> or a local binary text resource, line by line, and which returns a lazy
> evaluated sequence of text lines. My idea is to use the sequence in FLOWR
> expressions, but I don't want the whole sequence to materialize in memory,
> because I want to use it in applications which can involve huge
> files/resources (several GB).
>
>        So, is it possible to do that? And if it is so, which interfaces or
> classes from eXist core should I use?
>
>        Best Regards,
>                José María
> --
> "La violencia es el último recurso del incompetente"
>        - Salvor Hardin en "La Fundación" de Isaac Asimov
> "Premature optimization is the root of all evil." - Donald Knuth
>
> José María Fernández González
> e-mail: jos...@gm...
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Dmitriy Shabanov

[Exist-development] Lazy node sequences

[José M. F. G. <jm...@us...>]

Hi everybody,
	I want to write an XQuery module (I have already written other XQuery modules in Java) with a function which reads either a local text file or a local binary text resource, line by line, and which returns a lazy evaluated sequence of text lines. My idea is to use the sequence in FLOWR expressions, but I don't want the whole sequence to materialize in memory, because I want to use it in applications which can involve huge files/resources (several GB).

	So, is it possible to do that? And if it is so, which interfaces or classes from eXist core should I use?

	Best Regards,
		José María
-- 
"La violencia es el último recurso del incompetente"
	- Salvor Hardin en "La Fundación" de Isaac Asimov
"Premature optimization is the root of all evil." - Donald Knuth

José María Fernández González
e-mail: jos...@gm...

Re: [Exist-development] Fwd: [Exist-commits] SF.net SVN: exist:[13631] trunk/eXist/webapp/biblio/mods

[Dmitriy S. <sha...@gm...>]

2011/1/28 Jens Østergaard Petersen <oe...@gm...>

> >> Yeah, sure. After export via Java Admin Client, most line-breaks
> (sometimes all) have been stripped and this often causes oXygen to choke. I
> could (manually) indent the documents, I guess, but it would be nicer to
> have the Admin Client maintain the line breaks.
>
>
Can you make sure that  Options->Indent enable? I do use same technics for
long time without any issue.

-- 
Dmitriy Shabanov

[Exist-development] Fwd: [Exist-commits] SF.net SVN: exist:[13631] trunk/eXist/webapp/biblio/mods

[Jens Ø. P. <oe...@gm...>]

Forgot to mail the list.

Begin forwarded message:

> From: Joe Wicentowski <jo...@gm...>
> Date: January 28, 2011 5:17:02 PM GMT+01:00
> To: Jens Østergaard Petersen <oe...@gm...>
> Subject: Re: [Exist-commits] SF.net SVN: exist:[13631] trunk/eXist/webapp/biblio/mods
> 
> Hi Jens,
> 
> Thanks for your reply!  I think it'd be helpful for the others in the
> exist-development list to see this - I think you only sent it to me.
> Could you send it to the list too?
> 
> Have a good weekend too!
> Joe
> 
> 
> 2011/1/28 Jens Østergaard Petersen <oe...@gm...>:
>> 
>> On Jan 28, 2011, at 3:01 PM, Joe Wicentowski wrote:
>> 
>>> Hi folks,
>>> 
>>> I've noticed that some commits of XML files, such as Jens' below, come
>>> as a single, looooong line with no line breaks.  This makes it
>>> impossible to spot what changed in the commit, and I imagine it's not
>>> very efficient from an SVN perspective in which only "deltas" are
>>> stored.
>>> 
>>> I suspect this is caused by eXist's WebDAV or Java admin client not
>>> indenting during serialization.  Jens - which method are you using to
>>> get files out of eXist and into your SVN working directory?
>> 
>> I export from db via Java Admin Client, copy to webapp folder (manually!), commit via oXygen SVN Client.
>> 
>>> Am I
>>> right that the lack of indentation is unintended, Jens?
>> 
>> Yeah, sure. After export via Java Admin Client, most line-breaks (sometimes all) have been stripped and this often causes oXygen to choke. I could (manually) indent the documents, I guess, but it would be nicer to have the Admin Client maintain the line breaks.
>> 
>>> Are there steps we could recommend Jens to follow to prevent this
>>> phenomenon from occurring?
>> 
>> Thanks for bringing this up, Joe.
>> 
>> Have a nice weekend!
>> 
>> Jens
>> 
>>> 
>>> Thanks,
>>> Joe
>>> 
>>>> -<code-table><code-table-name>date-encoding-code</code-table-name><status>finished</status><form>closed</form><basis>http://www.loc.gov/standards/mods/v3/mods-userguide-generalapp.html</basis><description/><notes/><items><item><label>(none selected)</label><value/></item><item><label>w3cdtf</label><value>w3cdtf</value><description>This value is used for the profile of ISO 8601 that specifies the following date pattern: YYYY-MM-DD.</description></item><item><label>iso8601</label><value>iso8601</value><description>This value is used for formatted dates allowed in ISO 8601 which use the alternative described as "basic" rather than "extended". This alternative specified in the standard uses the following date pattern: YYYYMMDD (hours, minutes, seconds may also be added). It is also used for other encodings specified in ISO 8601, e.g. date ranges, which are in the form of YYYY/YYYY (in which case start and end portions are not parsed). The ISO 8601 basic expression has been used widely in MARC 21 date elements.</description></item><item><label>marc</label><value>marc</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item></items></code-table>
>>>> \ No newline at end of file
>>>> +<code-table><code-table-name>date-encoding-code</code-table-name><status>finished</status><form>closed</form><basis>http://www.loc.gov/standards/mods/v3/mods-userguide-generalapp.html</basis><description/><notes/><items><item><label>(none selected)</label><value/></item><item><label>YYYY-MM-DD</label><value>w3cdtf</value><description>This value is used for the profile of ISO 8601 that specifies the following date pattern: YYYY-MM-DD.</description></item><item><label>iso8601</label><value>iso8601</value><description>This value is used for formatted dates allowed in ISO 8601 which use the alternative described as "basic" rather than "extended". This alternative specified in the standard uses the following date pattern: YYYYMMDD (hours, minutes, seconds may also be added). It is also used for other encodings specified in ISO 8601, e.g. date ranges, which are in the form of YYYY/YYYY (in which case start and end portions are not parsed). The ISO 8601 basic expression has been used widely in MARC 21 date elements.</description></item><item><label>marc</label><value>marc</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item><item type="added"><label>text</label><value>text</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item></items></code-table>
>> 
>> 

Re: [Exist-development] Developers Teleconference

[Wolfgang M. <wol...@ex...>]

> Are non-core developers welcome to listen in on these meetings?

Sure, it is open to everyone. Just send me your skype contact for the next
meeting next week. Today I need to leave short after 4 utc, so I cannot host
it.

Wolfgang

Re: [Exist-development] Developers Teleconference

[Patrick B. <pat...@jo...>]

Are non-core developers welcome to listen in on these meetings?

-Patrick

On Fri, Jan 28, 2011 at 10:17 AM, Wolfgang Meier <wol...@ex...>wrote:

> Hi guys,
>
> there will be no developer's skype conference today. I nearly forgot
> that I won't have time to talk. We'll repeat it next week.
>
> Wolfgang
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Patrick Bosek
Jorsek Software
Cell (585) 820 9634
Office (585) 239 6060
Jorsek.com

Re: [Exist-development] Developers Teleconference

[Wolfgang M. <wol...@ex...>]

Hi guys,

there will be no developer's skype conference today. I nearly forgot
that I won't have time to talk. We'll repeat it next week.

Wolfgang

Re: [Exist-development] [Exist-commits] SF.net SVN: exist:[13631] trunk/eXist/webapp/biblio/mods

[Joe W. <jo...@gm...>]

Hi folks,

I've noticed that some commits of XML files, such as Jens' below, come
as a single, looooong line with no line breaks.  This makes it
impossible to spot what changed in the commit, and I imagine it's not
very efficient from an SVN perspective in which only "deltas" are
stored.

I suspect this is caused by eXist's WebDAV or Java admin client not
indenting during serialization.  Jens - which method are you using to
get files out of eXist and into your SVN working directory?  Am I
right that the lack of indentation is unintended, Jens?

Are there steps we could recommend Jens to follow to prevent this
phenomenon from occurring?

Thanks,
Joe

> -<code-table><code-table-name>date-encoding-code</code-table-name><status>finished</status><form>closed</form><basis>http://www.loc.gov/standards/mods/v3/mods-userguide-generalapp.html</basis><description/><notes/><items><item><label>(none selected)</label><value/></item><item><label>w3cdtf</label><value>w3cdtf</value><description>This value is used for the profile of ISO 8601 that specifies the following date pattern: YYYY-MM-DD.</description></item><item><label>iso8601</label><value>iso8601</value><description>This value is used for formatted dates allowed in ISO 8601 which use the alternative described as "basic" rather than "extended". This alternative specified in the standard uses the following date pattern: YYYYMMDD (hours, minutes, seconds may also be added). It is also used for other encodings specified in ISO 8601, e.g. date ranges, which are in the form of YYYY/YYYY (in which case start and end portions are not parsed). The ISO 8601 basic expression has been used widely in MARC 21 date elements.</description></item><item><label>marc</label><value>marc</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item></items></code-table>
> \ No newline at end of file
> +<code-table><code-table-name>date-encoding-code</code-table-name><status>finished</status><form>closed</form><basis>http://www.loc.gov/standards/mods/v3/mods-userguide-generalapp.html</basis><description/><notes/><items><item><label>(none selected)</label><value/></item><item><label>YYYY-MM-DD</label><value>w3cdtf</value><description>This value is used for the profile of ISO 8601 that specifies the following date pattern: YYYY-MM-DD.</description></item><item><label>iso8601</label><value>iso8601</value><description>This value is used for formatted dates allowed in ISO 8601 which use the alternative described as "basic" rather than "extended". This alternative specified in the standard uses the following date pattern: YYYYMMDD (hours, minutes, seconds may also be added). It is also used for other encodings specified in ISO 8601, e.g. date ranges, which are in the form of YYYY/YYYY (in which case start and end portions are not parsed). The ISO 8601 basic expression has been used widely in MARC 21 date elements.</description></item><item><label>marc</label><value>marc</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item><item type="added"><label>text</label><value>text</value><description>This value is used only for dates coded according to MARC 21 rules in field 008/07-14 for dates of publication/issuance. Thus, this would only apply to the attribute in dateIssued. Examples include: 19uu (a MARC convention to show unknown digits in a date), 9999 (a MARC convention showing that the end date has not occurred or is not known).</description></item></items></code-table>

Re: [Exist-development] multi lingual XQuery support in eXist

[Thomas W. <tho...@gm...>]

Rohit,

I have used eXist for multi-language applications. The format I used is:

<catalogue xml:lang="en" locale="en" pk="key" default="yes" base="yes" ts="2010-07-05T16:12:26.984+01:00" >
    <message key="accomodation.type.alpine-hut" ts="2009-09-13T13:49:32.515+01:00">Alpine Hut</message>
    <message key="accomodation.type.backpackers" ts="2009-09-13T13:49:32.609+01:00">Backpackers</message>
    <message key="accomodation.type.bb">Bed and Breakfast</message>
    <message key="accomodation.type.farm-stay" ts="2009-09-08T13:22:57.343+01:00">Farm Stay</message>
    <message key="accomodation.type.four-star" ts="2009-09-08T15:43:39.312+01:00">Four Stars Hotel</message>
    <message key="accomodation.type.guest-house" ts="2009-09-13T13:49:32.671+01:00">Guest House</message>
    <message key="accomodation.type.holiday-home" ts="2009-09-08T16:36:26.265+01:00">Holiday Home</message>
</catalogue>


For each locale there is a version of this file save in the db with different  xml:lang="xx" locale="xx" attributes.

You can create a XQuery/XSLT function that will take two parameters: a locale and a string key. Depending on the locale the function will select the corresponding string.
In your code/templates  you have to use a key instead of the string and call to the function to get the string for the chosen locale.
You can use Google Translate for an initial translation of thr strings.

The format can be extended to include parameters inside the text like %1 or split the text and parameters in elements.

I hope this will help.

Thomas

  ----- Original Message ----- 
  From: Casey Jordan 
  To: Rohit Jain (MT2010118) 
  Cc: Loren Cahlander ; exi...@li... 
  Sent: Thursday, January 27, 2011 2:58 PM
  Subject: Re: [Exist-development] multi lingual XQuery support in eXist


  Rohit,

  I am not aware of any standards methods for doing what you want to do. You could create an xml file that mapped the associations between your elements (and use it to join your queries), however the general idea of having the same tags in different languages is, to be honest, somewhat backwards and not how xml was intended to be used.

  A suggestion:

  Use xslt to normalize all your files to use the same tag names so that it correctly conforms to a schema, and add @xml:lang attributes to signify language.

  If you have no control over the xml and you cannot transform it, you will have to create another xml file to hold relations and join based on that, but this can be tricky and the file could get unwieldy depending on the number of permutations you have.

  Cheers,

  Casey



  On Thu, Jan 27, 2011 at 12:06 AM, Rohit Jain (MT2010118) <roh...@ii...> wrote:

    @Jordan

    it was just for example , structure of document may or may not be similar
    for example consider in a same document both tags are present having same meaning but belongs to different language,

    <contents>
          <Datos>Datos en Inglés</Datos>

          <data> data not similar to above, but still tags means the same <data>
    </contents>

    now if query something like this

    doc("file.xml")/contents/data or doc("file.xml")/contents/Datos

    i should get both the result as both data and Datos means the same but just in different language

    @Loren

    i was considering no control over xml file, but still ok if i enforce the use if xml:lang tag then how could i make use of it to solve the issue i mentioned above.
    ________________________________________
    From: Loren Cahlander [lor...@gm...]
    Sent: Thursday, January 27, 2011 8:01 AM
    To: Casey Jordan
    Cc: Loren Cahlander; Rohit Jain (MT2010118); exi...@li...
    Subject: Re: [Exist-development] multi lingual XQuery support in eXist


    You should use the attribute xml:lang in the tag.

    Please check out Best Practices for XML Internationalization
    http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/

    Loren

    On Jan 26, 2011, at 5:47 PM, Casey Jordan wrote:

    Rohit,

    Is the schema for each of the three files the same? So they are structurally identical?

    An example would be helpful, something like:

    <contents>
        <data>Data in english</data>
    </contents>

    <contents>
        <data>Datos en Inglés</data>
    </contents>

    with the query you want to run and the results you want to see.

    Cheers,

    Casey


    On Wed, Jan 26, 2011 at 12:20 PM, Rohit Jain (MT2010118) <roh...@ii...<mailto:roh...@ii...>> wrote:
    Hey,

    is it some way in which we can support multi lingual query in eXist database, to explain clearly,,, suppose i have a collection of 3 XML files containing same data but in different language.
    Suppose all 3 have a element common in them suppose "data" so if i Query for "data" in 1 language it should gives me result from all files that may be containing "data" but in some other language also.

    So is there some other way in which we can extend eXist to support such Query and in some way make our database capable of such problems.
    It might not be related to eXist but we are planning to implement it for eXist database so just looking for some guidance and if eXist doesn't supports it then what could be few suggestions for this and what API and other tools we can use to accomplish this task.

    Thank You,
    Rohit Jain
    IIITB
    ------------------------------------------------------------------------------
    Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
    Finally, a world-class log management solution at an even better price-free!
    Download using promo code Free_Logger_4_Dev2Dev. Offer expires
    February 28th, so secure your free ArcSight Logger TODAY!
    http://p.sf.net/sfu/arcsight-sfd2d
    _______________________________________________
    Exist-development mailing list

    Exi...@li...<mailto:Exi...@li...>

    https://lists.sourceforge.net/lists/listinfo/exist-development



    --
    --
    Casey Jordan
    Jorsek Software LLC.
    "CaseyDJordan" on LinkedIn, Twitter & Facebook
    Cell (585) 348 7399
    Office (585) 239 6060

    Jorsek.com<http://Jorsek.com>



    This message is intended only for the use of the Addressee(s) and may
    contain information that is privileged, confidential, and/or exempt from
    disclosure under applicable law.  If you are not the intended recipient,
    please be advised that any disclosure  copying, distribution, or use of
    the information contained herein is prohibited.  If you have received
    this communication in error, please destroy all copies of the message,
    whether in electronic or hard copy format, as well as attachments, and
    immediately contact the sender by replying to this e-mail or by phone.
    Thank you.
    ------------------------------------------------------------------------------
    Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
    Finally, a world-class log management solution at an even better price-free!
    Download using promo code Free_Logger_4_Dev2Dev. Offer expires
    February 28th, so secure your free ArcSight Logger TODAY!
    http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________
    Exist-development mailing list
    Exi...@li...
    https://lists.sourceforge.net/lists/listinfo/exist-development





  -- 
  --
  Casey Jordan
  Jorsek Software LLC.
  "CaseyDJordan" on LinkedIn, Twitter & Facebook
  Cell (585) 348 7399
  Office (585) 239 6060
  Jorsek.com


  This message is intended only for the use of the Addressee(s) and may
  contain information that is privileged, confidential, and/or exempt from
  disclosure under applicable law.  If you are not the intended recipient,
  please be advised that any disclosure  copying, distribution, or use of
  the information contained herein is prohibited.  If you have received
  this communication in error, please destroy all copies of the message,
  whether in electronic or hard copy format, as well as attachments, and
  immediately contact the sender by replying to this e-mail or by phone.
  Thank you.



------------------------------------------------------------------------------


  ------------------------------------------------------------------------------
  Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
  Finally, a world-class log management solution at an even better price-free!
  Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
  February 28th, so secure your free ArcSight Logger TODAY! 
  http://p.sf.net/sfu/arcsight-sfd2d


------------------------------------------------------------------------------


  _______________________________________________
  Exist-development mailing list
  Exi...@li...
  https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] multi lingual XQuery support in eXist

[Casey J. <cas...@jo...>]

Rohit,

I am not aware of any standards methods for doing what you want to do. You
could create an xml file that mapped the associations between your elements
(and use it to join your queries), however the general idea of having the
same tags in different languages is, to be honest, somewhat backwards and
not how xml was intended to be used.

A suggestion:

Use xslt to normalize all your files to use the same tag names so that it
correctly conforms to a schema, and add @xml:lang attributes to signify
language.

If you have no control over the xml and you cannot transform it, you will
have to create another xml file to hold relations and join based on that,
but this can be tricky and the file could get unwieldy depending on the
number of permutations you have.

Cheers,

Casey


On Thu, Jan 27, 2011 at 12:06 AM, Rohit Jain (MT2010118) <
roh...@ii...> wrote:

> @Jordan
>
> it was just for example , structure of document may or may not be similar
> for example consider in a same document both tags are present having same
> meaning but belongs to different language,
>
> <contents>
>       <Datos>Datos en Inglés</Datos>
>
>       <data> data not similar to above, but still tags means the same
> <data>
> </contents>
>
> now if query something like this
>
> doc("file.xml")/contents/data or doc("file.xml")/contents/Datos
>
> i should get both the result as both data and Datos means the same but just
> in different language
>
> @Loren
>
> i was considering no control over xml file, but still ok if i enforce the
> use if xml:lang tag then how could i make use of it to solve the issue i
> mentioned above.
> ________________________________________
> From: Loren Cahlander [lor...@gm...]
> Sent: Thursday, January 27, 2011 8:01 AM
> To: Casey Jordan
> Cc: Loren Cahlander; Rohit Jain (MT2010118);
> exi...@li...
> Subject: Re: [Exist-development] multi lingual XQuery support in eXist
>
> You should use the attribute xml:lang in the tag.
>
> Please check out Best Practices for XML Internationalization
> http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/
>
> Loren
>
> On Jan 26, 2011, at 5:47 PM, Casey Jordan wrote:
>
> Rohit,
>
> Is the schema for each of the three files the same? So they are
> structurally identical?
>
> An example would be helpful, something like:
>
> <contents>
>     <data>Data in english</data>
> </contents>
>
> <contents>
>     <data>Datos en Inglés</data>
> </contents>
>
> with the query you want to run and the results you want to see.
>
> Cheers,
>
> Casey
>
> On Wed, Jan 26, 2011 at 12:20 PM, Rohit Jain (MT2010118) <
> roh...@ii...<mailto:roh...@ii...>> wrote:
> Hey,
>
> is it some way in which we can support multi lingual query in eXist
> database, to explain clearly,,, suppose i have a collection of 3 XML files
> containing same data but in different language.
> Suppose all 3 have a element common in them suppose "data" so if i Query
> for "data" in 1 language it should gives me result from all files that may
> be containing "data" but in some other language also.
>
> So is there some other way in which we can extend eXist to support such
> Query and in some way make our database capable of such problems.
> It might not be related to eXist but we are planning to implement it for
> eXist database so just looking for some guidance and if eXist doesn't
> supports it then what could be few suggestions for this and what API and
> other tools we can use to accomplish this task.
>
> Thank You,
> Rohit Jain
> IIITB
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...<mailto:
> Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>
>
> --
> --
> Casey Jordan
> Jorsek Software LLC.
> "CaseyDJordan" on LinkedIn, Twitter & Facebook
> Cell (585) 348 7399
> Office (585) 239 6060
> Jorsek.com<http://Jorsek.com>
>
>
> This message is intended only for the use of the Addressee(s) and may
> contain information that is privileged, confidential, and/or exempt from
> disclosure under applicable law.  If you are not the intended recipient,
> please be advised that any disclosure  copying, distribution, or use of
> the information contained herein is prohibited.  If you have received
> this communication in error, please destroy all copies of the message,
> whether in electronic or hard copy format, as well as attachments, and
> immediately contact the sender by replying to this e-mail or by phone.
> Thank you.
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
>
> http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________
> Exist-development<http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________%0AExist-development>mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
--
Casey Jordan
Jorsek Software LLC.
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 348 7399
Office (585) 239 6060
Jorsek.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.

Re: [Exist-development] building & using xmldb samples (was (no subject))

[Stefan M. <ste...@un...>]

On 27/01/11 10:33, Rohit Jain (MT2010118) wrote:
> folder itself at following path : eXist/samples/src/org/exist/examples/xmldb
> but i am unable to compile them or use them,

in a shell you can trigger the build with

./build.sh samples

for windows this would probably be

build.bat samples

this should compile the samples if you have a build environment in 
place. I haven't used them myself as I don't use the xml:db api, so you 
probably still have to find out how to use them. But, as these are 
examples, you have to figure this out anyway if you want to use similar 
approaches in your own code.

cheers,
Stefan

[Exist-development] (no subject)

[Rohit J. (MT2010118) <roh...@ii...>]

Hey,
 had been looking to use XML:DB API with eXist, and on looking i got set of example in eXist folder itself at following path : eXist/samples/src/org/exist/examples/xmldb
but i am unable to compile them or use them, so could you please help me out by providing with exact steps so that i can use them.
I would be thankful if someone could help me out in using XML:DB with eXist, i am stuck up with packages and files to import in my program.

Re: [Exist-development] multi lingual XQuery support in eXist

[Rohit J. (MT2010118) <roh...@ii...>]

@Jordan

it was just for example , structure of document may or may not be similar
for example consider in a same document both tags are present having same meaning but belongs to different language,

<contents>
       <Datos>Datos en Inglés</Datos>

       <data> data not similar to above, but still tags means the same <data>
</contents>

now if query something like this 

doc("file.xml")/contents/data or doc("file.xml")/contents/Datos

i should get both the result as both data and Datos means the same but just in different language 

@Loren

i was considering no control over xml file, but still ok if i enforce the use if xml:lang tag then how could i make use of it to solve the issue i mentioned above.
________________________________________
From: Loren Cahlander [lor...@gm...]
Sent: Thursday, January 27, 2011 8:01 AM
To: Casey Jordan
Cc: Loren Cahlander; Rohit Jain (MT2010118); exi...@li...
Subject: Re: [Exist-development] multi lingual XQuery support in eXist

You should use the attribute xml:lang in the tag.

Please check out Best Practices for XML Internationalization
http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/

Loren

On Jan 26, 2011, at 5:47 PM, Casey Jordan wrote:

Rohit,

Is the schema for each of the three files the same? So they are structurally identical?

An example would be helpful, something like:

<contents>
     <data>Data in english</data>
</contents>

<contents>
     <data>Datos en Inglés</data>
</contents>

with the query you want to run and the results you want to see.

Cheers,

Casey

On Wed, Jan 26, 2011 at 12:20 PM, Rohit Jain (MT2010118) <roh...@ii...<mailto:roh...@ii...>> wrote:
Hey,

is it some way in which we can support multi lingual query in eXist database, to explain clearly,,, suppose i have a collection of 3 XML files containing same data but in different language.
Suppose all 3 have a element common in them suppose "data" so if i Query for "data" in 1 language it should gives me result from all files that may be containing "data" but in some other language also.

So is there some other way in which we can extend eXist to support such Query and in some way make our database capable of such problems.
It might not be related to eXist but we are planning to implement it for eXist database so just looking for some guidance and if eXist doesn't supports it then what could be few suggestions for this and what API and other tools we can use to accomplish this task.

Thank You,
Rohit Jain
IIITB
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Exist-development mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-development



--
--
Casey Jordan
Jorsek Software LLC.
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 348 7399
Office (585) 239 6060
Jorsek.com<http://Jorsek.com>


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________
Exist-development mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] multi lingual XQuery support in eXist

[Loren C. <lor...@gm...>]

You should use the attribute xml:lang in the tag.

Please check out Best Practices for XML Internationalization
http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/

Loren

On Jan 26, 2011, at 5:47 PM, Casey Jordan wrote:

> Rohit,
> 
> Is the schema for each of the three files the same? So they are structurally identical?
> 
> An example would be helpful, something like:
> 
> <contents>
>      <data>Data in english</data>
> </contents>
> 
> <contents>
>      <data>Datos en Inglés</data>
> </contents>
> 
> with the query you want to run and the results you want to see.
> 
> Cheers,
> 
> Casey
> 
> On Wed, Jan 26, 2011 at 12:20 PM, Rohit Jain (MT2010118) <roh...@ii...> wrote:
> Hey,
> 
> is it some way in which we can support multi lingual query in eXist database, to explain clearly,,, suppose i have a collection of 3 XML files containing same data but in different language.
> Suppose all 3 have a element common in them suppose "data" so if i Query for "data" in 1 language it should gives me result from all files that may be containing "data" but in some other language also.
> 
> So is there some other way in which we can extend eXist to support such Query and in some way make our database capable of such problems.
> It might not be related to eXist but we are planning to implement it for eXist database so just looking for some guidance and if eXist doesn't supports it then what could be few suggestions for this and what API and other tools we can use to accomplish this task.
> 
> Thank You,
> Rohit Jain
> IIITB
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
> 
> 
> 
> -- 
> --
> Casey Jordan
> Jorsek Software LLC.
> "CaseyDJordan" on LinkedIn, Twitter & Facebook
> Cell (585) 348 7399
> Office (585) 239 6060
> Jorsek.com
> 
> 
> This message is intended only for the use of the Addressee(s) and may
> contain information that is privileged, confidential, and/or exempt from
> disclosure under applicable law.  If you are not the intended recipient,
> please be advised that any disclosure  copying, distribution, or use of
> the information contained herein is prohibited.  If you have received
> this communication in error, please destroy all copies of the message,
> whether in electronic or hard copy format, as well as attachments, and
> immediately contact the sender by replying to this e-mail or by phone.
> Thank you.
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
> February 28th, so secure your free ArcSight Logger TODAY! 
> http://p.sf.net/sfu/arcsight-sfd2d_______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] multi lingual XQuery support in eXist

[Casey J. <cas...@jo...>]

Rohit,

Is the schema for each of the three files the same? So they are structurally
identical?

An example would be helpful, something like:

<contents>
     <data>Data in english</data>
</contents>

<contents>
     <data>Datos en Inglés</data>
</contents>

with the query you want to run and the results you want to see.

Cheers,

Casey

On Wed, Jan 26, 2011 at 12:20 PM, Rohit Jain (MT2010118) <
roh...@ii...> wrote:

> Hey,
>
> is it some way in which we can support multi lingual query in eXist
> database, to explain clearly,,, suppose i have a collection of 3 XML files
> containing same data but in different language.
> Suppose all 3 have a element common in them suppose "data" so if i Query
> for "data" in 1 language it should gives me result from all files that may
> be containing "data" but in some other language also.
>
> So is there some other way in which we can extend eXist to support such
> Query and in some way make our database capable of such problems.
> It might not be related to eXist but we are planning to implement it for
> eXist database so just looking for some guidance and if eXist doesn't
> supports it then what could be few suggestions for this and what API and
> other tools we can use to accomplish this task.
>
> Thank You,
> Rohit Jain
> IIITB
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
--
Casey Jordan
Jorsek Software LLC.
"CaseyDJordan" on LinkedIn, Twitter & Facebook
Cell (585) 348 7399
Office (585) 239 6060
Jorsek.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.

[Exist-development] multi lingual XQuery support in eXist

[Rohit J. (MT2010118) <roh...@ii...>]

Hey,

is it some way in which we can support multi lingual query in eXist database, to explain clearly,,, suppose i have a collection of 3 XML files containing same data but in different language.
Suppose all 3 have a element common in them suppose "data" so if i Query for "data" in 1 language it should gives me result from all files that may be containing "data" but in some other language also.

So is there some other way in which we can extend eXist to support such Query and in some way make our database capable of such problems.
It might not be related to eXist but we are planning to implement it for eXist database so just looking for some guidance and if eXist doesn't supports it then what could be few suggestions for this and what API and other tools we can use to accomplish this task.

Thank You,
Rohit Jain
IIITB

Re: [Exist-development] perfomance issue

[Dmitriy S. <sha...@gm...>]

minimal bits is 32, more and more of 64 one, so maybe use int or long here?

On Wed, Jan 26, 2011 at 4:52 PM, Evgeny Gazdovsky <gaz...@gm...>wrote:

>
>
> 2011/1/26 Evgeny Gazdovsky <gaz...@gm...>
>
>> Just we have one more complex problem:
>>
>>
>> lines 71, 72 of SymbolTable.java:
>>
>>     public static int LENGTH_LOCAL_NAME = 2; //sizeof short
>>>     public static int LENGTH_NS_URI = 2; //sizeof short
>>>
>>
>>
>> This is limit the number of namespaces or local names by 32K values.
>>
>
>
> Exception in result:
>
> java.lang.ArrayIndexOutOfBoundsException: -32768
>     at org.exist.dom.SymbolTable.getSymbol(SymbolTable.java:204)
>     at
> org.exist.storage.structural.NativeStructuralIndexWorker.computeKey(NativeStructuralIndexWorker.java:525)
>     at
> org.exist.storage.structural.NativeStructuralIndexWorker.findElementsByTagName(NativeStructuralIndexWorker.java:84)
>
>
-- 
Dmitriy Shabanov

Re: [Exist-development] perfomance issue

[Evgeny G. <gaz...@gm...>]

2011/1/26 Evgeny Gazdovsky <gaz...@gm...>

> Just we have one more complex problem:
>
> lines 71, 72 of SymbolTable.java:
>
>     public static int LENGTH_LOCAL_NAME = 2; //sizeof short
>>     public static int LENGTH_NS_URI = 2; //sizeof short
>>
>
>
> This is limit the number of namespaces or local names by 32K values.
>


Exception in result:

java.lang.ArrayIndexOutOfBoundsException: -32768
    at org.exist.dom.SymbolTable.getSymbol(SymbolTable.java:204)
    at
org.exist.storage.structural.NativeStructuralIndexWorker.computeKey(NativeStructuralIndexWorker.java:525)
    at
org.exist.storage.structural.NativeStructuralIndexWorker.findElementsByTagName(NativeStructuralIndexWorker.java:84)


--
Evgeny

Re: [Exist-development] perfomance issue

[Evgeny G. <gaz...@gm...>]

Just we have one more complex problem:

lines 71, 72 of SymbolTable.java:

    public static int LENGTH_LOCAL_NAME = 2; //sizeof short
>     public static int LENGTH_NS_URI = 2; //sizeof short
>


This is limit the number of namespaces or local names by 32K values.

--
Evgeny

Re: [Exist-development] perfomance issue

[Evgeny G. <gaz...@gm...>]

2011/1/26 Evgeny Gazdovsky <gaz...@gm...>

>
>
> 2011/1/25 Wolfgang Meier <wol...@ex...>
>
> Evgeny,
>>
>> as you found out, the performance issue was caused by the symbol table
>> being written out entirely after adding a new element name. I fixed
>> this in rev 13637. Both of your example queries should now run at
>> roughly the same speed.
>>
>> My commit changes the storage format of symbols.dbx. However,
>> databases using the old format should be transparently upgraded to the
>> new format.
>>
>> Wolfgang
>>
>>
>

Cool! 10K names takes ~50sec!

--
Evgeny

Re: [Exist-development] perfomance issue

[Evgeny G. <gaz...@gm...>]

2011/1/25 Wolfgang Meier <wol...@ex...>

> Evgeny,
>
> as you found out, the performance issue was caused by the symbol table
> being written out entirely after adding a new element name. I fixed
> this in rev 13637. Both of your example queries should now run at
> roughly the same speed.
>
> My commit changes the storage format of symbols.dbx. However,
> databases using the old format should be transparently upgraded to the
> new format.
>
> Wolfgang
>
>
Thanks very much!
Just will test

--
Evgeny

Re: [Exist-development] perfomance issue

[Wolfgang M. <wol...@ex...>]

Evgeny,

as you found out, the performance issue was caused by the symbol table
being written out entirely after adding a new element name. I fixed
this in rev 13637. Both of your example queries should now run at
roughly the same speed.

My commit changes the storage format of symbols.dbx. However,
databases using the old format should be transparently upgraded to the
new format.

Wolfgang


2011/1/20 Wolfgang Meier <wol...@ex...>:
>> Second query store docs with different element names:
>>
>>> for $i in (1 to 10000)
>>> return
>>>     xmldb:store("/db/temp", (), element {concat('tmp', $i)} {$i})
>
> I have not done any profiling yet, so I'm not sure why this is slow. I
> would expect it to be a bit slower, but probably not as much.
>
> However, I wonder why you need to store 10000 different root elements?
> It sounds like bad XML.
>
> Wolfgang
>

Re: [Exist-development] error in embedding eXist in an application

[Dmitriy S. <sha...@gm...>]

You don't have exist.jar in your classpath.

On Tue, Jan 25, 2011 at 7:19 PM, Rohit Jain (MT2010118) <
roh...@ii...> wrote:

>   Hey, i followed the steps given in
> http://exist-db.org/deployment.html#N1040E to deploy eXist , i read your
> mailing list and somehow got to compile the code but getting class not found
> error :org.exist.xmldb.DatabaseImpl
>
>  also if you can through some light on how exactly things are happening
> and what those library are doing then it will be a bit easier to understand
> the working of eXist  as per the deployment is concerned.
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>


-- 
Dmitriy Shabanov

Re: [Exist-development] regarding embeddding xquery in java

[Loren C. <lor...@gm...>]

We should probably have a utility class to do some of these common things so that no-one has to reinvent the wheel.

Loren

On Jan 25, 2011, at 10:06 AM, Dannes Wessels wrote:

> Bharat,
> 
> On Tue, Jan 25, 2011 at 4:39 PM, Dmitriy Shabanov <sha...@gm...> wrote:
>> Here the java code, it use xmldb interface
>> hope,that help.
> 
> please have a good look at the distribution. We have lot's of junit
> tests, and a well filled "samples" directory, containing code samples
> for many of the interfaces.
> 
> For embedded use, i'd recommend to use the 'fluent' api.
> 
> D.
> 
> 
> 
> 
> -- 
> eXist-db Native XML Database - http://exist-db.org
> Join us on linked-in: http://www.linkedin.com/groups?gid=35624
> 
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
> February 28th, so secure your free ArcSight Logger TODAY! 
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development