Getdown how do I dynically change a value in a file without running digester

[Doug Sievers]

We have the need to be able to change a config property file that has a line in it like the following:
providerUrl=http-remoting://<location1>

if we have a server issue and need to change over to another location with
java web start we would
just change the config file to be this:
providerUrl=http-remoting://<location2>

but with getdown this only works if we run the digester.  Is there a way to
do this without running the digester?

Same issue if we want to change logging levels or any other dynamic change.

[Michael Bayne]

I assume that you mean you want to make some change to the app configuration which is then picked up as an update by everyone who runs your app. In that case, you have to update the getdown.txt file and generate an updated digest.txt file because that's how Getdown knows that there is an app update which needs to be downloaded and applied.

There is no way to convey configuration changes to all the computers that have installed your application short of an actual update to your app.

If you're just talking about the user making a change to their local system that causes their app to behave in a different way, but wherein Getdown does not discover an app update and download and apply it, then there are other mechanisms to make dynamic changes, but it doesn't sound like that's what you want.

--
You received this message because you are subscribed to the Google Groups "OOO Libs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ooo-libs+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ooo-libs/bca05bef-d52d-4494-828c-8780dbc02fa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-- m...@samskivert.com

[Doug Sievers]

Ok, so we decided to write a bat file that will make the change they want to the properties file, then run the digester.  but it still is not showing up on the client machines.  Does the digester not recognize changes to resource = files  ?

On Wednesday, June 26, 2019 at 6:19:39 PM UTC-6, Michael Bayne wrote:

I assume that you mean you want to make some change to the app configuration which is then picked up as an update by everyone who runs your app. In that case, you have to update the getdown.txt file and generate an updated digest.txt file because that's how Getdown knows that there is an app update which needs to be downloaded and applied.

There is no way to convey configuration changes to all the computers that have installed your application short of an actual update to your app.

If you're just talking about the user making a change to their local system that causes their app to behave in a different way, but wherein Getdown does not discover an app update and download and apply it, then there are other mechanisms to make dynamic changes, but it doesn't sound like that's what you want.

On Thu, Jun 20, 2019 at 12:14 PM Doug Sievers <dsieve...@gmail.com> wrote:

We have the need to be able to change a config property file that has a line in it like the following:
providerUrl=http-remoting://<location1>

if we have a server issue and need to change over to another location with
java web start we would
just change the config file to be this:
providerUrl=http-remoting://<location2>

but with getdown this only works if we run the digester.  Is there a way to
do this without running the digester?

Same issue if we want to change logging levels or any other dynamic change.

--
You received this message because you are subscribed to the Google Groups "OOO Libs" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ooo-...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ooo-libs/bca05bef-d52d-4494-828c-8780dbc02fa2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-- m...@samskivert.com

[Martin Brunecky]

We handle deployment (on Tomcat) and any deployed app changes by having an (init) servlet which monitors the deployed app and our configuration files. On any change it re-generates any files that must change and then runs the digester against deployed webapp.

Next time getdown starts that webapps it detects the changes and updates local cache. 

Hence we do not build digests etc at the app build time but only on deployment. Each deployed app has it's own server though we share our configuration files.

To unsubscribe from this group and stop receiving emails from it, send an email to ooo-libs+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ooo-libs/fc5ee3d4-beaa-429c-bdd1-02f4fb74cc09%40googlegroups.com.