An EDT project has different layout with an RBD project, the best way to make RBD code working in EDT is to create a new EDT project and copy the code to it. There have also been some changes to the EGL language that may require you to change your RBD-developed code to be modified prior to running on EDT.&nbsp;

+

An EDT project has a different layout than an Rational Business Developer project. The best way to make Rational Business Developer code work in EDT is to create a new EDT project and copy the code to it. There have also been some changes to the EGL language that may require you to change your code before it can be run with EDT.&nbsp; In addition to the information mentioned below, a high level overview of changes can be found on the [[EDT:The_Differences_between_EDT_0.7.0_and_RBD|Differences between EDT 0.7.0 and IBM Rational Business Developer]] page.<br>

−

== Move code to an EDT project ==

+

== Move code to an EDT project ==

#Create a new EDT project.

#Create a new EDT project.

−

##If the application contains RUI Handlers, choose either '''Web2.0 client application''' or '''Web 2.0 client application with service''' depending on if the application also contains services.

##If the application contains only Programs and common code, choose '''Basic'''.

+

##If the application contains only Programs and common code, choose '''Basic'''.

−

#Copy EGL files and packages from the RBD project to the EDT project

+

#Copy EGL files and packages from the Rational Business Developer project to the EDT project.

−

#Configure EGL Compiler and generators. Compiler setting is a new feature in EDT which allows setting of different generators for each package and file.

+

#Configure the EGL Compiler and generators. The Compiler setting is a new feature in EDT which allows specifying generators for each package or file.

−

##Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts(Record, Library) which are referenced by Rich UI Handlers or Widgets

+

##Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts (Record, Library) which are referenced by Rich UI Handlers or Widgets.

−

##Select Java Generator for Services, Programs and any common parts referenced by Services or Programs

+

##Select Java Generator for Services, Programs and any common parts referenced by Services or Programs.

−

##Common parts require both JavaScript Generator and Java Generator are suggest to be put into a separate package which is configured with both Generators

+

##Common parts that require both JavaScript Generator and Java Generator should be put into a separate package configured with both Generators.

−

##Compiler setting of a parent resource is inherited by the children. Setting the package is usually good enough.

+

##The compiler setting of a parent resource is inherited by the children, so setting at the package level is usually good enough.

−

##Refactor package and code is sometimes necessary

+

##Refactoring packages and code is sometimes necessary.

−

+

== Modify EGL code ==

== Modify EGL code ==

+

#Use Organize Imports (Ctrl+Shift+O) to let EDT import the correct widgets and system parts. This is needed for almost all EGL files because of the package name changes.

#Use Organize Imports (Ctrl+Shift+O) to let EDT import the correct widgets and system parts. This is needed for almost all EGL files because of the package name changes.

−

#Below is a handy list of things to modify. It is recorded when we move RBD samples and test apps to EDT. See the [http://wiki.eclipse.org/EDT:EGL_Language_conversion EGL Language conversion page] for more information about updates to EGL. The [http://wiki.eclipse.org/EDT:Code_snippets Code snippets page] is also a good place to find code.

+

#Below is a handy list of things to modify. It is recorded when we moved Rational Business Developer samples and test apps to EDT. See the [[EDT:EGL Language conversion|EGL Language conversion page]] for more information about updates to EGL. The [[EDT:Code snippets|Code snippets page]] is also a good place to find code.

