brunp wrote:
OK......I appreciate the effort in trying to get answers, but I am also very
new to the entire Jetspeed process.
-> Does the portlet show up in the portlet selector?
There is no portlet selector in our system. The Jetspeed distribution is
pretty much the core (i.e., no additional libraries/pages beyond the
absolute minimum
--> Can you install it on a portal page without an exception being thrown?
I can not simply add a portal and see if it is installed correctly. Jetspeed
is part of a much larger product in which Jetspeed is simply a means to
incorporate pages from another website locations. I don't have the source
for those pages, just links to the webapp locations within Tomcat.
You can add a page that only includes the portlet in question. It does
not require any other portlets and does not affect the rest of the portal.
--> 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.
Nothing shows up in the console, and as there are no "WAR" files, nothing
really shows up. I do see the JAVA code within the Webapp being executed,
but the content does not show up....
When the portal starts, do you see the portlet's webapp being
initialized correctly? This should show up in Tomcat's log.
In what webapp is the errant portlet included?
How do you have webapps with no war files?
Can you post the evidence that you have that the appropriate methods
are being called in the portlet.
Can you log the result being returned to see what html is being generated.
-->Do you see the JSP(s) being compiled in the Tomcat /work directory?
The JSP's are pre-compiled @ build time.....
Not true.
Stop Tomcat, clear the /work directory and then see what shows up.
As for logs, this is another issue because no logs are produced based on the
Log4j.properties. No matter what I do and how I configure the properties
files, no logs are produced to: ${applicationRoot}/logs. I do see
JetspeedContainerServlet logs from within the tomcat logging infrastructure,
but nothing there indicates there is an issue or exception.
You need to get your logging setup so that you can debug.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
