exist-development — eXist Developer's List

Re: [Exist-development] logging create and delete events for Server-Sent Events

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

Hi Dmitriy,
I thought that either Node.js or Clojure would be good for an SSE server - keep it away from eXist-db. 

Either of those should be able to provide a socket for Log4J (but if that’s too hard, I’ll fall back to a text log).


> On 19 May 2015, at 4:48 pm, Dmitriy Shabanov <sha...@gm...> wrote:
> 
> Are you going to implement this in java?
> 
> On Mon, May 18, 2015 at 8:25 PM, Alister Pillow <gsp...@gm... <mailto:gsp...@gm...>> wrote:
> Hi,
> 
> Has anyone generated Server-Sent events from eXist? (Regardless of event source.) In particular, I want to record Create and Delete events - possibly updates. This would apply to all resources - not just XML.
> 
> I want to avoid triggers if possible - because I’m already using them in different places and I want this to be a global service for the /db.
> 
> It seems that the simplest approach might be to use Log4J to write to a log file - or a socket.
> 
> Is there already such a log message (I can’t see anything in debug mode) - where might be the best place to add such a log message?
> 
> Thanks,
> Alister.
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y>
> _______________________________________________
> Exist-development mailing list
> Exi...@li... <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-development <https://lists.sourceforge.net/lists/listinfo/exist-development>
> 
> 
> 
> -- 
> Dmitriy Shabanov

Re: [Exist-development] logging create and delete events for Server-Sent Events

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

Are you going to implement this in java?

On Mon, May 18, 2015 at 8:25 PM, Alister Pillow <gsp...@gm...>
wrote:

> Hi,
>
> Has anyone generated Server-Sent events from eXist? (Regardless of event
> source.) In particular, I want to record Create and Delete events -
> possibly updates. This would apply to all resources - not just XML.
>
> I want to avoid triggers if possible - because I’m already using them in
> different places and I want this to be a global service for the /db.
>
> It seems that the simplest approach might be to use Log4J to write to a
> log file - or a socket.
>
> Is there already such a log message (I can’t see anything in debug mode) -
> where might be the best place to add such a log message?
>
> Thanks,
> Alister.
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Dmitriy Shabanov

[Exist-development] logging create and delete events for Server-Sent Events

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

Hi,

Has anyone generated Server-Sent events from eXist? (Regardless of event source.) In particular, I want to record Create and Delete events - possibly updates. This would apply to all resources - not just XML.

I want to avoid triggers if possible - because I’m already using them in different places and I want this to be a global service for the /db.

It seems that the simplest approach might be to use Log4J to write to a log file - or a socket.

Is there already such a log message (I can’t see anything in debug mode) - where might be the best place to add such a log message?

Thanks,
Alister.

Re: [Exist-development] The syntax highlighting in oXygen 17 fails with eXist-db Update Extension

[George B. <ge...@ox...>]

Hi Loren,

