exist-development — eXist Developer's List

Re: [Exist-development] org.xml.sax.SAXParseException - Prefixed namespace bindings may not be empty.

[Alister P. <gsp...@gm...>]

Hi Michael,
That’s a great suggestion - I hadn’t considered trying to fix the problem from the XQuery side. I’ve looked through the Neko options and can’t see anything that will fix the problem - so solving in XQuery might be best.

Regards,
Alister.
On 1 Sep 2014, at 3:46 pm, Michael Westbay <wes...@ja...> wrote:

> Pillow-san,
> 
> I forgot to mention,
> Anyway, I control NekoHTML from the XQuery side in this way. You shouldn't have any trouble accessing it similarly in your Java module.
> 
> 
> The key is to fetch the document as as non-XML, process the bad parts with regular expressions as a string, then parse it to XML.
> 
> Hope this provides a hint that gets you through.
> 
> -- 
> Michael Westbay
> Writer/System Administrator
> http://www.japanesebaseball.com/

Re: [Exist-development] org.xml.sax.SAXParseException - Prefixed namespace bindings may not be empty.

[Michael W. <wes...@ja...>]

Pillow-san,

I forgot to mention,

> Anyway, I control NekoHTML from the XQuery side in this way. You shouldn't
> have any trouble accessing it similarly in your Java module.
>

The key is to fetch the document as as non-XML, process the bad parts with
regular expressions as a string, *then* parse it to XML.

Hope this provides a hint that gets you through.

-- 
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/

Re: [Exist-development] org.xml.sax.SAXParseException - Prefixed namespace bindings may not be empty.

[Michael W. <wes...@ja...>]

Pillow-san,

I get bad HTML that NekoHTML can only partially fix in my http-client
fetches all the time. Here's a trick I do in XQuery to deal with sites and
produce poor HTML that Neko's parser can't handle:

One site places two style="..." attributes in several elements. I don't
need the styles, so I declare a function in a variable like so:

*declare variable **$STRIP-STYLES* := *function*(*$body*) {
  *replace*(*$body*,'style="[^"]*"','')
};


Then I filter it out before converting the page from text to XML.

      *let* *$request* := <http:request *method*=*"GET"* *href*=*"*{*$url*}
*"* *override-media-type*=*"html"*>
        <http:header *name*=*"Connection"* *value*=*"close"*/>
      </http:request>
      *let* *$responses* := *http:send-request*(*$request*)
      *return if* (*$responses*[1]/*@status* eq '200') *then*
        *let **$body* := *util:binary-to-string*(*$responses*[2],*$encoding*
)
        (: Fix for all kinds of specific calamities :)
        *let* *$body* := *$STRIP-STYLES*(*$body*)
        *return **util:parse-html*(*$body*,*$options*)
      *else* ()


Oh, and options are defined as:

  *let $options* := <options>
    <feature *name*=*"http://cyberneko.org/html/features/scanner/script/strip-comment-delims
<http://cyberneko.org/html/features/scanner/script/strip-comment-delims>"*
*value*=*"true"*/>
    <property *name*=*"http://cyberneko.org/html/properties/default-encoding
<http://cyberneko.org/html/properties/default-encoding>"* *value*=*"*{
*$encoding*}*"*/>
    <property *name*=*"http://cyberneko.org/html/properties/names/elems
<http://cyberneko.org/html/properties/names/elems>"* *value*=*"upper"*/>
    <property *name*=*"http://cyberneko.org/html/properties/names/attrs
<http://cyberneko.org/html/properties/names/attrs>"* *value*=*"lower"*/>
  </options>


