Stefan Weinert wrote:
I had the same error (or to be honest it was one of the many errors I came accross) and through the many reinstallations I too chose the j2 directory to ease navigation which solved this problem without me knowing what fixed it.
Well that particular bug needed to be at least in the release notes We missed it
There are lots of portlets not being initialized porperly with the demo portal though.
That usually occurs because you hit the portal site too soon The very first initialization is very slow depending on your machine
Is there a common practise in 'debugging' these errors in J2. As a noob I'd rather be pointed to a checklist than asking for each error. I understand JSR168 being a powerfull standard which not only allows standard definition of portlets but should allow standard debugging.
I use Eclipse to remote debug
So what are the common steps you (aka the pros) go through when coming accross a "Failed to retrieve Portlet Definition for XYZ" message?
Check the jetspeed.log file, see what went wrong Also check the catalina.out --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