As Wolfgang mentioned, the XQuery update in eXist is different from the 
W3C XQuery Update syntax and oXygen supports the later. If version 16 
worked for you for the eXist specific syntax, that was by accident, 
probably on a specific sample, not by design.

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 13/05/15 18:47, Joe Wicentowski wrote:
> In that case, I'd suggest that you report it to su...@ox...
> <mailto:su...@ox...>.
>
> On Wed, May 13, 2015 at 11:07 AM, Loren Cahlander
> <lor...@gm... <mailto:lor...@gm...>> wrote:
>
>     It was handling it until the release of 17
>
>     Sent from my iPhone
>
>     On May 13, 2015, at 10:53 AM, Joe Wicentowski <jo...@gm...
>     <mailto:jo...@gm...>> wrote:
>
>     You mean oXygen's highlighting of eXist's XQuery Update syntax?
>     Yes, that will be true as long as eXist doesn't match the spec.  I
>     wouldn't expect oXygen to add special handling for eXist, though I
>     certainly wouldn't object to it!
>
>     On Wed, May 13, 2015 at 10:33 AM, Loren Cahlander
>     <lor...@gm... <mailto:lor...@gm...>> wrote:
>
>         I thought so.  The syntax highlighting for XQuery update in
>         oXygen 17 is broken.
>
>
>
>         Sent from my iPad
>
>         On May 13, 2015, at 9:53 AM, wol...@gm...
>         <mailto:wol...@gm...> wrote:
>
>>>         Does eXist-db 2.2 support the XQuery 3.0 update syntax?
>>>         Http://w3.org/TR/xquery-update-30
>>
>>         No, the xquery update features in eXist differ not only
>>         syntactically, but also conceptually from the W3C
>>         specification, which was published quite some time after eXist
>>         introduced the feature. We did not try to align the syntax as
>>         that would be confusing, but intentionally left it non-standard.
>>
>>         Wolfgang
>
>         ------------------------------------------------------------------------------
>         One dashboard for servers and applications across
>         Physical-Virtual-Cloud
>         Widest out-of-the-box monitoring support with 50+ applications
>         Performance metrics, stats and reports that give you Actionable
>         Insights
>         Deep dive visibility with transaction tracing using APM Insight.
>         http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>         _______________________________________________
>         Exist-development mailing list
>         Exi...@li...
>         <mailto:Exi...@li...>
>         https://lists.sourceforge.net/lists/listinfo/exist-development
>
>
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>

Re: [Exist-development] The syntax highlighting in oXygen 17 fails with eXist-db Update Extension

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

In that case, I'd suggest that you report it to su...@ox....

On Wed, May 13, 2015 at 11:07 AM, Loren Cahlander <lor...@gm...
> wrote:

> It was handling it until the release of 17
>
> Sent from my iPhone
>
> On May 13, 2015, at 10:53 AM, Joe Wicentowski <jo...@gm...> wrote:
>
> You mean oXygen's highlighting of eXist's XQuery Update syntax?  Yes, that
> will be true as long as eXist doesn't match the spec.  I wouldn't expect
> oXygen to add special handling for eXist, though I certainly wouldn't
> object to it!
>
> On Wed, May 13, 2015 at 10:33 AM, Loren Cahlander <
> lor...@gm...> wrote:
>
>> I thought so.  The syntax highlighting for XQuery update in oXygen 17 is
>> broken.
>>
>>
>>
>> Sent from my iPad
>>
>> On May 13, 2015, at 9:53 AM, wol...@gm... wrote:
>>
>> Does eXist-db 2.2 support the XQuery 3.0 update syntax?
>> Http://w3.org/TR/xquery-update-30
>>
>>
>> No, the xquery update features in eXist differ not only syntactically,
>> but also conceptually from the W3C specification, which was published quite
>> some time after eXist introduced the feature. We did not try to align the
>> syntax as that would be confusing, but intentionally left it non-standard.
>>
>> Wolfgang
>>
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>
>

Re: [Exist-development] The syntax highlighting in oXygen 17 fails with eXist-db Update Extension

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

It was handling it until the release of 17

Sent from my iPhone

On May 13, 2015, at 10:53 AM, Joe Wicentowski <jo...@gm...> wrote:

You mean oXygen's highlighting of eXist's XQuery Update syntax?  Yes, that will be true as long as eXist doesn't match the spec.  I wouldn't expect oXygen to add special handling for eXist, though I certainly wouldn't object to it!

> On Wed, May 13, 2015 at 10:33 AM, Loren Cahlander <lor...@gm...> wrote:
> I thought so.  The syntax highlighting for XQuery update in oXygen 17 is broken.
> 
> 
> 
> Sent from my iPad
> 
> On May 13, 2015, at 9:53 AM, wol...@gm... wrote:
> 
>>> Does eXist-db 2.2 support the XQuery 3.0 update syntax? Http://w3.org/TR/xquery-update-30
>> 
>> No, the xquery update features in eXist differ not only syntactically, but also conceptually from the W3C specification, which was published quite some time after eXist introduced the feature. We did not try to align the syntax as that would be confusing, but intentionally left it non-standard.
>> 
>> Wolfgang
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development