I auto set $encoding depending on the site as I access sites in English,
Japanese, Korean, Taiwanese, and Chinese (Taiwan uses a different character
encoding than mainland China when they don't use Unicode).

Anyway, I control NekoHTML from the XQuery side in this way. You shouldn't
have any trouble accessing it similarly in your Java module.

-- 
Michael Westbay
Writer/System Administrator
http://www.japanesebaseball.com/

Re: [Exist-development] org.xml.sax.SAXParseException - Prefixed namespace bindings may not be empty.

[Alister P. <gsp...@gm...>]

The error in more detail… Only happening when storing the document, not when parsing.
 
2014-08-31 17:19:02,585 [eXistThread-31] DEBUG (ModuleUtils.java [htmlToXHtml]:251) - Converting HTML to XML using NekoHTML parser for: alternative 
2014-08-31 17:19:03,724 [eXistThread-31] DEBUG (TransactionManager.java [execute]:159) - Starting new transaction: 5 
2014-08-31 17:19:03,730 [eXistThread-31] DEBUG (Collection.java [validateXMLResourceInternal]:1631) - Scanning document /db/test/message-6.xml 
2014-08-31 17:19:03,731 [eXistThread-31] DEBUG (GrammarPool.java [retrieveInitialGrammarSet]:81) - Retrieve initial grammarset (http://www.w3.org/TR/REC-xml). 
2014-08-31 17:19:03,731 [eXistThread-31] DEBUG (GrammarPool.java [retrieveInitialGrammarSet]:85) - Found 0 grammars. 
2014-08-31 17:19:03,740 [eXistThread-31] DEBUG (Indexer.java [fatalError]:419) - fatal error at (58,2064) : The value of the attribute "prefix="xmlns",localpart="o",rawname="xmlns:o"" is invalid. Prefixed namespace bindings may not be empty. 
2014-08-31 17:19:03,740 [eXistThread-31] DEBUG (GrammarPool.java [retrieveInitialGrammarSet]:81) - Retrieve initial grammarset (http://www.w3.org/TR/REC-xml). 
2014-08-31 17:19:03,740 [eXistThread-31] DEBUG (GrammarPool.java [retrieveInitialGrammarSet]:85) - Found 0 grammars. 
2014-08-31 17:19:03,741 [eXistThread-31] ERROR (XMLDBStore.java [evalWithCollection]:220) - The XML parser reported a problem: fatal error at (58,2064) : The value of the attribute "prefix="xmlns",localpart="o",rawname="xmlns:o"" is invalid. Prefixed namespace bindings may not be empty. 
org.xmldb.api.base.XMLDBException: The XML parser reported a problem: fatal error at (58,2064) : The value of the attribute "prefix="xmlns",localpart="o",rawname="xmlns:o"" is invalid. Prefixed namespace bindings may not be empty.
	at org.exist.xmldb.LocalCollection.storeXMLResource(LocalCollection.java:893)
	at org.exist.xmldb.LocalCollection.storeResource(LocalCollection.java:766)
	at org.exist.xmldb.LocalCollection.storeResource(LocalCollection.java:754)

I’ve tried adding a RemoveElement filter to the NekoHTML parser - but can’t make that work - no content is returned. The documentation seems to suggest that I have to add an acceptElement for every element I want to keep - which means all of HTML!!!

Now I’m trying a FilterInputStream approach - but that seems such a blunt instrument - any other suggestions on how to remove <o:p></o:p> from the result of htmlTXHtml?

This is how I modified ModuleUtils.htmlToXHtml 

  LOG.debug("Converting HTML to XML using NekoHTML parser for: " + url);
            reader = (XMLReader) Class.forName("org.cyberneko.html.parsers.SAXParser").newInstance();

            ElementRemover remover = new ElementRemover();
            remover.removeElement("o:p");
            // setup filter chain
            XMLDocumentFilter[] filters = {
                    remover
            };

            reader.setProperty("http://cyberneko.org/html/properties/names/elems","match");
            reader.setProperty("http://cyberneko.org/html/properties/names/attrs","no-change");
            reader.setProperty("http://cyberneko.org/html/properties/filters", filters); // ADDED FILTER here


On 31 Aug 2014, at 6:11 pm, Alister Pillow <gsp...@gm...> wrote:

> Hi,
> Trying to finish off the mail:get-messages function. The error appears when trying to store an email as xml in the /db.
> 
> I’ve hit a nasty little bug - nothing to do with eXist - and (surprise) related to mail from Microsoft Outlook - via Apple Mail. I now suspect that Apple Mail is the culprit.
> 
> I forwarded an email from my Inbox to another account and then retrieved it using mail:get-messages. 
> The original html section is full of <o:p></o:p> tags. These are end-of-paragraph markers inserted by MS Word when creating HTML.
> 
> In the original email, the prefix and namespace is declared - but in the forwarded message, it is missing - consequently I get an error from SAXParser when trying to store this content in the DB. 
> 
> Is there some way to tell the parser to skip these (empty) elements? Or will I have to write a filter for the text before parsing it?
> 
> I’m using Wolfgang’s suggestion:
> DocumentImpl html = ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(part.getInputStream()), null, null);
> ElementImpl rootElem = (ElementImpl)html.getDocumentElement();
> 
> (Otherwise, mail:get-messages is working quite nicely.)
> 
> Thanks,
> Alister.

[Exist-development] org.xml.sax.SAXParseException - Prefixed namespace bindings may not be empty.

[Alister P. <gsp...@gm...>]

Hi,
Trying to finish off the mail:get-messages function. The error appears when trying to store an email as xml in the /db.

I’ve hit a nasty little bug - nothing to do with eXist - and (surprise) related to mail from Microsoft Outlook - via Apple Mail. I now suspect that Apple Mail is the culprit.

I forwarded an email from my Inbox to another account and then retrieved it using mail:get-messages. 
The original html section is full of <o:p></o:p> tags. These are end-of-paragraph markers inserted by MS Word when creating HTML.

In the original email, the prefix and namespace is declared - but in the forwarded message, it is missing - consequently I get an error from SAXParser when trying to store this content in the DB. 

Is there some way to tell the parser to skip these (empty) elements? Or will I have to write a filter for the text before parsing it?

I’m using Wolfgang’s suggestion:
DocumentImpl html = ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(part.getInputStream()), null, null);
ElementImpl rootElem = (ElementImpl)html.getDocumentElement();

(Otherwise, mail:get-messages is working quite nicely.)

Thanks,
Alister.

Re: [Exist-development] mail message to xml

[Adam R. <ad...@ex...>]

> I’ve had a look at various options for representing email messages in XML, but there’s nothing appealing. They either try to capture every little detail or skimp.
> In the end, I chose to stay close to the form that is already used in the Mail Module - used by get-message-list-as-xml. The body content is stored as text and html if present, and attachments are available as base64 for storage. (I’ve successfully stored a PDF, ODT, PNG sent as attachments.)
>

Cool :-)

> mail:get-messages($folder-handle, $message-numbers)
>
> There is a problem with mail:get-message-list-as-xml.
> The message number is index based rather than coming from the folder:
> builder.addAttribute( new QName( "number", null, null ), String.valueOf( i ) ); // where “i” is the loop index.
>
> this should be:
> builder.addAttribute(new QName("number", null, null), String.valueOf(message.getMessageNumber()));
>
> This means you can’t use the message-list to choose a set of messages to retrieve.
>
> I think this is a bug - easily fixed - but will it cause a problem for anyone if I change it?

Nope please do, but as a separate commit.

