this is part of a product in which we upgraded to 2.1.3 just about a month
ago, so unfortunately, this is where we are at and the Jetspeed deployment
is a little unorthodox because the traditional portlet admin interfaces are
not installed, therefore, can't see the portlet selector, and there are no
"WAR" files. They are all JSP's.
The problem is that it used to work in Jetspeed 2.0 and then we migrated.
For the last question, there is no HTML source rendered within the Portlet
itself. I am also not sure if I can start anything in debug mode at all....
I unfortunately took over this development and am unfortunately stuck as the
traditional forms of debugging are not available to me.....
Paul
Ron McNulty wrote:
>
> Hi Paul
>
> Some simple tests are in order if you want help from the NG:
>
> - Does the portlet show up in the portlet selector?
> - Can you install it on a portal page without an exception being thrown?
> - When you first bring up the page (after refreshing the .war file), do
> you
> see any messages going past on the console? At minimum I would expect a
> "myapp.war installed successfully" or similar.
> - Do you see the JSP(s) being compiled in the Tomcat /work directory?
> - If you start Jetspeed in debug mode, do breakpoints on JSR168 entry
> points get hit? (doRender() in particular)
> - Does your Java code swallow exceptions?
> - Does a view source show any HTML generated by the portlet?
>
> With most people moving on to Jetspeed 2.2, help with 2.1.3 is going to
> diminish - can you upgrade to 2.2?
>
> Regards
>
> Ron
>
>
> ----- Original Message -----
> From: "brunp" <paul.b...@gmail.com>
> To: <jetspeed-user@portals.apache.org>
> Sent: Wednesday, July 15, 2009 3:31 AM
> Subject: Re: Portlet shows up "blank", no content
>
>
>>
>> can't be the only person to have encountered this, no???
>>
>> Paul
>>
>>
>> brunp wrote:
>>>
>>>
>>>
>>> Roberto Rossi-3 wrote:
>>>>
>>>> Have you seen the log file for error messages?
>>>>
>>>>
>>>
>>> That is my other problem....no error messages and it appears
>>> Log4j.properties has no affect. No specific logs are produced or sent
>>> to:
>>>
>>> ${applicationRoot}/logs/
>>>
>>> and of the logs that are included in our tomcat logs, nothing really
>>> shows
>>> up to let us know what could be the cause of the error.
>>>
>>> Paul
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Portlet-shows-up-%22blank%22%2C-no-content-tp24409649p24481933.html
>> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Portlet-shows-up-%22blank%22%2C-no-content-tp24409649p24498087.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