Re: [Exist-development] The syntax highlighting in oXygen 17 fails with eXist-db Update Extension

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

You mean oXygen's highlighting of eXist's XQuery Update syntax?  Yes, that
will be true as long as eXist doesn't match the spec.  I wouldn't expect
oXygen to add special handling for eXist, though I certainly wouldn't
object to it!

On Wed, May 13, 2015 at 10:33 AM, Loren Cahlander <lor...@gm...
> wrote:

> I thought so.  The syntax highlighting for XQuery update in oXygen 17 is
> broken.
>
>
>
> Sent from my iPad
>
> On May 13, 2015, at 9:53 AM, wol...@gm... wrote:
>
> Does eXist-db 2.2 support the XQuery 3.0 update syntax?
> Http://w3.org/TR/xquery-update-30
>
>
> No, the xquery update features in eXist differ not only syntactically, but
> also conceptually from the W3C specification, which was published quite
> some time after eXist introduced the feature. We did not try to align the
> syntax as that would be confusing, but intentionally left it non-standard.
>
> Wolfgang
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

Re: [Exist-development] The syntax highlighting in oXygen 17 fails with eXist-db Update Extension

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

I thought so.  The syntax highlighting for XQuery update in oXygen 17 is broken.



Sent from my iPad

> On May 13, 2015, at 9:53 AM, wol...@gm... wrote:
> 
>> Does eXist-db 2.2 support the XQuery 3.0 update syntax? Http://w3.org/TR/xquery-update-30
> 
> No, the xquery update features in eXist differ not only syntactically, but also conceptually from the W3C specification, which was published quite some time after eXist introduced the feature. We did not try to align the syntax as that would be confusing, but intentionally left it non-standard.
> 
> Wolfgang

Re: [Exist-development] The syntax highlighting fails with eXist-db Update Extension

[<wol...@gm...>]

> Does eXist-db 2.2 support the XQuery 3.0 update syntax? Http://w3.org/TR/xquery-update-30 <http://w3.org/TR/xquery-update-30>
No, the xquery update features in eXist differ not only syntactically, but also conceptually from the W3C specification, which was published quite some time after eXist introduced the feature. We did not try to align the syntax as that would be confusing, but intentionally left it non-standard.

Wolfgang

[Exist-development] Fwd: The syntax highlighting fails with eXist-db Update Extension

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

Does eXist-db 2.2 support the XQuery 3.0 update syntax? Http://w3.org/TR/xquery-update-30



Sent from my iPad

Begin forwarded message:

> From: Oxygen XML Support <su...@ox...>
> Date: May 8, 2015 at 10:52:28 AM EDT
> To: lor...@gm...
> Subject: The syntax highlighting fails with eXist-db Update Extension
> 
> Hello,
> 
> Thank you for contacting us.
> 
> The syntax highlight covers only the syntax for the W3C's XQuery 1.0, XQuery Update Facility 1.0, XQuery 3.0, XQuery Update Facility 3.0 standards.
> 
> The difference between your sample and the XQuery Update standard syntax is as follows:
>> update insert element { 'dataset' } { $dataset } into $datasets
> insert node element { 'dataset' } { $dataset } into $datasets
> 
> I will add an improvement request to update our grammar for recognizing a such extension.
> Let us know if you need additional assistance.
> 
> Regards,
> Alin
> 
> 
> -- 
> Alin Balasa
> <oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
> 
> 

Re: [Exist-development] 99 issues, but a release ain't one!

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

I don;t like it.... the clients feel just sooooo old; it is another app to install and start, and is lurking batteries; and... I can;t access it from behind a corporate firewall.

but these are just my 2 cts