>
> Message example:
> <mail:message xmlns:mail="http://exist-db.org/xquery/mail" number="5" contentType="multipart/mixed">
>     <mail:subject>open office doc</mail:subject>
>     <mail:sent>2014-08-27T12:55:43.000+09:30</mail:sent>
>     <mail:received>2014-08-27T12:54:40.000+09:30</mail:received>
>     <mail:from>Alister Pillow &lt;ali...@me...&gt;</mail:from>
>     <mail:recipients>
>         <mail:recipient type="to">in...@pe...</mail:recipient>
>     </mail:recipients>
>     <mail:text mime-type="text/plain; charset=windows-1252">Please find attached…
> </mail:text>
>     <mail:attachment filename="test.odt" mime-type="application/vnd.oasis.opendocument.text; x-mac-type=4E4F2546; &#xD;&#xA;&#x9;x-unix-mode=0644; name=test.odt" type="binary" encoding="Base64Encoded">...</mail:attachment>
>     <mail:flags>
>         <mail:flag type="seen"/>
>     </mail:flags>
> </mail:message>
>
> I want to clean up the addresses - separate the display name from the address so that the escaped < > delimiters can be removed
>  - and also clean up the mime-type (which is really the content-type).
>
> On 20 Aug 2014, at 10:41 pm, Adam Retter <ad...@ex...> wrote:
>
>> Hi Alister,
>>
>> I would stay away from having the user passing a function to handle
>> the content as you don't really gain anything from that approach here.
>>
>> Can I suggest studying the code of eXist's httpclient module to see
>> how to create XML, text or binary (base64) from external values and
>> return them as nodes.
>>
>> Could I also suggest adopting an existing standard for representing
>> email in XML if such a suitable one exists for your needs? Perhaps a
>> Google for such a thing, e.g.
>> http://petewarden.com/2008/10/15/an-xml-format-for-email/
>>
>> On 20 August 2014 13:31, Alister Pillow <gsp...@gm...> wrote:
>>> Hi all,
>>>
>>> I would appreciate some advice. I’m trying to write a mail:get-messages() function.
>>> mail:get-messages($folder, $messageNumbers)
>>>
>>> I was hoping to put the contents of multipart messages (e.g. text, html, other binary forms) into an xml result (either as text, xhtml or base64binary), but I’m finding it hard to do.
>>>
>>> The alternative is to follow the compression:unzip approach and get the user to supply a function to handle the content. I should be able to copy the AbstractExtractFunction.processCompressedEntry method.
>>> mail:get-messages($folder, $filterFunction, $storeFunction)
>>>
>>> Are there any downsides to that approach (other than it being harder to construct for the XQuery user)?
>>>
>>> ….
>>> This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:
>>> // for each BodyPart bp and bp.getContentType()
>>> builder.startElement(new QName("body", MailModule.NAMESPACE_URI, MailModule.PREFIX), null);
>>> builder.addAttribute(new QName("type", null, null), String.valueOf(contentType));
>>>
>>>
>>> if (contentType.contains("text/plain")) {  // if TEXT store as Characters
>>>    builder.characters(bp.getContent().toString());
>>> } else if (contentType.contains("text/html")) { // XHTML
>>>    builder.?ADD?( ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null));
>>> } else {   // otherwise store as base64Binary
>>>    add base64 data somehow
>>> }
>>> builder.endElement();
>>>
>>> Regards,
>>> Alister
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Exist-development mailing list
>>> Exi...@li...
>>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>
>>
>> --
>> Adam Retter
>>
>> eXist Developer
>> { United Kingdom }
>> ad...@ex...
>> irc://irc.freenode.net/existdb
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] mail message to xml

[Alister P. <gsp...@gm...>]

I’ve had a look at various options for representing email messages in XML, but there’s nothing appealing. They either try to capture every little detail or skimp. 
In the end, I chose to stay close to the form that is already used in the Mail Module - used by get-message-list-as-xml. The body content is stored as text and html if present, and attachments are available as base64 for storage. (I’ve successfully stored a PDF, ODT, PNG sent as attachments.)

mail:get-messages($folder-handle, $message-numbers)

There is a problem with mail:get-message-list-as-xml.
The message number is index based rather than coming from the folder:
builder.addAttribute( new QName( "number", null, null ), String.valueOf( i ) ); // where “i” is the loop index.

this should be:
builder.addAttribute(new QName("number", null, null), String.valueOf(message.getMessageNumber()));

This means you can’t use the message-list to choose a set of messages to retrieve.

I think this is a bug - easily fixed - but will it cause a problem for anyone if I change it?


Message example:
<mail:message xmlns:mail="http://exist-db.org/xquery/mail" number="5" contentType="multipart/mixed">
    <mail:subject>open office doc</mail:subject>
    <mail:sent>2014-08-27T12:55:43.000+09:30</mail:sent>
    <mail:received>2014-08-27T12:54:40.000+09:30</mail:received>
    <mail:from>Alister Pillow &lt;ali...@me...&gt;</mail:from>
    <mail:recipients>
        <mail:recipient type="to">in...@pe...</mail:recipient>
    </mail:recipients>
    <mail:text mime-type="text/plain; charset=windows-1252">Please find attached…
</mail:text>
    <mail:attachment filename="test.odt" mime-type="application/vnd.oasis.opendocument.text; x-mac-type=4E4F2546; &#xD;&#xA;&#x9;x-unix-mode=0644; name=test.odt" type="binary" encoding="Base64Encoded">...</mail:attachment>
    <mail:flags>
        <mail:flag type="seen"/>
    </mail:flags>
</mail:message>

I want to clean up the addresses - separate the display name from the address so that the escaped < > delimiters can be removed
 - and also clean up the mime-type (which is really the content-type).

On 20 Aug 2014, at 10:41 pm, Adam Retter <ad...@ex...> wrote:

> Hi Alister,
> 
> I would stay away from having the user passing a function to handle
> the content as you don't really gain anything from that approach here.
> 
> Can I suggest studying the code of eXist's httpclient module to see
> how to create XML, text or binary (base64) from external values and
> return them as nodes.
> 
> Could I also suggest adopting an existing standard for representing
> email in XML if such a suitable one exists for your needs? Perhaps a
> Google for such a thing, e.g.
> http://petewarden.com/2008/10/15/an-xml-format-for-email/
> 
> On 20 August 2014 13:31, Alister Pillow <gsp...@gm...> wrote:
>> Hi all,
>> 
>> I would appreciate some advice. I’m trying to write a mail:get-messages() function.
>> mail:get-messages($folder, $messageNumbers)
>> 
>> I was hoping to put the contents of multipart messages (e.g. text, html, other binary forms) into an xml result (either as text, xhtml or base64binary), but I’m finding it hard to do.
>> 
>> The alternative is to follow the compression:unzip approach and get the user to supply a function to handle the content. I should be able to copy the AbstractExtractFunction.processCompressedEntry method.
>> mail:get-messages($folder, $filterFunction, $storeFunction)
>> 
>> Are there any downsides to that approach (other than it being harder to construct for the XQuery user)?
>> 
>> ….
>> This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:
>> // for each BodyPart bp and bp.getContentType()
>> builder.startElement(new QName("body", MailModule.NAMESPACE_URI, MailModule.PREFIX), null);
>> builder.addAttribute(new QName("type", null, null), String.valueOf(contentType));
>> 
>> 
>> if (contentType.contains("text/plain")) {  // if TEXT store as Characters
>>    builder.characters(bp.getContent().toString());
>> } else if (contentType.contains("text/html")) { // XHTML
>>    builder.?ADD?( ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null));
>> } else {   // otherwise store as base64Binary
>>    add base64 data somehow
>> }
>> builder.endElement();
>> 
>> Regards,
>> Alister
>> 
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
> 
> 
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

Re: [Exist-development] mail message to xml

[Alister P. <gsp...@gm...>]

Thanks Adam & Wolfgang - good suggestions.

The DocumentBuilderReceiver wrapper worked correctly - exposing the awful underbelly of html with inline images. The HTTPClient module is exactly the example I was looking for.

