Return-Path: Delivered-To: apmail-portals-jetspeed-dev-archive@www.apache.org Received: (qmail 24764 invoked from network); 26 Feb 2007 04:41:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Feb 2007 04:41:48 -0000 Received: (qmail 21572 invoked by uid 500); 26 Feb 2007 04:41:56 -0000 Delivered-To: apmail-portals-jetspeed-dev-archive@portals.apache.org Received: (qmail 21540 invoked by uid 500); 26 Feb 2007 04:41:56 -0000 Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@portals.apache.org Received: (qmail 21527 invoked by uid 99); 26 Feb 2007 04:41:56 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Feb 2007 20:41:56 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [209.86.89.63] (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Feb 2007 20:41:44 -0800 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=jmwq8W0xWkri0modbqARoJqKbXUk3jh0GuC+NNDr+N7GX/ci6twzp0NvAYLM053+; h=Received:Message-ID:Date:From:Reply-To:User-Agent:X-Accept-Language:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [68.164.170.126] (helo=[192.168.1.34]) by elasmtp-junco.atl.sa.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1HLXfv-0005Ol-4S; Sun, 25 Feb 2007 23:41:23 -0500 Message-ID: <45E264E5.6030509@earthlink.net> Date: Sun, 25 Feb 2007 20:41:09 -0800 From: Roger Ruttimann Reply-To: roger.ruttimann@earthlink.net User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cyrus Keong CC: Jetspeed Developers List Subject: Re: Apache perl portal bridge References: <45E2072C.2020505@its.monash.edu.au> In-Reply-To: <45E2072C.2020505@its.monash.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 896bf647e3c9dc9f78faf5d9b9bdf34bd780f4a490ca69563f9fea00a6dd62bcd1119d35056d604e0a31f989fd862beb350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.164.170.126 X-Virus-Checked: Checked by ClamAV on apache.org The sample is the simplest possible script: just an html wrapped into a perl call. You can include any perl code even have multiple perl script in the same directory referencing each other. We have tested the perl bridge in production and we were able to run a web based network configuration program in a portlet (including a lot of Java script). The perl bridge replaces relative links to portlet actions so that the navigation remains in the same portlet and not opening a new window. As I mentioned before just include your perl code without modifications in the perl bridge and access it from the portal. Roger Cyrus Keong wrote: > my name is Cyrus from DART(dart.edu.au), i have some questions about > your perl bridge. in the example there are two files: perl-demo.cgi and > perl-demo-2.cgi, however they are not perl script cgi files, > they just a HTML file. can you give me more information about how the > bridge can be used to put perl cgi script into portlet? > --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org For additional commands, e-mail: jetspeed-dev-help@portals.apache.org