> On 17 Mar 2015, at 20:33 , Adam Retter <ad...@ex...> wrote:
> 
> Yay.. yet another thing :-( Was there anything particularly wrong with
> IRC? i.e. why are we replacing IRC?

Re: [Exist-development] 99 issues, but a release ain't one!

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

> A related note: I often look back to the old times when IRC was our only communication channel. Live was so much simpler ;-) Unfortunately all devs (except Adam) have abandoned IRC, so I rarely start the IRC client these days. Lars, Tobi, Joern and me have thus been searching for a solution which would replace IRC as well as our private jabber channels. The best match so far seems to be hipchat, mainly because it allows unlimited access for anyone as well as private chats, and has a searchable history.
>

Yay.. yet another thing :-( Was there anything particularly wrong with
IRC? i.e. why are we replacing IRC?



-- 
Adam Retter

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

Re: [Exist-development] 99 issues, but a release ain't one!

[<wol...@gm...>]

Hi,

nice idea. I agree it would be good to have a joint effort on bug fixing and stabilising (!) develop to prepare the ground for a new release. There have been some major changes which should be tested by those running on develop (we always need some time to update our systems). I also have a few show stoppers and killer bugs on my list.

So for me, any weekend except the next and those between April 17 and 27 will work.

A related note: I often look back to the old times when IRC was our only communication channel. Live was so much simpler ;-) Unfortunately all devs (except Adam) have abandoned IRC, so I rarely start the IRC client these days. Lars, Tobi, Joern and me have thus been searching for a solution which would replace IRC as well as our private jabber channels. The best match so far seems to be hipchat, mainly because it allows unlimited access for anyone as well as private chats, and has a searchable history.

I would thus like to invite all developers/users to give it a try:

https://www.hipchat.com/gEBQ3SNfp

You may enter the chat without having an account. If it works out for all developers, we’ll migrate from IRC.

Wolfgang

Re: [Exist-development] 99 issues, but a release ain't one!