Regarding the XML representation - I was simply going to add one or more mail:body elements (with @type) to the message element used in mail:get-message-list-as-xml. A switch to a different representation here might be confusing to users of the mail module unless I rewrite the get-message-list-as-xml function as well (and that’s probably not a good idea). However, I’ll spend a little more time looking around for mail-xml ideas - but nothing (other than Pete Warden’s work) has jumped out at me yet.


On 20 Aug 2014, at 10:41 pm, Adam Retter <ad...@ex...> wrote:

> Hi Alister,
> 
> I would stay away from having the user passing a function to handle
> the content as you don't really gain anything from that approach here.
> 
> Can I suggest studying the code of eXist's httpclient module to see
> how to create XML, text or binary (base64) from external values and
> return them as nodes.
> 
> Could I also suggest adopting an existing standard for representing
> email in XML if such a suitable one exists for your needs? Perhaps a
> Google for such a thing, e.g.
> http://petewarden.com/2008/10/15/an-xml-format-for-email/
> 
> On 20 August 2014 13:31, Alister Pillow <gsp...@gm...> wrote:
>> Hi all,
>> 
>> I would appreciate some advice. I’m trying to write a mail:get-messages() function.
>> mail:get-messages($folder, $messageNumbers)
>> 
>> I was hoping to put the contents of multipart messages (e.g. text, html, other binary forms) into an xml result (either as text, xhtml or base64binary), but I’m finding it hard to do.
>> 
>> The alternative is to follow the compression:unzip approach and get the user to supply a function to handle the content. I should be able to copy the AbstractExtractFunction.processCompressedEntry method.
>> mail:get-messages($folder, $filterFunction, $storeFunction)
>> 
>> Are there any downsides to that approach (other than it being harder to construct for the XQuery user)?
>> 
>> ….
>> This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:
>> // for each BodyPart bp and bp.getContentType()
>> builder.startElement(new QName("body", MailModule.NAMESPACE_URI, MailModule.PREFIX), null);
>> builder.addAttribute(new QName("type", null, null), String.valueOf(contentType));
>> 
>> 
>> if (contentType.contains("text/plain")) {  // if TEXT store as Characters
>>    builder.characters(bp.getContent().toString());
>> } else if (contentType.contains("text/html")) { // XHTML
>>    builder.?ADD?( ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null));
>> } else {   // otherwise store as base64Binary
>>    add base64 data somehow
>> }
>> builder.endElement();
>> 
>> Regards,
>> Alister
>> 
>> 
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
> 
> 
> 
> -- 
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb

Re: [Exist-development] mail message to xml

[Adam R. <ad...@ex...>]

Hi Alister,

I would stay away from having the user passing a function to handle
the content as you don't really gain anything from that approach here.

Can I suggest studying the code of eXist's httpclient module to see
how to create XML, text or binary (base64) from external values and
return them as nodes.

Could I also suggest adopting an existing standard for representing
email in XML if such a suitable one exists for your needs? Perhaps a
Google for such a thing, e.g.
http://petewarden.com/2008/10/15/an-xml-format-for-email/

On 20 August 2014 13:31, Alister Pillow <gsp...@gm...> wrote:
> Hi all,
>
> I would appreciate some advice. I’m trying to write a mail:get-messages() function.
> mail:get-messages($folder, $messageNumbers)
>
> I was hoping to put the contents of multipart messages (e.g. text, html, other binary forms) into an xml result (either as text, xhtml or base64binary), but I’m finding it hard to do.
>
> The alternative is to follow the compression:unzip approach and get the user to supply a function to handle the content. I should be able to copy the AbstractExtractFunction.processCompressedEntry method.
> mail:get-messages($folder, $filterFunction, $storeFunction)
>
> Are there any downsides to that approach (other than it being harder to construct for the XQuery user)?
>
> ….
> This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:
> // for each BodyPart bp and bp.getContentType()
> builder.startElement(new QName("body", MailModule.NAMESPACE_URI, MailModule.PREFIX), null);
> builder.addAttribute(new QName("type", null, null), String.valueOf(contentType));
>
>
> if (contentType.contains("text/plain")) {  // if TEXT store as Characters
>     builder.characters(bp.getContent().toString());
> } else if (contentType.contains("text/html")) { // XHTML
>     builder.?ADD?( ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null));
> } else {   // otherwise store as base64Binary
>     add base64 data somehow
> }
> builder.endElement();
>
> Regards,
> Alister
>
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb

Re: [Exist-development] mail message to xml

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

> This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:

It’s hard to say without trying it out myself, but I would suggest the following: wrap a DocumentBuilderReceiver around your builder:

DocumentBuilderReceiver receiver = new DocumentBuilderReceiver(builder);

When you call ModuleUtils.htmlToXHtml, keep the returned DocumentImpl:

DocumentImpl htmlDoc = ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null);

and stream it to the receiver:

ElementImpl rootElem = (ElementImpl)htmlDoc.getDocumentElement();
htmlDoc.copyTo(rootElem, receiver);

Hope this works.

Wolfgang

[Exist-development] mail message to xml

[Alister P. <gsp...@gm...>]

Hi all,

I would appreciate some advice. I’m trying to write a mail:get-messages() function.
mail:get-messages($folder, $messageNumbers)

I was hoping to put the contents of multipart messages (e.g. text, html, other binary forms) into an xml result (either as text, xhtml or base64binary), but I’m finding it hard to do. 

The alternative is to follow the compression:unzip approach and get the user to supply a function to handle the content. I should be able to copy the AbstractExtractFunction.processCompressedEntry method.
mail:get-messages($folder, $filterFunction, $storeFunction)

Are there any downsides to that approach (other than it being harder to construct for the XQuery user)?

….
This is what I wanted to do - but can’t find simple methods of adding those content types to the XML result:
// for each BodyPart bp and bp.getContentType()
builder.startElement(new QName("body", MailModule.NAMESPACE_URI, MailModule.PREFIX), null);
builder.addAttribute(new QName("type", null, null), String.valueOf(contentType));


if (contentType.contains("text/plain")) {  // if TEXT store as Characters
    builder.characters(bp.getContent().toString());
} else if (contentType.contains("text/html")) { // XHTML
    builder.?ADD?( ModuleUtils.htmlToXHtml(context, "alternative", new StreamSource(bp.getInputStream()), null, null));
} else {   // otherwise store as base64Binary
    add base64 data somehow
}
builder.endElement();

