[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Standard way to daemonize Equinox


On 14-Mar-09, at 2:47 PM, Pascal Rapicault wrote:

It is complementary.
- console and port will give unsecure remote access to the fwk.
- ignoreApp will cause the fwk to not look for an application on startup and thus avoid an entry in the log
- noExit will prevent the fwk to exit.

My JSW entry now looks like:

wrapper.app.parameter.1=org.eclipse.equinox.launcher.Main
wrapper.app.parameter.2=-ignoreApp
wrapper.app.parameter.3=-noExit

But but the container is still exiting. I'm using eclipse-equinox-3.4.zip bundle. Is ignoreApp an option or a system property?

<graycol.gif>Jason van Zyl ---03/14/2009 04:19:56 PM---On 14-Mar-09, at 10:16 AM, Pascal Rapicault wrote: > This seems reasonable. If you are not running a

<ecblank.gif>
From:
<ecblank.gif>
Jason van Zyl <jason@xxxxxxxxx>
<ecblank.gif>
To:
<ecblank.gif>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
<ecblank.gif>
Date:
<ecblank.gif>
03/14/2009 04:19 PM
<ecblank.gif>
Subject:
<ecblank.gif>
Re: [equinox-dev] Standard way to daemonize Equinox






On 14-Mar-09, at 10:16 AM, Pascal Rapicault wrote:
That seems to be down.

Is specifying this system property different then port listening trickery?
      PaScaL

      <graycol.gif>
      Jason van Zyl ---03/14/2009 12:25:08 PM---Hi, After puttering around for a few minutes I found something for
      <ecblank.gif>
      From:
      <ecblank.gif>
      Jason van Zyl <jason@xxxxxxxxx>
      <ecblank.gif>
      To:
      <ecblank.gif>
      equinox-dev@xxxxxxxxxxx
      <ecblank.gif>
      Date:
      <ecblank.gif>
      03/14/2009 12:25 PM
      <ecblank.gif>
      Subject:
      <ecblank.gif>
      [equinox-dev] Standard way to daemonize Equinox




      Hi,

      After puttering around for a few minutes I found something for  
      daemonizing Equinox but I wanted to see if there is a more standard  
      way. In my Java Service Wrapper I have the following:

      wrapper.app.parameter.1=org.eclipse.equinox.launcher.Main
      wrapper.app.parameter.2=-console
      wrapper.app.parameter.3=5901
      wrapper.app.parameter.4=-noExit

      Is there a better, more accepted way of doing this? I'm attempting to  
      create a framework for building stock Maven assemblies for JSW+Plexus,  
      JSW+Equinox, and JSW+Jetty and I just want to make sure I'm using the  
      best practices for Equinox.

      Thanks,

      Jason

      ----------------------------------------------------------
      Jason van Zyl
      Founder,  Apache Maven

      http://twitter.com/jvanzyl
      ----------------------------------------------------------

      Selfish deeds are the shortest path to self destruction.

      -- The Seven Samuari, Akira Kurosawa

      _______________________________________________
      equinox-dev mailing list

      equinox-dev@xxxxxxxxxxx
      https://dev.eclipse.org/mailman/listinfo/equinox-dev


      _______________________________________________
      equinox-dev mailing list

      equinox-dev@xxxxxxxxxxx
      https://dev.eclipse.org/mailman/listinfo/equinox-dev

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------

A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole

-- Christopher Alexander, A Pattern Language

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
----------------------------------------------------------