Project

General

Profile

Feature #1638

implement Java access to converted appserver code (must be a simple replacement for the “Open Java Client”)

Added by Greg Shah over 11 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Constantin Asofiei
Target version:
FWD - Runtime Support for Server Features
Start date:
05/25/2013
Due date:
05/30/2013
% Done:

100%

Estimated time:
32.00 h
billable:
No
vendor_id:
GCD
version_reported:
version_resolved:

Related issues

Blocked by Base Language - Feature #1608: implement full appserver support (from 4GL clients only) Closed 02/08/2013 05/24/2013

History

#1 Updated by Greg Shah over 11 years ago

One approach: based on a list of interfaces (hints), create a set of Java interfaces that can be used via our net protocol to access the remote features of this appserver; provide a simple connection/invocation example/helpers.

#2 Updated by Greg Shah over 11 years ago

  • Target version set to Milestone 7

#3 Updated by Greg Shah about 11 years ago

  • Estimated time changed from 80.00 to 32.00
  • Assignee set to Constantin Asofiei

The customer appserver only has 1 entry point that is called remotely. It provides their "entity API" via a single top-level procedure.

This task will be simplified down to the following work:

1. Manually code an interface that contains a single method that represents this entity API entry point.

2. Manually code an implementation of this interface that runs on the P2J server and which properly invokes the backing converted procedure in appserver context.

3. Manually create the code and config to load this server-side code (and export the interface) at P2J load time.

4. Manually write a sample that connects to the P2J server, obtains the remote object and calls the entity API.

5. Integrate this stuff into the customer project build.

At this time we don't need to implement any automated conversion processing.

I expect this plan to be refined once the #1991 is implemented.

#4 Updated by Greg Shah about 11 years ago

  • Start date set to 05/25/2013
  • Due date set to 05/30/2013

#5 Updated by Greg Shah about 11 years ago

In the next 2-3 weeks we need to share details about the design of how Java code will be able to use the appserver functionality (#1638). Today they use the Open Java Client provided by Progress. They will replace that with hand-coded Java that uses the equivalent techniques in P2J.

In support of you thinking on the above, you should take a look at the code in ~/secure/clients/<customer>/<app_name>_comms/AppserverConnectionV1.zip. This is a cut-down version of the code in their <app_name> (previously called <old_app_name>) application. They have built an abstraction layer to hide the usage of the Open Java Client.

I will be posting some additional notes shortly.

LE: GES removed customer-specific name and app names from this entry.

#6 Updated by Constantin Asofiei almost 11 years ago

  • Status changed from New to WIP
  • % Done changed from 0 to 80

#7 Updated by Greg Shah almost 11 years ago

Is there anything left to do on this or can we close the task?

#8 Updated by Constantin Asofiei almost 11 years ago

At this time, no.

#9 Updated by Greg Shah almost 11 years ago

  • % Done changed from 80 to 100
  • Status changed from WIP to Closed

#10 Updated by Greg Shah over 7 years ago

  • Target version changed from Milestone 7 to Runtime Support for Server Features

Also available in: Atom PDF