[Leif-Jöran O. <lj...@ex...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I agree, a weekend would be good.

Cheers,
Leif-Jöran

Den 2015-03-17 12:01, Dmitriy Shabanov skrev:
> Good idea, any weekends are good for me, just need to know it
> upfront.
> 
> On Tue, Mar 17, 2015 at 12:21 PM, Adam Retter <ad...@ex...>
> wrote:
>> I am concerned that when I last looked, we had 99 open issues on 
>> GitHub. I think we are getting to that horrible situation that we
>> also had on SF, which is that we have many issues that are never
>> addressed or fixed. Apart from Dannes I don't see a lot of people
>> consistently responding to issues. This is not good as many
>> people look at this figure as part of an indicator to the health
>> of a project.
>> 
>> I was thinking that perhaps we could have an issue hack-weekend,
>> where we all agree a weekend and then explicitly spend the
>> weekend working together to attack issues and trying to
>> fix/answer as many as possible to reduce the backlog. This could
>> be done via Skype (or other) from home/office without actually
>> meeting.
>> 
>> Would anyone else be willing to set aside a weekend for this? If
>> so, could you give me a vague idea of which weekends you might
>> have available in the next 3 months.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iD8DBQFVCD+ShcIn5aVXOPIRAumwAJ9Y74LxIFYhSqIUnCgkjZxOqcKaIACeN00L
qcXToF4OTEky4rE8RUQfWCc=
=m42i
-----END PGP SIGNATURE-----

Re: [Exist-development] 99 issues, but a release ain't one!

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

Good idea, any weekends are good for me, just need to know it upfront.

On Tue, Mar 17, 2015 at 12:21 PM, Adam Retter <ad...@ex...> wrote:
> I am concerned that when I last looked, we had 99 open issues on
> GitHub. I think we are getting to that horrible situation that we also
> had on SF, which is that we have many issues that are never addressed
> or fixed. Apart from Dannes I don't see a lot of people consistently
> responding to issues. This is not good as many people look at this
> figure as part of an indicator to the health of a project.
>
> I was thinking that perhaps we could have an issue hack-weekend, where
> we all agree a weekend and then explicitly spend the weekend working
> together to attack issues and trying to fix/answer as many as possible
> to reduce the backlog. This could be done via Skype (or other) from
> home/office without actually meeting.
>
> Would anyone else be willing to set aside a weekend for this? If so,
> could you give me a vague idea of which weekends you might have
> available in the next 3 months.

-- 
Dmitriy Shabanov

[Exist-development] 99 issues, but a release ain't one!

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

Hey devs,

I am concerned that when I last looked, we had 99 open issues on
GitHub. I think we are getting to that horrible situation that we also
had on SF, which is that we have many issues that are never addressed
or fixed. Apart from Dannes I don't see a lot of people consistently
responding to issues. This is not good as many people look at this
figure as part of an indicator to the health of a project.

I was thinking that perhaps we could have an issue hack-weekend, where
we all agree a weekend and then explicitly spend the weekend working
together to attack issues and trying to fix/answer as many as possible
to reduce the backlog. This could be done via Skype (or other) from
home/office without actually meeting.

Would anyone else be willing to set aside a weekend for this? If so,
could you give me a vague idea of which weekends you might have
available in the next 3 months.

Cheers Adam.

-- 
Adam Retter

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

Re: [Exist-development] unable to get monex to work in servlet container

[Chris T. <chr...@gm...>]

Hello,

I copied exist-monex-0.5.jar into WEB-INF/lib and restarted the clean test database and the following errors appeared in the catalina.out:

> 04-Mar-2015 14:28:21.700 INFO [main] org.apache.catalina.core.AprLifecycleListener.init The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /Users/chris/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
> 04-Mar-2015 14:28:21.811 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-51173"]
> 04-Mar-2015 14:28:21.819 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
> 04-Mar-2015 14:28:21.820 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-51176"]
> 04-Mar-2015 14:28:21.822 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
> 04-Mar-2015 14:28:21.822 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 266 ms
> 04-Mar-2015 14:28:21.838 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
> 04-Mar-2015 14:28:21.838 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.12
> 04-Mar-2015 14:28:21.852 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist.war
> 04-Mar-2015 14:28:28.474 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: 
>  org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/exist]]
> 	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
> 	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
> 	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
> 	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714)
> 	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:919)
> 	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1704)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Invalid <url-pattern> rconsole in servlet mapping
> 	at org.apache.catalina.core.StandardContext.addServletMapping(StandardContext.java:3104)
> 	at org.apache.catalina.core.StandardContext.addServletMapping(StandardContext.java:3079)
> 	at org.apache.catalina.startup.ContextConfig.configureContext(ContextConfig.java:1368)
> 	at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1172)
> 	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:767)
> 	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:302)
> 	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
> 	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
> 	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5074)
> 	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> 	... 10 more
> 
> 04-Mar-2015 14:28:28.475 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist.war
>  java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/exist]]
> 	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:727)
> 	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
> 	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714)
> 	at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:919)
> 	at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1704)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> 
> 04-Mar-2015 14:28:28.476 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/exist.war has finished in 6,624 ms
> 04-Mar-2015 14:28:28.477 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/docs
> 04-Mar-2015 14:28:28.527 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/docs has finished in 50 ms
> 04-Mar-2015 14:28:28.527 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/examples
> 04-Mar-2015 14:28:28.669 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/examples has finished in 142 ms
> 04-Mar-2015 14:28:28.669 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/host-manager
> 04-Mar-2015 14:28:28.680 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/host-manager has finished in 11 ms
> 04-Mar-2015 14:28:28.681 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/manager
> 04-Mar-2015 14:28:28.692 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/manager has finished in 11 ms
> 04-Mar-2015 14:28:28.700 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/ROOT
> 04-Mar-2015 14:28:28.714 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/indium/exist/apache-tomcat-8.0.12/webapps/ROOT has finished in 14 ms
> 04-Mar-2015 14:28:28.718 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-51173"]
> 04-Mar-2015 14:28:28.722 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-51176"]
> 04-Mar-2015 14:28:28.723 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 6900 ms


