| Author |
PortletService in V5.0 results in NoClassDefFoundError
|
|
|
| I could not yet find any documentation on how to migrate 4.2 portlets to 5.0.
I attempted to deploy my PortletService as described in the infocenter:
Registering the service
To plug the service into the portal server, the corresponding class files must be copied to wp_root/shared/app. Then the PortletServiceRegistryService.properties file in the wp_root/shared/app/config/services directory must be changed:
I did so but always failed. The server logged a NoClassDefFoundError regarding my PortletService Interface. This PortletService ran successfully under 4.2.
However I managed to get it running by adding the required files to wps.jar. This is ugly of course but works.
Any comments?
| |
|
| I have been asked to more deeply explain the way I fixed the problem.
I assumed that at least wps.jar in folder WPS_HOME/shared/app will be loaded by Portal Server. Therefore I added my class files (which make up the Portal Server) to the archive wps.jar. As I said this is brute, but worked for me.
| |
|
| The solution can be found in the libraries.xml file located in {WAS_HOME}/config/cells/{my_cell_name}/nodes/{my_node_name}/.
All shared libraries are listed in it. Just add you lib and it should work. The best way to enter it would be adding a new entry under WPSlib:
<classPath>${WPS_HOME}/shared/app/my_jar.jar</classPath>
|
|
|
|