Bug 572162 - Unresolved requirement: Import-Package: javax.rmi
Summary: Unresolved requirement: Import-Package: javax.rmi
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.20   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-22 04:36 EDT by raviteja nama CLA
Modified: 2023-03-13 05:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description raviteja nama CLA 2021-03-22 04:36:06 EDT
Hi Team,

I have installed two plugins org.apache.axis2.eclipse.codegen.plugin_1.7.9 and org.apache.axis2.eclipse.service.plugin_1.7.9. After installing when i restart eclipse and check under new i can't see axis2 wizards. So i have opened eclipse in console and tried ss -axis2 and i see both the plugins status as installed, but when i try to start them using start command i get the below error.

org.osgi.framework.BundleException: Could not resolve module: org.apache.axis2.eclipse.codegen.plugin [998]
  Unresolved requirement: Import-Package: javax.rmi

org.osgi.framework.BundleException: Could not resolve module: org.apache.axis2.eclipse.service.plugin [999]
  Unresolved requirement: Import-Package: javax.rmi

Please help in resolving the issue

Thanks
Ravi
Comment 1 Wim Jongman CLA 2021-03-22 06:21:54 EDT
When the bundle has status INSTALLED, it cannot run. It means that dependencies are missing. When a bundle is installed and all the dependencies are resolved, then the bundle status will be set to RESOLVED. 

Starting bundles manually is almost never required.

I think you are running java 11 or higher. Java 11 no longer contains javax.rmi (JEP 320)

See [1] for a possible solution.

[1] https://stackoverflow.com/questions/56327632/java-11-and-jacorb-classnotfoundexception-javax-rmi-corba-stub
Comment 2 Eclipse Genie CLA 2023-03-13 05:14:27 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.