Re: WOlips Installation problem

[Klaus Berkling]

> On Nov 13, 2018, at 1:30 AM, Dennis Bliefernicht 
>  wrote:
> 
> Hm,
> 
>> On 13. Nov 2018, at 03:31, Klaus Berkling > > wrote:
>> 
>>> On Nov 12, 2018, at 12:23 AM, Dennis Bliefernicht 
>>> >> > wrote:
>>> the exception rather hints at an SSL problem even before trying to read the 
>>> content.xml; we experienced this exact issue before when running an older 
>>> JDK version, as wocommunity uses Lets Encrypt; the relevant root 
>>> certificates it seems only have been added in Java 8u101 and Java 7u111 (or 
>>> Java 9+) so you could either try upgrading the JDK you use for running 
>>> eclipse or import the relevant certificates into your keystore manually. 
>>> (See also https://letsencrypt.org/docs/certificate-compatibility/ 
>>> ).
>>> At least in our case a JDK update solved this issue since then.
>>> 
>> 
>> I updated to 1.8.0_191 but get the same error… :-( 
> 
> Just another hunch based on bad experience ;-) assuming a macOS installation: 
> As Eclipse sometimes likes to hardcode the installation VM on macOS (for 
> example in /Applications/Eclipse.app/Contents/Eclipse/eclipse.ini, hit me 
> once or twice during cleanup), might make sense to double-check the Menu 
> Eclipse -> About Eclipse -> Installation Details -> Configuration where 
> amongst all other system properties the java.runtime.version property should 
> indicate the actual running JDK. 
> 
> For reference: Running an OpenJDK Zulu build from Azul here, Version 
> 1.8.0_181-b02 on Mojave 10.14 using Eclipse Photon and can pull the WOLips 
> packages from the given URL
> 


That did the trick.  Changed the eclipse.ini file to point to the updated 
version.

Here is my setup:  Sun  Oracle Java JDK 1.8.0_191 on Mojave 10.14.1 using 
Eclipse 2018-09 (4.9) with WOnder7
Created a Wonder application from the template which compiled and ran with no 
problem.

Thanks Dennis.


"The era of procrastination, of half-measures, of soothing and baffling 
expedients, of delays, is coming to its close. In its place we are entering a 
period of consequences."
Winston Churchill

Klaus Berkling
www.berkling.us  | @kiberkli | Photography 







 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Consolidation of ERXMigrations

[Jesse Tayler]

I don’t see why not -- migrations keep a version available in the db to test 
against so the condition of the db can be anywhere along the line from no 
updates to half way or whatever this number just has to be in sync with the 
right level of update.

So, you don’t want to disrupt that continuity but that doesn’t mean you can’t 
write something in the first section that runs if the db version is zero and 
pushes it to completed version or something.

Migrations is a very simple mechanism so just be sure you understand the 
version number stored and how to adjust or use it and you should be fine.

Handily, Migrations are easy to run in a series of tests to prove it is ok 
before you release on production.



> On Nov 13, 2018, at 11:09 AM, Kai Lochbaum  
> wrote:
> 
> Hi everyone,
>  
> over the years we have accumulated lots of migration versions in multiple 
> models (one at 66, another at 54).
>  
> Did anyone ever think about some sort of consolidation to make the initial 
> migration on a fresh database quicker?
>  
> I was thinking of something like a “skipToVersion” method where you would 
> update your 0-Migration with the most current database model and add a 
> skipToVersion(66) call at the end, so that ERXMigration directly skips from 0 
> to 66.
>  
>  
>  
> Cheers,
> Kai Lochbaum
>  
> --
>  
> Telefon: 069 / 65 00 96 - 17  |  E-Mail: lochb...@salient-doremus.de 
> 
>  
> salient GmbH, Lindleystraße 12, 60314 Frankfurt
> Telefon Zentrale: 069 / 65 00 96 - 0  |  http://www.salient-doremus.de 
> ___
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com 
> )
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com 
> 
> 
> This email sent to jtay...@oeinc.com 
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Consolidation of ERXMigrations

[Kai Lochbaum]

Hi everyone,

over the years we have accumulated lots of migration versions in multiple 
models (one at 66, another at 54).

Did anyone ever think about some sort of consolidation to make the initial 
migration on a fresh database quicker?

I was thinking of something like a “skipToVersion” method where you would 
update your 0-Migration with the most current database model and add a 
skipToVersion(66) call at the end, so that ERXMigration directly skips from 0 
to 66.



Cheers,
Kai Lochbaum

--

Telefon: 069 / 65 00 96 - 17  |  E-Mail: 
lochb...@salient-doremus.de

salient GmbH, Lindleystraße 12, 60314 Frankfurt
Telefon Zentrale: 069 / 65 00 96 - 0  |  
http://www.salient-doremus.de
 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: WOlips Installation problem

[Dennis Bliefernicht]

Hm,

> On 13. Nov 2018, at 03:31, Klaus Berkling  wrote:
> 
>> On Nov 12, 2018, at 12:23 AM, Dennis Bliefernicht 
>> mailto:dennis.blieferni...@xyrality.com>> 
>> wrote:
>> the exception rather hints at an SSL problem even before trying to read the 
>> content.xml; we experienced this exact issue before when running an older 
>> JDK version, as wocommunity uses Lets Encrypt; the relevant root 
>> certificates it seems only have been added in Java 8u101 and Java 7u111 (or 
>> Java 9+) so you could either try upgrading the JDK you use for running 
>> eclipse or import the relevant certificates into your keystore manually. 
>> (See also https://letsencrypt.org/docs/certificate-compatibility/ 
>> ).
>> At least in our case a JDK update solved this issue since then.
>> 
> 
> I updated to 1.8.0_191 but get the same error… :-( 

Just another hunch based on bad experience ;-) assuming a macOS installation: 
As Eclipse sometimes likes to hardcode the installation VM on macOS (for 
example in /Applications/Eclipse.app/Contents/Eclipse/eclipse.ini, hit me once 
or twice during cleanup), might make sense to double-check the Menu Eclipse -> 
About Eclipse -> Installation Details -> Configuration where amongst all other 
system properties the java.runtime.version property should indicate the actual 
running JDK. 

For reference: Running an OpenJDK Zulu build from Azul here, Version 
1.8.0_181-b02 on Mojave 10.14 using Eclipse Photon and can pull the WOLips 
packages from the given URL

Greetings
Dennis

--






-
Dennis Bliefernicht • Head of Backend Development
T +49 40 357 3001 62
dennis.blieferni...@xyrality.com

XYRALITY GmbH • Friedensallee 290 • 22763 Hamburg
www.xyrality.com 
Registergericht: Hamburg HRB 115332
Geschäftsführer: Sven Ossenbrüggen
-

 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com