[CS Tan]

We hv been using Myeclipse Version: 2019.12.5 Build id: 16.0.0-20191205 with WAS 8.5.5. Base edition (FP15).

We encountered some problems when we install WAS 8.5.5. Express edition (FP18). The other changes are:
a) Installation on a new folder. In the configuration of a new WAS, we point it to the new folder for AppServ01.
b) And configuration uses the computer name as the hostname instead of the IP address.

We notice when we check out a new workspace, there was a small prompt to migrate the EJB Project. Which was handled automatically without any drama.

There are a number of problem on the console…

1) Problems with Java

Access restriction: The constructor ‘Base64()’ is not API (restriction on required library ‘C:\IBM_WAS\WebSphere\AppServer\java\jre\lib\xml.jar’)
SB_UtilityBean.java /BelsizeEJB/ejbModule/com/belsize/sb line 3497 Java Problem

BeanTaskInfo cannot be resolved to a type SB_ScheduleTaskBean.java /BelsizeEJB/ejbModule/com/belsize/sb line 192 Java Problem
com.ibm.websphere.scheduler cannot be resolved to a type SB_ScheduleTaskBean.java /BelsizeEJB/ejbModule/com/belsize/sb line 82 Java Problem
Scheduler cannot be resolved to a type SB_ScheduleTaskBean.java /BelsizeEJB/ejbModule/com/belsize/sb line 83 Java Problem
The import com.ibm.ejs cannot be resolved SB_UtilityBean.java /BelsizeEJB/ejbModule/com/belsize/sb line 92 Java Problem`

2) Server wouldn’t start in debug mode and I received this prompt.

Server WebSphere Application Server 8.5 at localhost failed to start.

runConfigActions script execution failed. Exit code: 1
Exception caught while waiting for runConfigActions script to complete: C:\IBM_WAS\WebSphere\AppServer\profiles\AppSrv01\bin\runConfigActions.bat

Can some one help

[support-swapna]

Hi,

Sorry that you are seeing issues post migrating to WAS newer version.

Firstly, we have a known issue with starting newer version of WAS from within MyEclipse. The workaround is to create a file named runConfigActions.disableAtServerStartup (empty file) under the [profile_root]/properties/service/ directory and then try starting the server from within the IDE.

Alternatively, you can start the WAS instance externally via startServer.bat from a command prompt. The MyEclipse console will detect the running instance and you can deploy your app and stop the server from the MyEclipse’s Servers view.

About the problems reported with Java, it looks like your code is pointing to a deprecated or restricted API. You can either replace the code or change the error level to ‘warning’ as suggested in this article : https://mkyong.com/java/access-restriction-the-type-base64encoder-is-not-accessible-due-to-restriction/

Hope this helps. Please let us know how you get on with it.

–Swapna
Genuitec Support

[CS Tan]

Thanks Swapna! The server seems to be starting fine now. And we will dial down the error level to warning.

[CS Tan]

Hi Swapna,

I still have a few errors on the WAS Express 8.5.5 FP18. What can I do.

Resolve to a type error
======================
1) BeanTaskInfo cannot be resolved to a type
2) com.ibm.websphere.scheduler cannot be resolved to a type
3) Scheduler cannot be resolved to a type
4) SelectItem cannot be resolved to a type
5) TaskHandler cannot be resolved to a type
6) TaskHandlerHome cannot be resolved to a type
7) TaskInfo cannot be resolved to a type
8) TaskStatus cannot be resolved to a type
9) Uuid cannot be resolved to a type

Cannot be resolved
=================
9a)The import com.ibm.ejs cannot be resolved
10)The import com.ibm.json cannot be resolved
11) The import com.ibm.websphere.scheduler cannot be resolved
12) The import com.ibm.ws.webservices cannot be resolved
13) The import javax.faces cannot be resolved

Inherited abstract method
=========================
14) The type SB_ScheduleTaskBean must implement the inherited abstract method SB_ScheduleTaskLocal.process(TaskStatus)
15) The type SB_ScheduleTaskBean must implement the inherited abstract method SB_ScheduleTaskLocal.processTask(TaskStatus)
15) The type SB_ScheduleTaskBean must implement the inherited abstract method SB_ScheduleTaskLocal.task_11491000(TaskStatus)
16) The type SB_ScheduleTaskBean must implement the inherited abstract method SB_ScheduleTaskRemote.process(TaskStatus)

[support-swapna]

Hi,

Sorry that you are seeing these errors.

Are you seeing them during deployment? It looks like some of the dependencies are missing. Can you please recheck the compiler version and also check if any quick fix is available in case the errors are reported in the editor area?

If you are still seeing issues, then please share the deployment log to help us get the full list of the errors.

–Swapna
Genuitec Support

[CS Tan]

Hi Swapna,

good news again. I just clean the project and it seems all the error disappeared.

We are using Myeclipse Version: 2019.12.5. Which we find stable for our use. Would a later version have a better performance? Or any other advantages?

CS

[support-swapna]

CS,

Glad that you are all set.
The newer version of MyEclipse is based on Eclipse 2020-06 including Java 14 support and we have also upgraded the frameworks and their versions.
Please see the delivery log for more details about the fixes/enhancements that went into the releases post 2019.12.5 : https://www.genuitec.com/products/myeclipse/deliverylog/ci/

There haven’t been any particular performance improvements apart from one ‘No more handles’ issue with dark theme on Windows. We recommend you stay updated on the version to take advantage of the fixes and enhancements made.

Hope this helps. Please let us know if you have any further questions.

–Swapna
Genuitec Support

[Author]

Posts