Regards,
Alister

Re: [Exist-development] build extensions?

[Dannes W. <da...@ex...>]

hi,

On Wed, Aug 20, 2014 at 3:43 AM, Alister Pillow <gsp...@gm...>
wrote:

> Is there a way to build extensions only - rather than building the whole
> project with ./build.sh
> I’m working on the mail module.


the first link on google
<https://www.google.nl/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=exist-db%20build%20exitensions>
 shows


   1. eXist-db Documentation - XQuery Extension Modules
   <http://exist-db.org/exist/apps/doc/extensions.xml>
   *exist*-*db*.org/*exist*/apps/doc/extensions.xml

   <https://www.google.nl/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#>
   -
      <http://webcache.googleusercontent.com/search?q=cache:l_Nag8bwGZwJ:exist-db.org/exist/apps/doc/extensions.xml+&cd=1&hl=en&ct=clnk&gl=nl>
      -
      <https://www.google.nl/search?espv=2&biw=1293&bih=783&q=related:exist-db.org/exist/apps/doc/extensions.xml+exist-db+build+extensions&tbo=1&sa=X&ei=TnP0U6rUG4H8ywP1xICoBA&ved=0CCcQHzAA>
   They may then be compiled in place using either
   $EXIST_HOME/build.sh extension-modules or
   %EXIST_HOME%\build.bat extension-modules depending on  ...
   ‎Introduction
   <http://exist-db.org/exist/apps/doc/extensions.xml#module_intro> - ‎Example
   Module <http://exist-db.org/exist/apps/doc/extensions.xml#module_example>
    - ‎Cache Module
   <http://exist-db.org/exist/apps/doc/extensions.xml#module_cache> -
‎Compression
   Module
   <http://exist-db.org/exist/apps/doc/extensions.xml#module_compression>

regards

Dannes

-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624

[Exist-development] htmlToXhtml and a MemTreeBuilder

[Alister P. <gsp...@gm...>]

Hi,
I’m trying to add HTML from a mail message to an xml document being constructed using the MemTreeBuilder.

