portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <rwhee...@artifact-software.com>
Subject Re: Portlet shows up "blank", no content
Date Thu, 16 Jul 2009 16:31:25 GMT
Did you do the database conversions?

Ron

brunp wrote:
> I am unfortunately unable to post any file sets or code because this is part
> of a product line that is yet to be released. What real evidence am I
> supposed to look at here? 
>
> As for conversion.....all I did was update the Jetspeed binaries from 2.0 to
> 2.1.3. The migration to Jetspeed 2.1.3 also seems to mess up some of the
> styling too.....not sure why, but it does for some reason.....even in the
> same browser, but that is relatively easy to fix.....
>
> Paul
>
>
> ronatartifact wrote:
>   
>> see below.
>>
>> brunp wrote:
>>     
>>> Thanks for your input guys, but I have to say, there is no Portlet
>>> selector
>>> in the install base. The previous instance of Jetspeed 2.0 was just the 
>>> binaries. It was a custom install as part of a larger product
>>> distribution
>>> and
>>> to reduce disk space usage, all the unnecessary elements and I assume the
>>> jetspeed admin interface was stripped from the distribution. I am just
>>> stipulating
>>> what I know at this point in time. 
>>>
>>> The portlet in question does have a portlet.xml file and I have no idea
>>> if
>>> the application follows JSR 168 specification as I didn't create it
>>> myself.
>>> As I 
>>> had mentioned, the pages work on their own, but when absorbed within the
>>> jetspeed collective, it doesn't. 
>>>
>>> I wish I can say more.....I wish I knew more....but I have been stuck
>>> with
>>> this
>>> development. :-)
>>>
>>> This particular portlet does have a WAR file, and the others that do not
>>> appear
>>> to work as they have the portlet.xml specification in the WEB-INF
>>> directory.
>>>
>>> Thanks again....guess I am on my own on this one.
>>>
>>>   
>>>       
>> Don't give up so easily.
>> You are getting good help.
>> You need to start posting more real evidence.
>> Give more details about the structure of the applications and some of 
>> the relevant configuration files.
>> That will lead to more definite questions and suggestions.
>>
>> You might also review your conversion steps to make sure that you 
>> actually followed each of the required steps.
>>
>> Ron
>>
>>     
>>> Paul
>>>
>>>   
>>>       
>>     
>>> Eva Petro wrote:
>>>   
>>>       
>>>> 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.brun@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-unsubscribe@portals.apache.org
>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>
>>>>>       
>>>>>           
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>>
>>>>
>>>>     
>>>>         
>>>   
>>>       
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>>     
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org


Mime
View raw message