| In Rational Business Developer, you could set a non-nullable variable to null (in certain cases). This is not allowed in EDT. You must indicate the variable is nullable by using the&nbsp;? See [[EDT:Language Overview02#Nullability|Nullability]].

+

|-

+

| <source lang="java">

employeeList Employee[0];

employeeList Employee[0];

−

</source>

+

</source>

−

|<source lang="java">

+

| <source lang="java">

employeeList Employee[];

employeeList Employee[];

−

</source>

+

</source>

−

|Dimension is not allowed on Array declaration, change to [ ].

+

| Dimension is not allowed on an Array declaration, change to [ ].

|-

|-

−

|<source lang="java">

+

| <source lang="java">

−

program MyProgram type BasicProgram {}

+

−

library MyLibrary type BasicLibrary {}

+

−

record recordName type BasicRecord

+

−

</source>

+

−

|<source lang="java">

+

−

program MyProgram

+

−

record recordName

+

−

library MyLibrary

+

−

</source>

+

−

|Basic stereotypes including BasicLibrary, BasicProgram, BasicRecord are removed. A part without stereotype is the basic type

+

−

|-

+

−

|<source lang="java">

+

myService1 MyService {@DedicatedService};

myService1 MyService {@DedicatedService};

−

</source>

+

</source>

−

|<source lang="java">

+

| <source lang="java">

myService1 MyService?{@DedicatedService};

myService1 MyService?{@DedicatedService};

−

</source>

+

</source>

−

|Service-access variable has to be defined as nullable with a ?

+

| Service-access variable has to be defined as nullable with a&nbsp;?

|-

|-

−

|<source lang="java">

+

| <source lang="java">

myService1 MyService {@bindService{bindingKey = "abc"}};

myService1 MyService {@bindService{bindingKey = "abc"}};

−

</source>

+

</source>

−

|<source lang="java">

+

| <source lang="java">

myService1 MyService?{@Resource {bindingKey = "abc"}};

myService1 MyService?{@Resource {bindingKey = "abc"}};

Line 61:

Line 60:

myService1 MyService?;

myService1 MyService?;

−

myService1 = SysLib.getResource("abc");

+

myService1 = Resources.getResource("abc");

−

</source>

+

</source>

−

|@Resource annotation is new in EDT. Search "resource annotation" in help for the details.

+

| The @Resource annotation is new in EDT. For details, search the Help for "resource annotation".

| The default value for a new Date variable is the current date. The default value for a new Timestamp variable is the current date/time. Time is not a supported type (use Timestamp instead).

+

|-

+

| <source lang="java">

+

cTimeStamp Timestamp;

+

DateTimeLib.dayOf(cTimeStamp);

+

DateTimeLib.weekdayOf(cTimeStamp);

+

DateTimeLib.monthOf(cTimeStamp);

+

DateTimeLib.yearOf(cTimeStamp);

+

DateTimeLib.dateOf(cTimeStamp);

+

s String = "Some string of characters";

+

index int = Strlib.indexOf(s,"a");

+

s = Strlib.clip(s);

+

s = Strlib.lowerCase(s);

+

s = Strlib.upperCase(s);

+

</source>

+

| <source lang="java">

+

cTimeStamp timestamp;

+

cTimeStamp.dayOf();

+

cTimeStamp.weekdayOf();

+

cTimeStamp.monthOf();

+

cTimeStamp.yearOf();

+

cTimeStamp.dateOf();

+

s String = "Some string of characters";

+

index int = s.indexOf(s,"a");

+

s = s.clip();

+

s = s.toLowerCase();

+

s = s.toUpperCase();

+

</source>

+

| Many operations become part of the type ('''timestamp''', '''date''', '''string'''). Check out the online help. Or you can type . after the variable name to let Content Assist tell you what's available. String and Date has more operations available then in Rational Business Developer.

+

|-

+

| <source lang="java">

+

var money(8,2);

+

var num(8,2);

+

var bin(9);

+

</source>

+

| <source lang="java">

+

var decimal(8,2);

+

var decimal(8,2);

+

var decimal(9);

+

</source>

+

| '''money''', '''num''' &amp; '''bin''' are not supported, use '''decimal''' instead. Check '''EGL numeric types''' in online help for more details.

+

|-

+

| <source lang="java">

+

ServiceLib.convertFromJSON(json, eglType);

+

ServiceLib.convertToJSON(eglType any);

+

</source>

+

| <source lang="java">

+

JsonLib.convertFromJSON(json string,eglType);

+

JsonLib.convertToJSON(eglType any);

+

</source>

+

| The two methods are moved to JsonLib

+

|-

+

| <source lang="java">

+

call ... returning to ...

+

onException ServiceLib.serviceExceptionHandler;

+

</source>

+

| <source lang="java">

+

call ... returning to ...

+

onException myExceptionHandler;

+

</source>

+

| ServiceLib.serviceExceptionHandler is not in EDT, write your own ExceptionHandler. You can write a function name and press Ctrl+1 to let quick fix create the function for you.

+

|}

−

+

<br> '''Language elements not supported in EDT'''

+

*Called program

+

*DataItem

+

*Datatable

+

*Structured Record

+

*Form, FormGroup,

+

*DataTimeLib.currentTime, DateTimeLib.timeOf, DataTimeLib.timeValue

+

*Interval

+

*Move statement,

+

*maxSize, validValues,

+

*RuntimeException

[[Category:EDT]]

[[Category:EDT]]

Latest revision as of 00:20, 15 May 2012

An EDT project has a different layout than an Rational Business Developer project. The best way to make Rational Business Developer code work in EDT is to create a new EDT project and copy the code to it. There have also been some changes to the EGL language that may require you to change your code before it can be run with EDT. In addition to the information mentioned below, a high level overview of changes can be found on the Differences between EDT 0.7.0 and IBM Rational Business Developer page.

Move code to an EDT project

Create a new EDT project.

If the application contains RUI Handlers, choose either Web 2.0 client application or Web 2.0 client application with service depending on whether the application contains services.

If the application contains only Programs and common code, choose Basic.

Copy EGL files and packages from the Rational Business Developer project to the EDT project.

Configure the EGL Compiler and generators. The Compiler setting is a new feature in EDT which allows specifying generators for each package or file.

Select JavaScript Generator for Rich UI Handlers, Widgets and any common parts (Record, Library) which are referenced by Rich UI Handlers or Widgets.

Select Java Generator for Services, Programs and any common parts referenced by Services or Programs.

Common parts that require both JavaScript Generator and Java Generator should be put into a separate package configured with both Generators.

The compiler setting of a parent resource is inherited by the children, so setting at the package level is usually good enough.

Refactoring packages and code is sometimes necessary.

Modify EGL code

Use Organize Imports (Ctrl+Shift+O) to let EDT import the correct widgets and system parts. This is needed for almost all EGL files because of the package name changes.

Below is a handy list of things to modify. It is recorded when we moved Rational Business Developer samples and test apps to EDT. See the EGL Language conversion page for more information about updates to EGL. The Code snippets page is also a good place to find code.

Rational Business Developer

EDT

Comments

myInt int=3;
myInt int=null;

myInt int=3;
myInt int?=null;

In Rational Business Developer, you could set a non-nullable variable to null (in certain cases). This is not allowed in EDT. You must indicate the variable is nullable by using the ? See Nullability.

Many operations become part of the type (timestamp, date, string). Check out the online help. Or you can type . after the variable name to let Content Assist tell you what's available. String and Date has more operations available then in Rational Business Developer.

var money(8,2);
var num(8,2);
var bin(9);

var decimal(8,2);
var decimal(8,2);
var decimal(9);

money, num & bin are not supported, use decimal instead. Check EGL numeric types in online help for more details.