builder.startElement(new QName("body", …. ), null);
if (contentType.contains("text/html")) {
   builder. add this as xml 
    ModuleUtils.htmlToXHtml(context, “alternative", bodyPart.getContent(), null, null)

Can’t quite see how to do that. 

Regards,
Alister.

[Exist-development] build extensions?

[Alister P. <gsp...@gm...>]

Hi 
Is there a way to build extensions only - rather than building the whole project with ./build.sh
I’m working on the mail module.

Thanks,
Alister.

Re: [Exist-development] zip:update

[Alister P. <gsp...@gm...>]

Hi Joe,
I will submit a pull request, but I’m concerned because my additions don’t match the spec. 
This zip:update function matches my own use-case - replacing one file in a zip, where the zip is stored in the database and the content is possibly in-memory. 


On 24 Jul 2014, at 11:02 am, Joe Wicentowski <jo...@gm...> wrote:

> Alister,
> 
> Great!  Have you considered submitting your work as a pull request?
> 
> Joe
> 
> Sent from my iPhone
> 
>> On Jul 23, 2014, at 6:29 PM, Alister Pillow <gsp...@gm...> wrote:
>> 
>> I’ve added a zip:update function to my clone of the expath zip module. (I desperately need this function in eXist 2.x - to replace a module I wrote for 1.2 and 1.4)
>> https://github.com/gspringtech/exist
>> 
>> (There’s also a minimal zip:entries function - not so useful considering what’s available in the compression: module.)
>> 
>> zip:update( $href as xs:anyURI, $paths as xs:string+, $binaries as xs:base64Binary+ ) as xs:base64Binary?
>> 
>> The function will replace existing content or add new content to a zip file. This is not the same as the specified zip:update-entries() - which would be difficult to use as well as hard to code.
>> 
>> I’ve chosen an href for the source file - so that it can be processed as a stream - but couldn’t quite figure out how to do the same for the binaries. In my use case, the updated content would be generated and not stored.
>> 
>> Example: 
>> 
>> xquery version “1.0";
>> let $odt := '/db/Job-Listing.odt'
>> let $content := '/db/new-content.xml'
>> let $binary-content := util:string-to-binary(util:serialize(doc($content),"method=xml"))
>> let $test-binary:= util:string-to-binary(util:serialize(<doc>Something else</doc>,"method=xml”))
>> 
>> let $updated := zip:update(xs:anyURI($odt),("content.xml","test/test.xml"), ($binary-content, $test-binary ))
>> 
>> return xmldb:store("/db","updated.odt",$updated)
>> 
>> 
>> I haven’t written zip:zip-file (which creates a new Zip file) because that functionality already exists in the compression module.
>> 
>> I guess that the way forward is to follow the new EXPath Archive spec.
>> 
>> Regards,
>> Alister.
>> 
>> 
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] zip:update

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

Alister,

Great!  Have you considered submitting your work as a pull request?

Joe

Sent from my iPhone

> On Jul 23, 2014, at 6:29 PM, Alister Pillow <gsp...@gm...> wrote:
> 
> I’ve added a zip:update function to my clone of the expath zip module. (I desperately need this function in eXist 2.x - to replace a module I wrote for 1.2 and 1.4)
> https://github.com/gspringtech/exist
> 
> (There’s also a minimal zip:entries function - not so useful considering what’s available in the compression: module.)
> 
> zip:update( $href as xs:anyURI, $paths as xs:string+, $binaries as xs:base64Binary+ ) as xs:base64Binary?
> 
> The function will replace existing content or add new content to a zip file. This is not the same as the specified zip:update-entries() - which would be difficult to use as well as hard to code.
> 
> I’ve chosen an href for the source file - so that it can be processed as a stream - but couldn’t quite figure out how to do the same for the binaries. In my use case, the updated content would be generated and not stored.
> 
> Example: 
> 
> xquery version “1.0";
> let $odt := '/db/Job-Listing.odt'
> let $content := '/db/new-content.xml'
> let $binary-content := util:string-to-binary(util:serialize(doc($content),"method=xml"))
> let $test-binary:= util:string-to-binary(util:serialize(<doc>Something else</doc>,"method=xml”))
> 
> let $updated := zip:update(xs:anyURI($odt),("content.xml","test/test.xml"), ($binary-content, $test-binary ))
> 
> return xmldb:store("/db","updated.odt",$updated)
> 
> 
> I haven’t written zip:zip-file (which creates a new Zip file) because that functionality already exists in the compression module.
> 
> I guess that the way forward is to follow the new EXPath Archive spec.
> 
> Regards,
> Alister.
> 
> 
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

[Exist-development] zip:update

[Alister P. <gsp...@gm...>]

I’ve added a zip:update function to my clone of the expath zip module. (I desperately need this function in eXist 2.x - to replace a module I wrote for 1.2 and 1.4)
https://github.com/gspringtech/exist

(There’s also a minimal zip:entries function - not so useful considering what’s available in the compression: module.)

zip:update( $href as xs:anyURI, $paths as xs:string+, $binaries as xs:base64Binary+ ) as xs:base64Binary?

The function will replace existing content or add new content to a zip file. This is not the same as the specified zip:update-entries() - which would be difficult to use as well as hard to code.

I’ve chosen an href for the source file - so that it can be processed as a stream - but couldn’t quite figure out how to do the same for the binaries. In my use case, the updated content would be generated and not stored.

Example: 

xquery version “1.0";
let $odt := '/db/Job-Listing.odt'
let $content := '/db/new-content.xml'
let $binary-content := util:string-to-binary(util:serialize(doc($content),"method=xml"))
let $test-binary:= util:string-to-binary(util:serialize(<doc>Something else</doc>,"method=xml”))

let $updated := zip:update(xs:anyURI($odt),("content.xml","test/test.xml"), ($binary-content, $test-binary ))

return xmldb:store("/db","updated.odt",$updated)


I haven’t written zip:zip-file (which creates a new Zip file) because that functionality already exists in the compression module.

I guess that the way forward is to follow the new EXPath Archive spec.

Regards,
Alister.

[Exist-development] zip:update

[Alister P. <gsp...@gm...>]

I’ve added a zip:update function to my clone of the expath zip module. (I desperately need this function in eXist 2.x - to replace a module I wrote for 1.2 and 1.4)

(There’s also a minimal zip:entries function - not so useful considering what’s available in the compression: module.)

zip:update( $href as xs:anyURI, $paths as xs:string+, $binaries as xs:base64Binary+ ) as xs:base64Binary?

The function will replace existing content or add new content to a zip file. This is not the same as the specified zip:update-entries() - which would be difficult to use as well as hard to code.

I’ve chosen an href for the source file - so that it can be processed as a stream - but couldn’t quite figure out how to do the same for the binaries. In my use case, the updated content would be generated and not stored.

Example: 

xquery version “1.0";
let $odt := '/db/Job-Listing.odt'
let $content := '/db/new-content.xml'
let $binary-content := util:string-to-binary(util:serialize(doc($content),"method=xml"))
let $test-binary:= util:string-to-binary(util:serialize(<doc>Something else</doc>,"method=xml”))

let $updated := zip:update(xs:anyURI($odt),("content.xml","test/test.xml"), ($binary-content, $test-binary ))

return xmldb:store("/db","updated.odt",$updated)


I haven’t written zip:zip-file (which creates a new Zip file) because that functionality already exists in the compression module.

I guess that the way forward is to follow the new EXPath Archive spec.

Regards,
Alister.

Re: [Exist-development] Possible very serious concurrency issue with XQueryURLRewrite

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

Ok, so I have finally had a moment to get back to this issue. I took some
time and was able to create a test that reproduced this very easily
(Basically a very specific stress test).

>From that I believe that I have found the issue.

URLRewrite.copyFrom(URLRewrite other) is not safe, if you look at the
method:

protected void copyFrom(URLRewrite other) {
        this.headers = other.headers;
        this.parameters = other.parameters;
        this.attributes = other.attributes;
    }

You can see it does not copy the contents of  the mappings for params,
attributes etc but instead maintains a reference to the existing
objects. This means that for static rewrites in high concurrency data will
absolutely get overwritten.

This method is only used in one place (XQueryURLRewrite.doRewrite()).

I believe that if this can be fixed it will correct this very serious
issue. That being said, I am not sure why it was designed this way to begin
with so I would appreciate some input from the team.

Thanks!




On Sat, Mar 29, 2014 at 7:33 PM, Casey Jordan <cas...@jo...>
wrote:

> I think I have found what I believe to be a very serious concurrency issue
> in the XQueryURLRewrite code (eXist develop). This has been very hard to
> track down so please bare with me as I describe what I have seen so far.
>
> I was noticing that every so often when there were several simultaneous
> requests to my application the result from one request would return the
> wrong result. Specifically, it would return the same result as another
> request that happened at a similar time.
>
> I started to debug this and found that the mixup happens with a parameter
> (via <add-parameter/>) somewhere in the rewrite code. I tried to create a
> reproducible test for this, but I can only seem to recreate it every so
> often and only with my production code, which is obviously much more
> complex than the simple tests cases I was creating.
>
> So I started doing a code review on the rewrite servlet, but after a few
> hours I decided it might be a good idea to ask the community.
>
> My controller is located at /api/get/controller.xql and  the xquery it
> gets forwarded to is located at /api/get/document.xql
>
> My request calls look like this:
> http://localhost:8080/api/get/[document-uri]?view=web
>
> For instance:
> http://localhost:8080/api/get/db/documents/langref/preface.dita?view=web
>
> My controllers role is to parse out the document-uri from this string and
> turn it into a request param forwarded to document.xql. This is essentially
> what my controller.xql looks like.
>
> let $path := replace(replace(substring-after(request:get-url(), 'get'),
> "//", "/"), ' ', '%20')
>
> let $out := util:log-system-out(concat("RW: ", $path))
>
> <dispatch xmlns="http://exist.sourceforge.net/NS/exist">
>
>  <forward url="/api/get/document.xql" >
>
>   <add-parameter name="path" value="{$path}"/>
>
>  </forward>
>
>  </dispatch>
>
> and in document.xql I get the param I set like so:
>
> let $path := request:get-parameter('path', '')
>
> let $out := util:log-system-out(concat("Compiling: ",$path))
>
> ....
>
> (Note the bolded debug messages in the code above as I will reference them
> later)
>
> Now I have noticed that every so often, the "path" parameter which comes
> into the request gets replaced with a different one from another request.
>
> I know this because I can look at the jetty request logs and I can see a
> request come into the server, then I can see the debug output in my
> controller, that shows that $path is parsed correctly, but then in my
> document.xql I never see this path get printed in the debug statement.
> Instead I see two debug statements with the "path" for a different request.
>
> Consider the following debug output:
>
> (Line: 18 /api/get/controller.xql) RW:
> /db/documents/archSpec/dita_technicalContent_InformationTypes.dita
>
> (Line: 18 /api/get/controller.xql) RW:
> /db/documents/archSpec/dita_concept_topic.dita
>
> (Line: 18 /api/get/controller.xql) RW:
> /db/documents/archSpec/dita_generic_task_topic.dita
>
> (Line: 18 /api/get/controller.xql) RW:
> /db/documents/archSpec/dita_task_topic.dita
>
> (Line: 18 /api/get/controller.xql) RW:
> /db/documents/archSpec/dita_reference_topic.dita
>
> (Line: 40 /api/get/document.xql) Compiling:
> /db/documents/archSpec/dita_task_topic.dita
>
> (Line: 40 /api/get/document.xql) Compiling:
> /db/documents/archSpec/dita_technicalContent_InformationTypes.dita
>
> (Line: 40 /api/get/document.xql) Compiling:
> /db/documents/archSpec/dita_task_topic.dita
>
> You can see here that the call for dita_generic_task_topic.dita comes
> into the controller, but never makes it into document.xql. Instead, there
> are two calls where dita_task_topic.dita is the "path" param.
>
> So this leads me to believe that there is a very serious issue where some
> data is being shared between request threads. My code review lead me to
> believe this is related  to the RewriteConfig because it keeps a set of
> mappings in memory, and while the methods to get these mappings are
> synchronized, it seems that they can return a URLRewrite instance (In this
> case PathForward) that is shared between multiple threads, and thus when
> the controller result is parsed can overwrite parameters stored in the
> URLRewrite instance.
>
> I am hoping that someone who is more familiar with this code can take a
> look for me. Obviously if params are indeed being overwritten then this
> could inadvertently cause all kinds of problems in applications that may
> delete or alter data.
>
> Thanks!
>
>
> --
> --
> Casey Jordan
> easyDITA a product of Jorsek LLC
> "CaseyDJordan" on LinkedIn, Twitter & Facebook
> (585) 348 7399
> easydita.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.
>



-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.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] line endings

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

Hi,

Is the repo set up to convert file endings to LF on checkout? I don't see any .gitattributes file ….

<https://help.github.com/articles/dealing-with-line-endings>

Jens

Re: [Exist-development] Java7

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

Sorry for my obtuseness. 

I found out, in a clearer moment, that I can open the standard oXygen under Java 7 with

export JAVA_HOME=`/usr/libexec/java_home -v 1.7`
cd /Applications/oxygen/
./oxygenMac.sh

as well, and eXist-db can be accessed again. I guess it then does not use the bundled JVM? However, double-clicking the version which bundles Java 7 is nicer.

Thank everybody for their patience!

Jens

On 1 May 2014 at 13:19:29, Joe Wicentowski (jo...@gm...) wrote:

Ah, I forgot: to get this version, you need to read the fine print at  
http://www.oxygenxml.com/download_oxygenxml_editor.html:  

"If you have OS X 10.7, 10.8 or 10.9 you can use the OS X 10.7 and  
later download which bundles Java SE 7. In this case Java is no longer  
required to be installed separately."  

The direct download link to this version in the fine print is  
http://www.oxygenxml.com/InstData/Editor/MacOSX/VM/oxygen.tar.gz (145  
MB) as opposed to  
http://www.oxygenxml.com/InstData/Editor/MacOSX/oxygen.zip (118 MB).  

Joe  

On Thu, May 1, 2014 at 7:13 AM, Joe Wicentowski <jo...@gm...> wrote:  
> Hi Jens,  
>  
> This might be a question for the oXygen forums or support line, but  
> oXygen 15.2 bundles Java 7 for Mac OS X 10.7+: see  
> http://www.oxygenxml.com/forum/topic10185.html and  
> http://www.oxygenxml.com/whatisnew15.2.html (under "Bundled Java 7 JRE  
> in the Mac OS X Installation Kit").  
>  
> Joe  
>  
> On Thu, May 1, 2014 at 6:57 AM, Jens Østergaard Petersen  
> <oe...@gm...> wrote:  
>> Hi Joe and Dannes,  
>>  
>> Yes, I did restart, but Dannes is right: my oXygen is running on the Mac OS  
>> default java.runtime.version 1.6.0_65-b14-462-11M4609 (which I believe you  
>> are not supposed to fiddle with).  
>>  
>> Perhaps it is because I am exceptionally jet-lagged, but I do not find  
>> instructions about how to set oXygen to run on Java 7 on Mac OS X. The old  
>> instructions at <http://www.oxygenxml.com/forum/topic6996.html> do not help,  
>> since I don't see how "to move Java 7 at the top of the list in Java  
>> Preferences" - that would be the Java Control Panel, I guess, but it only  
>> knows of Java 7.  
>>  
>> Jens  
>>  
>> On 1 May 2014 at 12:23:40, Joe Wicentowski (jo...@gm...) wrote:  
>>  
>> And did you restart oxygen if you updated the jars at an existing data  
>> source?  
>>  
>> Sent from my iPhone  
>>  
>> On May 1, 2014, at 5:32 AM, Dmitriy Shabanov <sha...@gm...> wrote:  
>>  
>> Did you update eXist's jar at oXygen?  
>>  
>> On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...>  
>> wrote:  
>>>  
>>> Hi,  
>>>  
>>> Does this mean that one cannot access eXist-db from oXygen?  
>>>  
>>> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to:  
>>> java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException :  
>>> Unsupported major.minor version 51.0  
>>>  
>>> is the error I get.  
>>  
>>  
>>  
>> --  
>> Dmitriy Shabanov  
>>  
>> ------------------------------------------------------------------------------  
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE  
>> Instantly run your Selenium tests across 300+ browser/OS combos. Get  
>> unparalleled scalability from the best Selenium testing platform available.  
>> Simple to use. Nothing to install. Get started now for free."  
>> http://p.sf.net/sfu/SauceLabs  
>>  
>> _______________________________________________  
>> Exist-development mailing list  
>> Exi...@li...  
>> https://lists.sourceforge.net/lists/listinfo/exist-development  

Re: [Exist-development] Java7

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

Ah, I forgot: to get this version, you need to read the fine print at
http://www.oxygenxml.com/download_oxygenxml_editor.html:

"If you have OS X 10.7, 10.8 or 10.9 you can use the OS X 10.7 and
later download which bundles Java SE 7. In this case Java is no longer
required to be installed separately."

The direct download link to this version in the fine print is
http://www.oxygenxml.com/InstData/Editor/MacOSX/VM/oxygen.tar.gz (145
MB) as opposed to
http://www.oxygenxml.com/InstData/Editor/MacOSX/oxygen.zip (118 MB).

Joe

On Thu, May 1, 2014 at 7:13 AM, Joe Wicentowski <jo...@gm...> wrote:
> Hi Jens,
>
> This might be a question for the oXygen forums or support line, but
> oXygen 15.2 bundles Java 7 for Mac OS X 10.7+: see
> http://www.oxygenxml.com/forum/topic10185.html and
> http://www.oxygenxml.com/whatisnew15.2.html (under "Bundled Java 7 JRE
> in the Mac OS X Installation Kit").
>
> Joe
>
> On Thu, May 1, 2014 at 6:57 AM, Jens Østergaard Petersen
> <oe...@gm...> wrote:
>> Hi Joe and Dannes,
>>
>> Yes, I did restart, but Dannes is right: my oXygen is running on the Mac OS
>> default java.runtime.version 1.6.0_65-b14-462-11M4609 (which I believe you
>> are not supposed to fiddle with).
>>
>> Perhaps it is because I am exceptionally jet-lagged, but I do not find
>> instructions about how to set oXygen to run on Java 7 on Mac OS X. The old
>> instructions at <http://www.oxygenxml.com/forum/topic6996.html> do not help,
>> since I don't see how "to move Java 7 at the top of the list in Java
>> Preferences" - that would be the Java Control Panel, I guess, but it only
>> knows of Java 7.
>>
>> Jens
>>
>> On 1 May 2014 at 12:23:40, Joe Wicentowski (jo...@gm...) wrote:
>>
>> And did you restart oxygen if you updated the jars at an existing data
>> source?
>>
>> Sent from my iPhone
>>
>> On May 1, 2014, at 5:32 AM, Dmitriy Shabanov <sha...@gm...> wrote:
>>
>> Did you update eXist's jar at oXygen?
>>
>> On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...>
>> wrote:
>>>
>>> Hi,
>>>
>>> Does this mean that one cannot access eXist-db from oXygen?
>>>
>>> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to:
>>> java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException :
>>> Unsupported major.minor version 51.0
>>>
>>> is the error I get.
>>
>>
>>
>> --
>> Dmitriy Shabanov
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
>> unparalleled scalability from the best Selenium testing platform available.
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>>
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Java7

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

Hi Jens,

This might be a question for the oXygen forums or support line, but
oXygen 15.2 bundles Java 7 for Mac OS X 10.7+: see
http://www.oxygenxml.com/forum/topic10185.html and
http://www.oxygenxml.com/whatisnew15.2.html (under "Bundled Java 7 JRE
in the Mac OS X Installation Kit").

Joe

On Thu, May 1, 2014 at 6:57 AM, Jens Østergaard Petersen
<oe...@gm...> wrote:
> Hi Joe and Dannes,
>
> Yes, I did restart, but Dannes is right: my oXygen is running on the Mac OS
> default java.runtime.version 1.6.0_65-b14-462-11M4609 (which I believe you
> are not supposed to fiddle with).
>
> Perhaps it is because I am exceptionally jet-lagged, but I do not find
> instructions about how to set oXygen to run on Java 7 on Mac OS X. The old
> instructions at <http://www.oxygenxml.com/forum/topic6996.html> do not help,
> since I don't see how "to move Java 7 at the top of the list in Java
> Preferences" - that would be the Java Control Panel, I guess, but it only
> knows of Java 7.
>
> Jens
>
> On 1 May 2014 at 12:23:40, Joe Wicentowski (jo...@gm...) wrote:
>
> And did you restart oxygen if you updated the jars at an existing data
> source?
>
> Sent from my iPhone
>
> On May 1, 2014, at 5:32 AM, Dmitriy Shabanov <sha...@gm...> wrote:
>
> Did you update eXist's jar at oXygen?
>
> On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...>
> wrote:
>>
>> Hi,
>>
>> Does this mean that one cannot access eXist-db from oXygen?
>>
>> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to:
>> java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException :
>> Unsupported major.minor version 51.0
>>
>> is the error I get.
>
>
>
> --
> Dmitriy Shabanov
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Java7

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

Hi Joe and Dannes,

Yes, I did restart, but Dannes is right: my oXygen is running on the Mac OS default java.runtime.version 1.6.0_65-b14-462-11M4609 (which I believe you are not supposed to fiddle with).

Perhaps it is because I am exceptionally jet-lagged, but I do not find instructions about how to set oXygen to run on Java 7 on Mac OS X. The old instructions at <http://www.oxygenxml.com/forum/topic6996.html> do not help, since I don't see how "to move Java 7 at the top of the list in Java Preferences" - that would be the Java Control Panel, I guess, but it only knows of Java 7.

Jens

On 1 May 2014 at 12:23:40, Joe Wicentowski (jo...@gm...) wrote:

And did you restart oxygen if you updated the jars at an existing data source?

Sent from my iPhone

On May 1, 2014, at 5:32 AM, Dmitriy Shabanov <sha...@gm...> wrote:

Did you update eXist's jar at oXygen?

On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...> wrote:
Hi,

Does this mean that one cannot access eXist-db from oXygen?

Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to: java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException : Unsupported major.minor version 51.0

is the error I get.


--
Dmitriy Shabanov
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Exist-development mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] Java7

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

And did you restart oxygen if you updated the jars at an existing data source?

Sent from my iPhone

> On May 1, 2014, at 5:32 AM, Dmitriy Shabanov <sha...@gm...> wrote:
> 
> Did you update eXist's jar at oXygen?
> 
>> On Thu, May 1, 2014 at 1:29 PM, Jens Østergaard Petersen <oe...@gm...> wrote:
>> Hi,
>> 
>> Does this mean that one cannot access eXist-db from oXygen?
>> 
>> Could not instantiate: ro.sync.db.nxd.exist.ExistSession due to: java.lang.UnsupportedClassVersionError: org/exist/xquery/XPathException : Unsupported major.minor version 51.0
>> 
>> is the error I get.
> 
> 
> -- 
> Dmitriy Shabanov
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development