One of the solutions that I was considering was to modify the php demo portlet. In the Class PHPApplicationPortlet. There is a refrence to a phpServletImpl = new com.itgroundwork.portlet.php.servlet(); I was thinking that I could just rewrite this class to extend the JavaBridge servlet provided by the php-java-bridge project.( http://php-java-bridge.sourceforge.net/) but I've been running into problems. one is that I can't find the source code for the com.itgroundwork.portlet.php package. its packaged in the phpportlet-1.0.jar. I tried reverse engeneering the class files, but the decompiler couldn't completely get the source back. if anyone has the source files I could try upgrading the php demo to support php5.
On 1/4/07, David Sean Taylor <[EMAIL PROTECTED]> wrote:
Aaron Evans wrote: > On 1/4/07, David Sean Taylor <[EMAIL PROTECTED]> wrote: >> >> I think the SSO solution in Jetspeed needs more testing and bug fixing. >> It does have a lot of potential. If we could get the IFrame portlet >> supporting the same authentication kinds as the WebContent, that would >> be a great start. >> > > David, > as an aside, I plan on making pretty heavy use of the SSOWebContent > portlet after we upgrade to 2.1, so I'll be more than happy to do more > testing and logging of bugs for it. ;-) > > -aaron Great, more bugs ;) I was just speaking with Roger about the PHP Portlet, and the advantages of using it over the WebContent or IFrame. He pointed out that the PHP portlet runs PHP inside of your Java application server, so you get the advantages running a single instance of PHP inside the application server, requiring less configuration and centralized administration. It also takes advantage of the load balancing provided by the application server. One thing that is missing is SSO functionality to the PHP portlet as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