Chris



> On Mar 4, 2015, at 12:52 PM, wol...@gm... wrote:
> 
> Hi,
> 
>> When I build and run standalone (./bin/startup.sh) on a virgin database and open the dashboard >> package manager and install monex, I then can successfully launch monex.
> 
> Ok, this would imply in general that the class loader is not picking up the jars when running in a .war. I’ll test this.
> 
> In the meantime you could manually copy the jars into the WEB-INF/lib/ directory so they get picked up.
> 
> Wolfgang

Re: [Exist-development] unable to get monex to work in servlet container

[<wol...@gm...>]

Hi,

> When I build and run standalone (./bin/startup.sh) on a virgin database and open the dashboard >> package manager and install monex, I then can successfully launch monex.

Ok, this would imply in general that the class loader is not picking up the jars when running in a .war. I’ll test this.

In the meantime you could manually copy the jars into the WEB-INF/lib/ directory so they get picked up.

Wolfgang

[Exist-development] unable to get monex to work in servlet container

[Chris T. <chr...@gm...>]

Hello,

Environment: Mac OS 10.10.2; java 1.8.0_31; Tomcat 8.0.12; eXist version:

  eXist-develop-20150303-5604f86

When I build and run standalone (./bin/startup.sh) on a virgin database and open the dashboard >> package manager and install monex, I then can successfully launch monex.

However, when I ./build.sh dist-war and deploy in tomcat on a virgin database and open the dashboard >> package manager and install monex and then launch monex I get the following resutl:

>   <exception>
>     <path>/db/apps/monex/modules/view.xql</path>
>     <message>
>       exerr:ERROR error found while loading module app: Error while loading module app.xql: error found while loading module console: Cannot find module class from EXPath repository: org.exist.console.xquery.ConsoleModule
>     </message>
>   </exception>


The repair:… functions don’t help and would seem to be superfluous any way since this is a fresh clean install.

I had thought that the problem was related to restoring an old /db/apps onto a fresh db and I did a test where I unzipped a full backup and then restored all but the old /db/apps and then installed monex and got the above error. This led me to see what happens in the initial conditions which is that monex doesn’t work.

I’ve tried installing and restarting the tomcat + db to no avail. I’ve tried running the repair functions at various points to no avail. I’ve verified that the monex is present in data/expathrepo as expected and that the ConsoleModule is in the jar in the /db/apps/monex/contents and so on.

I can’t migrate our production system until I can get monex working since with the removal of exist/admin there is no way to monitor and so on.

Finally, there’s nothing in the exist.log or any of the tomcat logs.

Thanks,
Chris

