.comment-link {margin-left:.6em;}

J. Daniel Ashton

www.flickr.com
This is a Flickr badge showing public photos from jdashton. Make your own badge here.
Whatever your hand finds to do, do it with all your might, —Ecclesiastes 9:10a NIV
The LORD God has told us what is right and what he demands:
"See that justice is done,
let mercy be your first concern,
and humbly obey your God." —Micah 6:8, CEV
With all your heart you must trust the LORD and not your own judgment.
Always let Him lead you, and He will clear the road for you to follow. —Proverbs 3:5,6 CEV

see also — My Homepage

My Photo
Name: Daniel Ashton
Location: Germantown, Maryland, United States


Any links with a dashed underscore probably point to Amazon.com

Friday, July 14, 2006

Rough Draft of findings on some work stuff

This is one of those little things that drives a newbie crazy. I'm working in RSA (Rational Software Architect), and I create a new portlet project. After taking various actions I try to run my new portlet on one of the WebSphere Portal Test Environments. The portlet dumps a stack trace and displays the RMOD (red message of death).

Analysis of the console log yields messages about an invalid context root or invalid root context. It appears that the correct action to take is to go into the project's Properties (click on the project and press Alt-Enter) and the J2EE page. On this page you can change the Context Root and propagate the change to "links that reference the context root".

I initially suspected that the problem was something to do with the actual content of this entry: perhaps it's OK to have a context root that starts with a period, or with a capital letter, or not. However, at present all options seem to be accepted.

So, it would appear that using this properties page to make the change is a sufficient remedy for this problem.

By the way, I see the following behavior after changing the root. 1) I try to run the portlet on the server TE, and it displays nothing at all, not even the RMOD. 2) I restart the server TE, and all is well.

I'm beginning to suspect that restarting a portal server will not fix an RMOD, but it is the most likely way to fix a portlet with no body, at least for WebSphere Portal v5.0 Test Environment.

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home