Activity
From 03/27/2022 to 04/25/2022
04/25/2022
- 03:42 PM Support #5567: move FWD to Java 11
- Rebased to latest 3821c and still testing
- 01:44 PM Support #5567: move FWD to Java 11
- Greg Shah wrote:
> Please show an example.
antlr warnings are related with objects representing numbers instantiati...
04/22/2022
- 01:27 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- OK, at a minimum, it seems like we need a list of those paths which are unsecured. These are publicly visible and re...
- 12:42 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg, this is a 'chicken and the egg' problem. Lets say an application secures only the @/rest/private/@ paths and l...
- 12:31 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- > If I use defaults for @login_path@, this mode where authentication is done at each call will no longer work.
Wha... - 12:08 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- The structure of an ACL to check if a path must be authenticated is:...
- 12:08 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > If I force defaults for @rest/authentication/login_path@ and @rest... - 12:05 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Constantin Asofiei wrote:
> If I force defaults for @rest/authentication/login_path@ and @rest/authentication/logout... - 06:38 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- If I force defaults for @rest/authentication/login_path@ and @rest/authentication/logout_path@, to @/fwdlogin@ and @/...
- 11:52 AM Support #5567: move FWD to Java 11
- Tomasz Domin wrote:
> Greg Shah wrote:
> > > Unfortunately antlr generated code will produce warnings in Java 11 un... - 10:10 AM Support #5567: move FWD to Java 11
- Today I refactored code to make use of ReflectiveOperationException on .newInstance (instead of 4 other exceptions), ...
- 05:42 AM Support #5567: move FWD to Java 11
- Greg Shah wrote:
> > Unfortunately antlr generated code will produce warnings in Java 11 until we migrate to newer v...
04/21/2022
- 12:46 PM Support #5567: move FWD to Java 11
- > Unfortunately antlr generated code will produce warnings in Java 11 until we migrate to newer version (which is a s...
- 12:36 PM Support #5567: move FWD to Java 11
- Today I've mainly worked on changes to newInstance and datatypes conversion, static accessors
Unfortunately antlr g... - 11:38 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> > or just disable the authentication at the rest/soap/webhandler nodes in the directory.
>
> W... - 11:18 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > or just disable the authentication at the rest/soap/webhandler nodes in the directory.
What is the advantage of ... - 11:14 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> This approach requires an explicit intervention to open everything. But that intervention is not... - 11:13 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- This approach requires an explicit intervention to open everything. But that intervention is not hard. It is just a...
- 09:27 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > the point is to 'force' the user to 'open access to all' for certain APIs, so these are explicitly visible in the d...
- 09:18 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> We probably should all the ones that are built into FWD. I see no reason these should be optiona... - 09:02 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > > I agree that we cannot expect calling applications to be rewritten to our authentication model. I'm not suggesti...
- 08:53 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Code Review Task Branch 3821c Revision 13800
The changes are good.
04/20/2022
- 03:08 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- 3821c/13800 contains improvements from the #5896-17 review.
The docs are updated and examples added in [[p2j:Java ...
04/19/2022
- 11:07 AM Support #5567: move FWD to Java 11
- Rebased to the latest p2j 3821c (13792)
Managed to build and test hotel_chui - no issues found.
As I dont have a ...
04/15/2022
- 01:42 PM Support #5567: move FWD to Java 11
- Tomasz Domin wrote:
> But I cannot make Swing GUI work - there is only yellow rectangle on screen, the application s...
04/14/2022
- 10:59 AM Support #5567: move FWD to Java 11
- Client Web GUI - both embedded and Virtual Desktop are now working fine
But I cannot make Swing GUI work - there is ... - 02:23 AM Support #5567: move FWD to Java 11
- Client Web GUI app works except there is a problem with font sizes.
The reason is modularization and ClassLoader.cl...
04/13/2022
- 04:10 PM Support #5567: move FWD to Java 11
- Built hotel_gui, but it does not work correctly.
Most of the scripts for hotel_*ui are based on system-wide java ins... - 06:37 AM Support #5567: move FWD to Java 11
- Attached for the reference only - patch against trunk branch
branch 5567a:
Rebased to 3821c, pushed to 5567a, com... - 11:27 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Ovidiu Maxiniuc wrote:
> @RecordSerializer@:
> * method @initialize()@: I think @record.initialize()@ should be inv...
04/12/2022
- 04:27 PM Support #5567: move FWD to Java 11
- Till now worked on trunk branch, as I was already working on it:
Added dependencies missing in java 11:
fwdCCS g... - 10:29 AM Support #5567: move FWD to Java 11
- > as I didn't know if there are any projects based on clean trunk.
All projects are dependent upon 3821c at this p... - 10:24 AM Support #5567: move FWD to Java 11
- Greg Shah wrote:
> Via email, from Tomasz:
> Please make sure to rebase 5567a from the latest 3821c. The differenc... - 09:14 AM Support #5567: move FWD to Java 11
- Via email, from Tomasz:
> Created branch 5567a, started porting with fixing compilation bugs. I've considered upgr...
04/11/2022
- 02:42 AM Support #5567 (WIP): move FWD to Java 11
- First step - prepare a plan.
Need to review all the code and all tools for problems with JDK11
04/07/2022
- 02:04 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> So: if the calling application has multiple threads, each thread will execute the login with the ... - 01:57 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> 1. The reasoning behind the use of @ThreadLocal@ in @JsonRequestsParser@, @ResponseArguments@ is ... - 01:37 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Code Review Task Branch 3821c Revisions 13714, 13740
It is very good. I especially like the extensibility of the ... - 11:42 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > The authentication and authorization implementation does this:
> * the request has a FWD username and a token. FW... - 11:17 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > 7. There is a comment "authentication and authorization is not mandatory". Does this mean that by default everythin...
- 11:11 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg Shah wrote:
> Help me understand the current model, then we will discuss this issue.
The authentication and au... - 10:55 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > concurrency issues: FWD contexts do not support this. So I need to prohibit an API call (or queue them?) if there i...
- 10:48 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- I have reviewed the documentation. Here are some questions/comments about the implementation:
Overall, this is ve...
04/06/2022
- 01:55 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg, please review [[p2j:Java REST Services]] and [[p2j:Securing the Web Services (REST, SOAP, WEBHANDLER)]], and le...
04/05/2022
- 01:57 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- The changes to add authentication and authorization for web services are in 3821c/13740.
I'll finish the documenta... - 12:10 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg, something which should have been obvious for me from the start: the agent will switch context and execute the t...
04/04/2022
- 01:01 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg, some notes about the authentication mechanism:
* the webservice resource plugin will allow ACLs to be set for ...
03/31/2022
- 12:46 PM Bug #6227: AcmeClient - unsupported Challenge Type
- Current AcmeClient implementation is using TlsSni01Challenge, which is unsupported since 2019.
It must to be migrate... - 12:45 PM Bug #6227 (New): AcmeClient - unsupported Challenge Type
- 10:18 AM Feature #5896: enhance legacy REST support to provide better pure Java development
- > Also, what wiki should I use for the documentation?
See [[p2j:Java REST Services]]
03/30/2022
- 04:06 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Constantin Asofiei wrote:
> Ovidiu: please take a look at @p2j.persist.Record@ and @p2j.rest.serializers.RecordSeria...
03/29/2022
- 01:52 PM Feature #5896: enhance legacy REST support to provide better pure Java development
- Greg, the support for the REST services implemented directly in Java is in 3821c/13714.
Please review. Also, what...
Also available in: Atom