Activity
From 08/04/2021 to 09/02/2021
09/02/2021
- 05:33 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I have most all of this task coded up, but I am unsure of one aspect. I have added a *String protocol* parameter that...
- 03:23 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> I like your original idea of providing a range of string parameters. If the chosen secure socket... - 02:31 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > perhaps we should just have -tls as an additional option, which would generate the TLSv1.2 context?
No, I think ... - 02:25 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- When @-ssl@ is passed in the @ENABLE-CONNECTIONS@ string @LowLevelSocketListerner.enableSSLConnections@ performs:
<p... - 11:46 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Ovidiu Maxiniuc wrote:
> Most likely at this point @keyStorePassword@ was an empty @String@.
Thanks, Ovidiu. That... - 07:54 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Roger Borrello wrote:
> It's not a question of getting hung up. I would expect that for any algorithm I add, there w... - 09:10 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- The attached is the zipped archive of the https://github.com/gquerret/adetran project sources. I'm also attaching the...
- 08:48 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Hynek alerted me to the following interesting articles:
https://knowledgebase.progress.com/articles/Article/Transl... - 07:21 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Yes, but you should base it on 3821c.
- 07:04 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg, should I create new task branch for the changes?
- 07:01 AM Feature #3817 (WIP): create resource bundles from string literals and implement optional support ...
09/01/2021
- 06:40 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Greg Shah wrote:
> Please see #2181 for details on the existing 4GL-compatible SSL socket support. Search on "keyst... - 03:15 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Please see #2181 for details on the existing 4GL-compatible SSL socket support. Search on "keystore" and "default_se...
- 03:08 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Constantin Asofiei wrote:
> I suspect the correct location is in the @deploy/client@ folder or wherever the FWD clie... - 02:47 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- I suspect the correct location is in the @deploy/client@ folder or wherever the FWD client working dir is.
- 02:45 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Actually, the @keyStoreName@ cannot be found. I tried to copy @./deploy/server/standard-private-key.store@ to @defaul...
- 02:42 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- > @KeyStore ks = KeyStore.getInstance("JKS"); <-- I believe this comes back null@
That doesn't so... - 01:02 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- The testcases I found in @uast/sockets@ and @uast/sockets/ssl@ are very helpful. However, I may need a little help co...
- 06:39 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- And which doesn't conflict with existing syntax from the 4GL.
- 06:38 AM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- It is our own syntax. This is a new feature/enhancement. Just make the syntax anything that makes sense and is easy...
08/31/2021
- 04:59 PM Feature #4366: support TLS 1.2 and other updated secure socket protocols
- Does 4GL already have syntax to enable this? Or are we making up our own?
In looking for the best documentation, i... - 08:16 AM Bug #5635: OpenEdge.Core.Util.ConfigBuilder implementation
- The current implementation is not fully compatible with 4GL because is is using a @Map@ to store the key/value pairs ...
- 08:16 AM Bug #5635 (New): OpenEdge.Core.Util.ConfigBuilder implementation
08/20/2021
- 12:07 PM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Please make a list of all of the cases you have found. It is OK to just list the names of the 4GL programs in the @t...
- 11:32 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Greg Shah wrote:
> Igor: Let's avoid using the term "UDF" here since that is specific to database WHERE clause execu... - 10:52 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- Igor: Let's avoid using the term "UDF" here since that is specific to database WHERE clause execution. The problem h...
- 10:50 AM Bug #5613: 4GL built-in functions throw IllegalArgumentException
- From Igor:
> Some Java counterparts of 4GL functions which are called directly from the converted code can throw @... - 10:50 AM Bug #5613 (New): 4GL built-in functions throw IllegalArgumentException
- 11:06 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> The plan is good.
>
> > 3. Implement conversion rules to emit required Java code - any bundle ... - 10:59 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- The plan is good.
> 3. Implement conversion rules to emit required Java code - any bundle initialization logic, ge... - 10:52 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- In order to estimate the efforts I came up with the following sub tasks:
1. Resolve the unknowns laid out by Greg ... - 09:34 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> * The 4GL essentially has resource-bundles that are specific to a single program. This may have ... - 09:28 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Depending on the @CURRENT-LANGUAGE@ scope, the resource bundle will have to be scoped accordingly. The possible outco...
- 08:08 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Hynek Cihlar wrote:
> Greg Shah wrote:
> > +FWD Implementation Questions+
> >
> > * To match the behavior of the... - 07:51 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- > I assume the scope includes translation of FWD runtime, too. Like error messages. Correct?
No, we will handle th... - 03:02 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- Greg Shah wrote:
> +FWD Implementation Questions+
>
> * To match the behavior of the 4GL
Greg, what behavior ... - 02:30 AM Feature #3817: create resource bundles from string literals and implement optional support for se...
- I assume the scope includes translation of FWD runtime, too. Like error messages. Correct?
08/18/2021
- 01:01 PM Bug #5608: raw vs memptr parameters
- @testcases/uast/memptr/memptr_vs_raw.p@ has some tests where raw/memptr args are passed for memptr/raw parameters. F...
- 12:56 PM Bug #5608 (New): raw vs memptr parameters
- 10:13 AM Bug #2375: fix the memptr initialization (in extent) and memptr parameter processing
- Greg Shah wrote:
> In @public raw(byte[] val)@, I think this text needs to be removed from the javadoc: "The passed ... - 09:17 AM Bug #2375 (Closed): fix the memptr initialization (in extent) and memptr parameter processing
- Code Review Task Branch 3821c Revision 12835
The solution is elegant and it makes sense.
In @public raw(byte[] ... - 06:19 AM Bug #2375 (Review): fix the memptr initialization (in extent) and memptr parameter processing
- The changes are in 3821c rev 12835.
- 05:33 AM Bug #2375: fix the memptr initialization (in extent) and memptr parameter processing
- The 'memptr is both unknown and not-unknown' seems to not happen in Windows OE 11.6. Do you recall if the #1635-31 w...
- 02:17 AM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- Greg Shah wrote:
> I'm confused by this code in @symbolResolver.loadConvertedClass()@:
>
> [...]
>
> Why do we...
08/17/2021
- 03:42 PM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- I'm confused by this code in @SymbolResolver.loadConvertedClass()@:...
- 08:32 AM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- Greg Shah wrote:
> I think we always have a @ClassDefinition@ instance whenever we also have a @ConvertedClassName@ ... - 08:26 AM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- Greg Shah wrote:
> The current implementation splits the conversion of method names between parse time, annotations ... - 08:20 AM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- I think we always have a @ClassDefinition@ instance whenever we also have a @ConvertedClassName@ instance. Let me kn...
08/16/2021
- 03:29 PM Feature #4350: method overload when they differ by a temp-table, dataset, buffer or object or ext...
- The current implementation splits the conversion of method names between parse time, annotations prep (@naming.rules@...
Also available in: Atom