"Kevin A. Burton" <[EMAIL PROTECTED]> wrote: <snip> > The problem is that RunData allows the user to have access to the > Servlet API and this needs to be abstracted so that Jetspeed doesn't > have to be run in an Servlet env (like embeding it in another > application or running it "headless".). > > Is there anything you need within RunData other than the HTTP parameters > (via ParameterParser)? If not then you should be able to run your > Screens as Portlets just fine. No. We just take the parameters from the PortalConfig and put them in the run data via the ParameterParser. But we are calling: ElementContainer ec = ScreenLoader.getInstance().eval(data, "MyScreen"); which requires a RunData object. > If you need the ServletConfig or ServletRequest then it won't work. > This would require a code rework to just use ParameterParser. This > isn't a bad thing IMO as it allows you to run in a larger env. If you're not using RunData, how will portlets/portletcations interact with the session? If we need to set/get something in the session? Jeffrey D. Brekke mailto:[EMAIL PROTECTED] http://sites.netscape.net/ekkerbj/homepage ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
