If you're interested to, I've developed a WebPagePortlet using Neko Html Parser (in SAX mode), based on WebSurfPortlet. It rewrites urls, manage session and cookies, form submissions and so on. Right now it doesn't manage code stripping, like head or body removing, and it doesn't rewrite javascript urls.
I think it's better than the HtmlEditorKit, because it's not too strict parsing html files. I had no time to clean it and complete my implementation. If someone can dedicate 2 or 3 days to fix it, I can provide my code on this list... Let me know, Dariush. -----Original Message----- From: Glen Carl <[EMAIL PROTECTED]> To: Jetspeed Users List <[EMAIL PROTECTED]> Date: Tue, 17 Dec 2002 18:37:22 -0800 Subject: Re: WebPagePortlet, WebBrowserPortlet woes > Joe, > You may want to look at WebPagePortlet2 and WebPagePortlet in Jetspeed > 1.4b3. These probably fix some of the troubles you are having. > > In reqards to WebBrowserPortlet, you may have a configuration error. > Make sure you have set the proxy value to be the host and port where > your instance of jetspeed is running. Also, at this time, > WebBrowserPortlet has not been added to the Jetspeed build. It does > work > best with Jetspeed-1.4b*. Casey and I have an improved > WebBrowserPortlet, but it may take a few weeks to contribute the update > due to some paying client needs. > > Glen > > Joe Barefoot wrote: > > Hi all, > > > > After much experimentation with WebPagePortlet (Jetspeed 1.3), and > digging into source code, I must confess that I don't see how the > content it returns would render properly some of the time. It never > strips the <html> and <body> tags from the returned content, which > throws the browser (IE) off with about half the web sites I've tried. > I imagine other browsers would be even worse. > > > > > > So, after striking out with WebPagePortlet, I tried > WebBrowserPortlet, as the talk on the list had me thinking it had much > promise. > > As far as I can tell, it doesn't work properly at all: > > --The images do not come up, probably because their src attribute has > been re-written. > > --None of the links work at all, even with open_in_popup set to > yes--the page refreshes, but no change. > > --The pages that didn't render properly with WebPagePortlet also > didn't with WebBrowserPortlet. > > > > Is there a newer version of this portlet out there...is what I'm > seeing just an old bug? > > > > > > Anyone have an recommendations/workarounds? I mean, I can definitely > parse and remove the <html> and <body> tags myself, but it just seems > really, really weird that they aren't already removed. > > > > > > thanks in advance, > > Joe Barefoot > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
