Hi Paul
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
In my experience, it is pretty much impossible to install Jetspeed 2.1.3
without the portal selector. The minimal installation includes it, as it is
an essential tool.
- Log in as admin
- Select the modify page icon
- Click "Add portlet"
That will put you in the portlet selector. Portlets that are properly
configured and ready for use will show up in this screen. To add a portlet,
click on the Add link for the portlet. You can add one or more instances to
the page (the count field shows how many). Click the green back arrow next
to the search box when done.
Also, debugging is pretty easy - very similar to debugging a standard J2EE
app. Jetspeed is simply a J2EE application that runs inside Tomcat. The
trick is to start Tomcat from inside Eclipse:
- Create a project in Eclipse that includes all your portlet source.
- Make sure all the portlet source code is on the Java source path, and
compiles without errors.
- Download and install the Tomcat plugin for Eclipse
- Configure the plugin to point to the Jetspeed base directory (typically
C:\Apache\Jetspeed-2.1.3 on Windows)
- Start Tomcat from the start icon
- Put breakpoints in interesting places
- Open a browser on Jetspeed, and the breakpoints will be hit when
executed.
You can also start Jetspeed (well Tomcat to be exact) externally in debug
mode and connect Eclipse as a remote debugger. This is covered in the
Eclipse and Tomcat documetation.
Getting a debugging environment going is an essential part of
troubleshooting J2EE applications. If you are unfamiliar with this, take a
day or two to come up to speed. It will pay back your time investment many
times over.
As Ron Wheeler said, it is hard to imagine how you can have portlets without
corresponding portlet application .war files. JSR168 mandates this. Some
thoughts:
- Are you sure your Jetspeed 2.0 code is playing by the JSR168 rules?
- Perhaps what you have is just a Tomcat installation without portlets?
- If you have not installed .war files into Jetspeed 2.1.3, then results
could be indeterminate. Jetspeed consumes the .war, and installs any
portlets it finds in it. These need to have valid descriptors in the
portlet.xml file. Without a portlet.xml, there are no portlets, so
displaying nothing sounds quite reasonable.
Best of luck...
Regards
Ron
----- Original Message -----
From: "brunp" <paul.b...@gmail.com>
To: <jetspeed-user@portals.apache.org>
Sent: Thursday, July 16, 2009 2:55 AM
Subject: Re: Portlet shows up "blank", no content
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.
--> 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....
-->Do you see the JSP(s) being compiled in the Tomcat /work directory?
The JSP's are pre-compiled @ build time.....
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.
Paul
--
View this message in context:
http://www.nabble.com/Portlet-shows-up-%22blank%22%2C-no-content-tp24409649p24499665.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