Re: [Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

> On 20 Feb 2015, at 23:24 , Adam Retter <ad...@ex...> wrote:
> 
> Is there a particular reason not to move to 2.x?


yes, licensing ;

the only usable option for eXist-db would be the implementation without LOCKing support ; for many users this limitation is not acceptable….

D.

Re: [Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

FYI I'm using DeletableCollectionResource with Milton 1.8

On Fri, Feb 20, 2015 at 5:24 PM, Adam Retter <ad...@ex...> wrote:

> Is there a particular reason not to move to 2.x?
> On 20 Feb 2015 21:24, "Dannes Wessels" <da...@ex...> wrote:
>
>> Hi,
>>
>>
>> On 20 Feb 2015, at 21:23 , Casey Jordan <cas...@jo...> wrote:
>>
>> Since MiltonCollection does not extend DeletableCollectionResource then
>> the default behavior is that the milton does a depth first traversal
>> deleting leaf documents and collections one by one.
>>
>> This isn't very atomic so I am just wondering if there was a specific
>> reason it was chosen to have it work this way?
>>
>>
>> pooh, I implemented the code quite some time ago, so I do not recall the
>> details; I probably did overlook DeletableCollectionResource, maybe because
>> some essential documentation was missing; or it was not available yet; at
>> least I did not need it to implement for a full feature set;
>>
>> checking the 2.x documentation, this could indeed acceleration the delete
>> operation; My first thought is however.... the documentation you find right
>> now is about the 2.x version, we still use the 1.x one (I don;t expect
>> we'll be upgrading)
>>
>> cheers
>>
>> Dannes
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Exist-development mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-development
>>
>>


-- 
--
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.

Re: [Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

Is there a particular reason not to move to 2.x?
On 20 Feb 2015 21:24, "Dannes Wessels" <da...@ex...> wrote:

> Hi,
>
>
> On 20 Feb 2015, at 21:23 , Casey Jordan <cas...@jo...> wrote:
>
> Since MiltonCollection does not extend DeletableCollectionResource then
> the default behavior is that the milton does a depth first traversal
> deleting leaf documents and collections one by one.
>
> This isn't very atomic so I am just wondering if there was a specific
> reason it was chosen to have it work this way?
>
>
> pooh, I implemented the code quite some time ago, so I do not recall the
> details; I probably did overlook DeletableCollectionResource, maybe because
> some essential documentation was missing; or it was not available yet; at
> least I did not need it to implement for a full feature set;
>
> checking the 2.x documentation, this could indeed acceleration the delete
> operation; My first thought is however…. the documentation you find right
> now is about the 2.x version, we still use the 1.x one (I don;t expect
> we’ll be upgrading)
>
> cheers
>
> Dannes
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>
>

Re: [Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

Ok thanks Dannes.

On Fri, Feb 20, 2015 at 4:24 PM, Dannes Wessels <da...@ex...> wrote:

> Hi,
>
>
> On 20 Feb 2015, at 21:23 , Casey Jordan <cas...@jo...> wrote:
>
> Since MiltonCollection does not extend DeletableCollectionResource then
> the default behavior is that the milton does a depth first traversal
> deleting leaf documents and collections one by one.
>
> This isn't very atomic so I am just wondering if there was a specific
> reason it was chosen to have it work this way?
>
>
> pooh, I implemented the code quite some time ago, so I do not recall the
> details; I probably did overlook DeletableCollectionResource, maybe because
> some essential documentation was missing; or it was not available yet; at
> least I did not need it to implement for a full feature set;
>
> checking the 2.x documentation, this could indeed acceleration the delete
> operation; My first thought is however.... the documentation you find right
> now is about the 2.x version, we still use the 1.x one (I don;t expect
> we'll be upgrading)
>
> cheers
>
> Dannes
>
>


-- 
--
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.

Re: [Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

Hi,


> On 20 Feb 2015, at 21:23 , Casey Jordan <cas...@jo...> wrote:
> 
> Since MiltonCollection does not extend DeletableCollectionResource then the default behavior is that the milton does a depth first traversal deleting leaf documents and collections one by one.
> 
> This isn't very atomic so I am just wondering if there was a specific reason it was chosen to have it work this way?

pooh, I implemented the code quite some time ago, so I do not recall the details; I probably did overlook DeletableCollectionResource, maybe because some essential documentation was missing; or it was not available yet; at least I did not need it to implement for a full feature set;

checking the 2.x documentation, this could indeed acceleration the delete operation; My first thought is however…. the documentation you find right now is about the 2.x version, we still use the 1.x one (I don;t expect we’ll be upgrading)

cheers

Dannes

[Exist-development] Why does MiltonCollection not implement DeletableCollectionResource?

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

Since MiltonCollection does not extend DeletableCollectionResource then the
default behavior is that the milton does a depth first traversal deleting
leaf documents and collections one by one.

This isn't very atomic so I am just wondering if there was a specific
reason it was chosen to have it work this way?

Thanks,

Casey

-- 
--
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.