If they are different, either update the ear POM file, or set the or the build/finalNameproperty in webapp module POM to update the webapp project settings/.component file. Solution - check the webapp project settings/.component file, ensure the context-root property of wb-module has the same value as the contextRoot defined in the ear maven-ear-plugin. 1) IBM Rational® Application Developer version 8.5 2) IBM WebSphere® Portal and Web Content Manager V8.0 On skill level, you should know how to work with IBM Rational Application Developer and portlet development to simplify the process of project creation. ![]() Issue - Run/Debug the portlet on Server shows error EJPPG0024I: Web application with context root XXX is deployed in the application server but not registered with portal. This can be achieved by two different ways.ġ) In ear module POM file, add the build/finalName property, and set the value as the ear module artifactId,Ģ) During the project import, use the - Name template in Advanced setting. ![]() Solution - check the ear project settings/.component file, ensure the deploy-name attribute of wb-module has the same value as the Eclipse project name. Issue - Open WebSphere Application Deployment for the EAR project shows error Could not open the editor: An unexpected exception was thrown. maven-ear-plugin 2.6 5 $ demo-webapp MavenDemoPortlet Solution - ensure in the ear module POM file, the maven-ear-plugin/configuration/version property is set to 5 or up. ![]() Issue - The EAR project popup menu doesn't show the option Open WebSphere Application Deployment Congratulations! now you have set up a Maevn based portlet development environment in RAD.
0 Comments
Leave a Reply. |