Portal Application Laboratory

N2 Collabo

2008-12-30T17:08:00.002+09:00

N2 Collabo provides Groupware and Collaboration features as JSR 168 compliant portlet. These portlets are developed by Portal Application Laboratory project. N2 Collabo runs on JSR 168 compliant Portal Server, such as Jetspeed 2, Liferay, and JBoss Portal. N2 Collabo Community Edition is free to download and use under Apache license. N2 Collabo contains the following components:

Scheduler
Address List
Facilities Management
Message Board
Timecard
TODO List
Bookmark
Chat
Notepad
Google Gadgets
Netvibes Widgets
Virtual File System (VFS)
User Management

It is much appreciated if you can provide any feedback and contribution to us.

Netvibes Widgets Portlet 1.0 Released

2008-09-25T08:29:00.000+09:00

Netvibes Widget Portlet enables you to display Netvibes Widgets on your portlet.

Step to run it
1) Get netvibes-widgets.war
2) Deploy netvibes-widgets.war(for the detail, see portal server's document)
3) Select a widget you want to use on EDIT mode.

Google Gadgets Portlet 1.0 Released

2008-09-25T08:24:00.000+09:00

Google Gadgets Portlet enables you to display Google Gadgets on your portlet.

Step to run it
1) Get googlegadgets.war
2) Deploy googlegadgets.war(for the detail, see portal server's document)
3) Select a gadget you want to use on EDIT mode.

PAL Portal 1.1 Released

2008-09-25T08:17:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, features are:

New Logging System
Improved WCM
New Site Management System
SEO support
Improved Page Design(using jQuery 1.2)
A lot of bug fixes

It is much appreciated if you can provide any feedback to us.

Download from: PAL Portal 1.1

How to install:

Note: Before running PAL Portal, you will need to install
Java SDK(1.5.x or later) and set environment JAVA_HOME
properly.

1. Download PALPortal-1.1-installer.jar
2. Run installer
Open command shell, or DOS command box, type:
$ java -jar PALPortal-1.1-installer.jar
You will see the installer executed. (Don't type '$')
3. Execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display
PAL Portal. To login as an administrator, you can use
admin/admin as Username/Password. To modify default pages,
create a use with siteadmin role and then edit pages
in /__subsite-root.

How to deploy PALab's portlets:

1. Login as admin
2. Navigate to Root >> Portal Administration >> Portlet Management
3. Click Deploy link you want to deploy

How to uninstall:

1. Delete the install directory,

PAL Portal 1.0.5 Released

2008-06-16T06:38:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, features are:

Bug fixes
Supported PSML in DB
Cluster support
Improved logging
Improved SSL page handling
Improved SSO features
Code cleanup

It is much appreciated if you can provide any feedback to us.

Download from: PAL Portal 1.0.5

How to install:

Note: Before running PAL Portal, you will need to install
Java SDK(1.5.x or later) and set environment JAVA_HOME
properly.

1. Download PALPortal-install-1.0.5.jar
2. Run installer
Open command shell, or DOS command box, type:
$ java -jar PALPortal-install-1.0.5.jar
You will see the installer executed. (Don't type '$')
3. Execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display
PAL Portal. To login as an administrator, you can use
admin/admin as Username/Password. To modify default pages,
use site/site as Site manager.

How to deploy PALab's portlets:

1. Login as admin
2. Navigate to Root >> Portal Administration >> Portlet Management
3. Click Deploy link you want to deploy

How to uninstall:

1. Delete the install directory,

PAL Portal 1.0.4 Released

2008-04-07T09:06:00.001+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, features are:

Bug fixes
Added UserManagerServlet to do a batch processing for user info.

It is much appreciated if you can provide any feedback to us.

Download from: PAL Portal 1.0.4

How to install:

Note: Before running PAL Portal, you will need to install
Java SDK(1.5.x or later) and set environment JAVA_HOME
properly.

1. Download PALPortal-install-1.0.4.jar
2. Run installer
Open command shell, or DOS command box, type:
$ java -jar PALPortal-install-1.0.4.jar
You will see the installer executed. (Don't type '$')
3. Execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display
PAL Portal. To login as an administrator, you can use
admin/admin as Username/Password. To modify default pages,
use site/site as Site manager.

How to deploy PALab's portlets:

1. Login as admin
2. Navigate to Root >> Portal Administration >> Portlet Management
3. Click Deploy link you want to deploy

How to uninstall:

1. Delete the install directory,

How to configure PAL Portal and OpenSSO

2008-04-01T10:20:00.002+09:00

PAL Portal supports OpenSSO by putting PAL's OpenSSOFilter to web.xml. If you use Jetspeed2, you can apply the same procedure to your J2. The procedure is below:

1. Setup OpenSSO.
2. Download palportal-sso-2.1.3_pal-1.0.3.jar and openssoclientsdk.jar, and copy them to webapps/palportal/WEB-INF/lib/.
3. Edit webapps/palportal/WEB-INF/web.xml


...
  <filter>
    <filter-name>OpenSSOFilter</filter-name>
    <filter-class>jp.sf.pal.portal.sso.opensso.OpenSSOFilter</filter-class>
    <init-param>
      <param-name>loginURL</param-name>
      <param-value>http://servername:8080/opensso</param-value>
    </init-param>
  </filter>
...
  <filter-mapping>
    <filter-name>OpenSSOFilter</filter-name>
    <url-pattern>/*</url-pattern>
  </filter-mapping>
...

How to manage user data by a remote access

2008-04-01T09:25:00.001+09:00

If you want to manage user data by a remote access on PAL Portal, you can use UserManagerServlet(If you use Jetspeed2, download UserManagerServlet.class).

An usage is simple. Please put the servlet information to web.xml:

  <servlet>
   <servlet-name>UserManagerServlet</servlet-name>
   <servlet-class>jp.sf.pal.portal.servlet.UserManagerServlet</servlet-class>
 </servlet>

 <servlet-mapping>
   <servlet-name>UserManagerServlet</servlet-name>
   <url-pattern>/userManager</url-pattern>
 </servlet-mapping>

and then access http://localhost:8080/palportal/userManager?name1=value1&... UserManagerServlert has the following features:

Check a user authentication

Add a user

Update a password

Delete a user

An example of an output format is below:

<?xml version="1.0" encoding="UTF-8" ?>
<results>
 <status>string</status>
 <message>string</message>
 <result>
   <name>string</name>
   <value>string</value>
 </result>
</results>

Check a user authentication

Parameters passed on URL:
[Request Parameters]="Value"
action=authenticate
username="User name"
password="Password"

Value of "status":
success -> Success!
authentication-failed -> Authentication failed.
invalid-parameter -> Invalid request parameter(s).
excluded-user -> a given user name is excluded.

Add a user

Parameters passed on URL:
[Request Parameters]="Value"
action=create
username="Username"
password="Password"

Value of "status":
success -> Success!
user-already-exists -> User already exists.
server-error -> Server error.
invalid-parameter -> Invalid request parameter(s).
excluded-user -> a given user name is excluded.

Update a password

Parameters passed on URL:
[Request Parameters]="Value"
action=update
username="User name"
password="Password"

Value of "status":
success -> Success!
user-not-found -> User not found.
server-error -> Server error.
invalid-parameter -> Invalid request parameter(s).
excluded-user -> a given user name is excluded.

Delete a user

Parameters passed on URL:
[Request Parameters]="Value"
action=update
username="User name"
password="Password"

Value of "status":
success -> Success!
user-not-found -> User not found.
server-error -> Server error.
invalid-parameter -> Invalid request parameter(s).
excluded-user -> a given user name is excluded.

How to setup PAL Portal(Jetspeed2) on GlassFish 2ur1

2008-04-01T08:52:00.001+09:00

An procedure about how to configure PAL Portal on GlassFish is below. Since PAL Portal is based on Jetspeed 2, if you want to setup J2 on GlassFish, you can refer the procedure. First of all, you need to download jetspeed-portal-glassfish.zip and jetspeed-security-glassfish-2.1.3_pal-1.0.3.jar, and then unzip jetspeed-portal-glassfish.zip to [palportal_home]/webapps/palportal/WEB-INF/classes.
The procedure is(if you apply it to j2, replace palportal with jetspeed and skip some steps):

$ java -Xmx256m -jar /tmp/glassfish-installer-v2ur1-b09d-linux.jar
$ mv glassfish/ glassfish-v2ur1
$ cd glassfish-v2ur1/
$ chmod -R +x lib/ant/bin
$ lib/ant/bin/ant -f setup.xml
$ cp /tmp/Portal/shared/lib/jetspeed-* domains/domain1/lib/
$ cp /tmp/Portal/shared/lib/p* domains/domain1/lib/
$ cp -r /tmp/Portal/webapps/palportal webapps/
$ vi webapps/palportal/WEB-INF/assembly/security-providers.xml
      <!--constructor-arg index="2"><value>login.conf</value></constructor-arg-->
      <constructor-arg index="2"><ref bean="org.apache.jetspeed.security.spi.CredentialHandler"/></constructor-arg>
      <constructor-arg index="3"><ref bean="org.apache.jetspeed.security.spi.UserSecurityHandler"/></constructor-arg>
$ vi domains/domain1/config/login.conf
Jetspeed {
  org.apache.jetspeed.security.impl.GlassFishLoginModule required;
};
$ vi webapps/palportal/WEB-INF/assembly/deployment.xml
<!--
 <bean id="org.apache.jetspeed.tools.pamanager.servletcontainer.ApplicationServerManager"
      class="org.apache.jetspeed.tools.pamanager.servletcontainer.TomcatManager"
      init-method="start" destroy-method="stop"
 >
      <constructor-arg index="0"><value>${autodeployment.catalina.base}</value></constructor-arg>
      <constructor-arg index="1"><value>${autodeployment.catalina.engine}</value></constructor-arg>
      <constructor-arg index="2"><value>${autodeployment.server}</value></constructor-arg>
      <constructor-arg index="3"><value>${autodeployment.port}</value></constructor-arg>
      <constructor-arg index="4"><value>${autodeployment.user}</value></constructor-arg>
      <constructor-arg index="5"><value>${autodeployment.password}</value></constructor-arg>
 </bean>
-->
<bean id="org.apache.jetspeed.tools.pamanager.servletcontainer.ApplicationServerManager"
     class="org.apache.jetspeed.tools.pamanager.servletcontainer.GlassFishManager"
     init-method="start" />
$ vi webapps/palportal/WEB-INF/assembly/portal-url-generation.xml
 <bean id="PortalURL"
      class="org.apache.jetspeed.container.url.impl.GlassFishPathInfoEncodingPortalURL"
$ cp /tmp/jetspeed-security-glassfish-2.1.3.jar domains/domain1/lib/
$ pushd domains/domain1/lib/classes/
$ jar xvf ../jetspeed-security-glassfish-2.1.3.jar
$ rm -r META-INF/
$ mkdir -p ../../../../webapps/palportal/WEB-INF/classes/org/apache/jetspeed/security/impl/
$ mv ./org/apache/jetspeed/security/impl/GlassFishLoginModule.class ../../../../webapps/palportal/WEB-INF/classes/org/apache/jetspeed/security/impl/
$ rm ../jetspeed-security-glassfish-2.1.3.jar
$ popd
$ cp /tmp/mysql-connector-java-5.0.4.jar domains/domain1/lib/
$ vi domains/domain1/config/domain.xml
     <java-config classpath-suffix="${com.sun.aas.instanceRoot}/lib/classes" ...
$ ./bin/asadmin start-domain domain1
$ echo adminadmin > passwordfile
$ ./bin/asadmin create-auth-realm --classname org.apache.jetspeed.security.impl.GlassFishRealm --user admin --passwordfile passwordfile --host localhost --port 4848 --property "jaas-context=Jetspeed:auth-type=jetspeed" Jetspeed
$ ./bin/asadmin stop-domain domain1
$ ./bin/asadmin start-domain domain1
-> Create Connection Pool(JetspeedDSPool) and JDBC Resource(jdbc/jetspeed)
$ ./bin/asadmin deploydir --user admin --passwordfile passwordfile webapps/palportal/
$ pushd webapps/
$ mkdir pal-admin
$ mkdir pal-wcm
$ cd pal-admin
$ jar xvf ../pal-admin.war
$ cd ../pal-wcm
$ jar xvf ../pal-wcm.war   
$ popd
$ rm webapps/pal-admin/WEB-INF/lib/geronimo-ejb_2.1_spec-1.0.jar
$ ./bin/asadmin deploydir --user admin --passwordfile passwordfile webapps/pal-admin
$ ./bin/asadmin deploydir --user admin --passwordfile passwordfile webapps/pal-wcm

PAL Portal 1.0.3 Released

2008-03-07T17:28:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, features are:

Supported JBoss AS
Supported WebLogic Server
Supported GlassFish

It is much appreciated if you can provide any feedback to us.

Download from: PAL Portal 1.0.3

How to install:

Note: Before running PAL Portal, you will need to install
Java SDK(1.5.x or later) and set environment JAVA_HOME
properly.

1. Download PALPortal-install-1.0.3.jar
2. Run installer
Open command shell, or DOS command box, type:
$ java -jar PALPortal-install-1.0.3.jar
You will see the installer executed. (Don't type '$')
3. Execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display
PAL Portal. To login as an administrator, you can use
admin/admin as Username/Password. To modify default pages,
use site/site as Site manager.

How to deploy PALab's portlets:

1. Login as admin
2. Navigate to Root >> Portal Administration >> Portlet Management
3. Click Deploy link you want to deploy

How to uninstall:

1. Delete the install directory,

How to setup PAL Portal(Jetspeed2) on JBoss AS 4.0.5 GA

2008-02-15T16:36:00.001+09:00

I installed PAL Portal on JBoss AS 4.0.2. Since PAL Portal is Jetspeed2 base portal, I think that the configuration is the same as Jetspeed2. The installation step is below:

$ cd /tmp
$ unzip /tmp/jboss-4.0.5.GA.zip
$ cd jboss-4.0.5.GA/
$ cp -r ../PALPortal/webapps/palportal/ server/default/deploy/palportal.war
$ cp ../PALPortal/shared/lib/*.jar server/default/lib/
$ cp -r ../PALPortal/database/ .
$ vi server/default/deploy/palportal-ds.xml
<datasources>
<local-tx-datasource>
  <jndi-name>/JetspeedDS</jndi-name>
  <connection-url>jdbc:derby:/tmp/jboss-4.0.5.GA/database/derby/productiondb;create=true</connection-url>
  <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
  <user-name></user-name>
  <password></password>
  <min-pool-size>5</min-pool-size>
  <max-pool-size>20</max-pool-size>
  <idle-timeout-minutes>0</idle-timeout-minutes>
</local-tx-datasource>
</datasources>
$ vi ./server/default/deploy/palportal.war/WEB-INF/assembly/deployment.xml
<!--
  <bean id="org.apache.jetspeed.tools.pamanager.servletcontainer.ApplicationServerManager"
       class="org.apache.jetspeed.tools.pamanager.servletcontainer.TomcatManager"
       init-method="start" destroy-method="stop"
  >
       <constructor-arg index="0"><value>${autodeployment.catalina.base}</value></constructor-arg>
       <constructor-arg index="1"><value>${autodeployment.catalina.engine}</value></constructor-arg>
       <constructor-arg index="2"><value>${autodeployment.server}</value></constructor-arg>
       <constructor-arg index="3"><value>${autodeployment.port}</value></constructor-arg>
       <constructor-arg index="4"><value>${autodeployment.user}</value></constructor-arg>
       <constructor-arg index="5"><value>${autodeployment.password}</value></constructor-arg>
  </bean>
-->
<bean id="org.apache.jetspeed.tools.pamanager.servletcontainer.ApplicationServerManager"
      class="org.apache.jetspeed.tools.pamanager.servletcontainer.JBossManager"
      init-method="start" />
$ rm server/default/deploy/palportal.war/WEB-INF/lib/commons-logging-*.jar
$ rm server/default/deploy/palportal.war/WEB-INF/lib/log4j-*.jar
$ vi server/default/deploy/palportal.war/WEB-INF/web.xml
<!--
  <listener>
    <listener-class>org.apache.jetspeed.webapp.logging.Log4JConfigurator</listener-class>
  </listener>
-->
$ vi server/default/deploy/palportal.war/WEB-INF/jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
  <class-loading>
    <loader-repository java2ClassLoadingCompliance="false">
      org.apache.jetspeed:loader=palportal.war<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
    </loader-repository>
  </class-loading>
  <security-domain flushOnSessionInvalidation="true">java:/jaas/Jetspeed</security-domain>
  <resource-ref>
    <res-ref-name>jdbc/jetspeed</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <jndi-name>java:/JetspeedDS</jndi-name>
  </resource-ref>
</jboss-web>
$ vi server/default/conf/login-config.xml
    <application-policy name="Jetspeed">
      <authentication>
        <login-module code="org.apache.jetspeed.security.impl.ext.JBossLoginModule"
          flag="required">
          <module-option name="unauthenticatedIdentity">guest</module-option>
        </login-module>
      </authentication>
    </application-policy>
$ pushd server/default/deploy/palportal.war/WEB-INF/deploy/
$ for warfile in `find . -type f|grep war`; do tfile=`zipnote $warfile|grep commons-logging|sed -e "s/@ //"`;if [ ! x$tfile = "x" ] ; then zip -d $warfile $tfile; fi; done
$ for warfile in `find . -type f|grep war`; do tfile=`zipnote $warfile|grep log4j|sed -e "s/@ //"`;if [ ! x$tfile = "x" ] ; then zip -d $warfile $tfile; fi; done
$ popd
$ ./bin/run.sh

PAL Portal 1.0.2 Released

2008-01-22T14:23:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, features are:

Based on Jetspeed 2.1.3
New UI (Drag and Drop layout)
New installer
Dropped j2-admin
Dropped J2 Desktop(and Dojo)

It is much appreciated if you can provide any feedback to us.

Download from: PAL Portal 1.0.2

How to install:

Note: Before running PAL Portal, you will need to install
Java SDK(1.5.x or later) and set environment JAVA_HOME
properly.

1. Download PALPortal-install-1.0.2.jar
2. Run installer
Open command shell, or DOS command box, type:
$ java -jar PALPortal-install-1.0.jar
You will see the installer executed. (Don't type '$')
3. Execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display
PAL Portal. To login as an administrator, you can use
admin/admin as Username/Password. To modify default pages,
use site/site as Site manager.

How to deploy PALab's portlets:

1. Login as admin
2. Navigate to Root >> Portal Administration >> Portlet Management
3. Click Deploy link you want to deploy

How to uninstall:

1. Delete the install directory,

Google Gadgets Portlet 0.3 Released

2007-07-02T08:54:00.000+09:00

Google Gadget portlet was updated. A portlet was separated by a category.

To deploy this portlet:
1) Download googlegadgets-*.war
2) Deploy googlegadgets-*.war(For how to deploy portlet, see portal server's document)

PAL WCM Portlet 0.1 released

2007-05-28T10:23:00.000+09:00

In Jetspeed, if you want to edit a content on portlet by WYSIWYG HTML editor, try this portlet. PAL WCM Portlet provides a feature of Web Content Management. You can deploy this portlet by RPAD after logging in to Jetspeed as admin, or you can also download it from http://sourceforge.jp/projects/pal/files/?release_id=25347#25347.

PAL Portal 1.0 Beta 5 Released

2007-05-15T17:27:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides. In this release, PAL-Admin and PAL-WCM portlets are contained. PAL-Admin portlet has User Management and Portlet Management portlet. In User Management portlet, you can handle over 100000 users in DB. PAL-WCM portlet provides a Web Content Management feature. In this portlet, you can edit a web content by FCKditor.

How to install:

Download PALPortal-install-1.0-beta5.jar from http://sourceforge.jp/projects/pal/files/?release_id=25345#25345
Run installer
$ java -jar PALPortal-install-1.0-beta5.jar
Run PAL Portal to execute <INSTALL_DIR>/bin/startup.[sh|bat]
Access http://localhost:8080/palportal to display PAL Portal. Information about Administrator's username/password is admin/admin. If you want to modify the default contents, login as site/site user.

How to uninstall:

Remove the install directory, <INSTALL_DIR>

Developing PAL Administration Portlet

2007-04-09T06:59:00.000+09:00

We started to develop PAL Administration Portlet which is a administration portlet for Jetspeed2. I think that it will become one of other alternative admin tools for J2. I implemented user/role/group management portlet right now. In the future, I'll create portlet management, site management and so on..
http://svn.sourceforge.jp/svnroot/pal/pal-admin/trunk/

Portlet Output Optimizer 0.2 released

2007-02-18T18:14:00.000+09:00

Portlet Output Optimizer is a portlet filter to optimize an output on JSF portlet. This filter depends on Faces Response Filter. In this version, some bugs about multibyte character were fixed.

JStock Portlet 0.6 Released

2007-01-22T12:40:00.000+09:00

This portlet is JSR 168 compliant and provides stock information for Japanese market. In this release, using AJAX, JStock portlet reload the content. It is much appreciated if you can provide any feedback to us.

CMS Portlet 0.4 was released

2007-01-22T12:34:00.000+09:00

CMS Portlet is JSR 168 compliant portlet which provides a feature of Contents Management System.

Step to run this portlet:
1) Get cms-portlet.war
2) Deploy cms-portlet.war(for the detail, see portal server's document)

VFS Portlet 1.4 Released

2007-01-22T12:32:00.000+09:00

Using this portlet, you can access various file system on your Portal. This portlet enables you to access file systems(ex. local file system) via commons-vfs. So, basically, this portlet will support file systems supported by commons-vfs(but I checked only a local file system..). In this release, multi-thread issue was fixed.

To deploy this portlet:
1) Download vfs-portlet.war
2) Deploy vfs-portlet.war(For how to deploy portlet, see portal server's document)

Note: for JBoss Portal, please see this post.

If you want user to access only some specified paths, you can set the following init param in portlet.xml:


        <init-param>
            <name>accept-paths</name>
            <value>.*</value>
        </init-param>

The default value is ".*". It means user can access all file/directory. For example, if you want user to access files under /tmp and /home, the value is "/tmp/.*,/home/.*". On the other hand, if you want user not to access files, you can also use "deny-paths".

Tomahawk Bridge 0.9.1 released

2007-01-13T23:07:00.000+09:00

Tomahawk Bridge 0.9.1 was released! It supports Tomahawk 1.1.3 on any portal servers. Using this portlet filter with Faces Resonse Filter, you can use Upload component and some components that uses JavaScript and CSS. In this release, synchronized issue was fixed.

To use Tomahawk Bridge:
1) Add faces-response-filter-0.2.jar, portals-bridges-portletfilter-1.0.jar, tomahawk-bridge-0.9.1.jar, commons-fileupload-1.1.jar and commons-io-1.1.jar to /WEB-INF/lib
2) Modify portlet.xml

For example, if you use the following portlet.xml,


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
       <portlet-class>
           jp.sf.pal.vfs.portlets.VFSPortlet
       </portlet-class>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

change it to:


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
        <portlet-class>org.apache.portals.bridges.portletfilter.FilterPortlet</portlet-class>
        <init-param>
            <name>portlet-class</name>
            <value>jp.sf.pal.vfs.portlets.VFSPortlet</value>
        </init-param>
        <init-param>
            <name>portlet-filters</name>
            <value>jp.sf.pal.facesresponse.FacesResponseFilter,jp.sf.pal.tomahawk.filter.ExtensionsPortletFilter</value>
        </init-param>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

Note: you need to set "server" as javax.faces.STATE_SAVING_METHOD in web.xml. Currently, "client" is not supported.

For Portals Portlet Filter, please see Apache Portals Bridges.

Tohamawk Bridge depends on Faces Response Filter. Faces Response Filter provides a feature to rewrite JSF resonse. So, if you create a new other filter, such as Ajax4JSF filter, I think that you can use both Tomahawk and Ajax4JSF components.

Thanks!

Faces Response Filter 0.2 release

2007-01-13T23:06:00.000+09:00

Faces Resonse Filter is a portlet filter, and provides a feature to be able to rewrite a response output stream on portlet environment. In this release, synchronized issue was fixed. Using this portlet filter, you can use Tomahawk components with Tomahawk Bridge.

VFS Portlet 1.３ Released

2006-12-27T07:03:00.000+09:00

Using this portlet, you can access various file system on your Portal. This portlet enables you to access file systems(ex. local file system) via commons-vfs. So, basically, this portlet will support file systems supported by commons-vfs(but I checked only a local file system..).

To deploy this portlet:
1) Download vfs-portlet.war
2) Deploy vfs-portlet.war(For how to deploy portlet, see portal server's document)

Note: for JBoss Portal, please see this post.

If you want user to access only some specified paths, you can set the following init param in portlet.xml:


        <init-param>
            <name>accept-paths</name>
            <value>.*</value>
        </init-param>

Portlet Output Optimizer 0.1 released

2006-12-17T07:22:00.000+09:00

Portlet Output Optimizer is a portlet filter to optimize an output on JSF portlet. This filter depends on Faces Response Filter, This version removes html, head, body tags from the output.

Tomahawk Bridge 0.9 released

2006-12-09T09:09:00.000+09:00

Tomahawk Bridge 0.9 was released! It supports Tomahawk 1.1.3 on any portal servers. Using this portlet filter with Faces Resonse Filter, you can use Upload component and some components that uses JavaScript and CSS.

MyFaces Bridge was deprecated by this release!

To use Tomahawk Bridge:
1) Add faces-response-filter-0.1.jar, portals-bridges-portletfilter-1.0.jar, tomahawk-bridge-0.9.jar, commons-fileupload-1.1.jar and commons-io-1.1.jar to /WEB-INF/lib
2) Modify portlet.xml

For example, if you use the following portlet.xml,


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
       <portlet-class>
           jp.sf.pal.vfs.portlets.VFSPortlet
       </portlet-class>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

change it to:


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
        <portlet-class>org.apache.portals.bridges.portletfilter.FilterPortlet</portlet-class>
        <init-param>
            <name>portlet-class</name>
            <value>jp.sf.pal.vfs.portlets.VFSPortlet</value>
        </init-param>
        <init-param>
            <name>portlet-filters</name>
            <value>jp.sf.pal.facesresponse.FacesResponseFilter,jp.sf.pal.tomahawk.filter.ExtensionsPortletFilter</value>
        </init-param>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

Faces Response Filter 0.1 release

2006-12-09T09:06:00.000+09:00

Faces Resonse Filter is a portlet filter, and provides a feature to be able to rewrite a response output stream on portlet environment. Using this portlet filter, you can use Tomahawk components with Tomahawk Bridge.

Teeda-Ajax-Portlet 1.0 released

2006-12-09T06:56:00.000+09:00

This portlet is JSR 168 compliant and a sample to use Teeda Ajax(http://teeda.seasar.org/ja/teeda_ajax.html, Sorry.. it's in Japanese..) on a portlet. It is much appreciated if you can provide any feedback to us.

JStock Portlet 0.4 Released

2006-12-09T06:53:00.000+09:00

This portlet is JSR 168 compliant and provides stock information for Japanese market. In this release, we implemented ajax feature experimentally It is much appreciated if you can provide any feedback to us.

Helloworld Portlet 1.1 Released

2006-11-12T06:46:00.000+09:00

This portlet is educational to learn JSR 168 portlet. To deploy this portlet(helloworld.war), please see your Portal's document.

To build it from the source code, run:
$ mvn install

Blog Portlet 1.5 Released

2006-11-12T06:18:00.000+09:00

Blog Portlet is JSR 168 portlet to manage your blog(including comment and trackback features). In this release, i18n bug was fixed.

To deploy this portlet:
1) Download blog.war
2) Deploy blog.war(For how to deploy portlet, see portal server's document)

Note:
- For JBoss Portal, please see this post.
- If you encountered "PermGen space" exception, please see this post.

It would be highly appreciated if you could send a feedback to us :)

PAL Portal 1.0 Beta 2 Released

2006-10-31T07:32:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides.

How to install:

Download PALPortal-install-1.0-beta2.jar and PALPortal-portletpack-1.0-beta2.zip from https://sourceforge.jp/projects/pal/files/?release_id=22504#22504
Run installer
$ java -jar PALPortal-install-1.0-beta2.jar
Since the installer asks about a location of a portlet pack, specify a path of PALPortal-portletpack-1.0-beta2.zip
Run PAL Portal to execute <INSTALL_DIR>/bin/startup.[sh|bat]
Access http://localhost:8080/palportal to display PAL Portal. Information about Administrator's username/password is admin/admin.

How to uninstall:

Remove the install directory, <INSTALL_DIR>

JStock Portlet 0.3 Released

2006-10-19T11:57:00.000+09:00

This portlet is JSR 168 compliant and provides stock information for Japanese market. It is much appreciated if you can provide any feedback to us

Google Gadgets Portlet 0.2 Released

2006-10-14T14:17:00.000+09:00

Do you want to have many contents on your portal? If yes, try this portlet. This release has almost ALL Google Gadgets as portlet. The number of portlet is over 1500!!

To deploy this portlet:
1) Download googlegadgets.war
2) Deploy googlegadgets.war(For how to deploy portlet, see portal server's document)

Web Parts Portlet 0.1 Released

2006-10-08T19:51:00.000+09:00

Web Parts Portlet is a portlet to display Gadgets and BlogParts components, like Google Gadgets, on a portlet if you specify a code which you want to display.

To deploy this portlet:
1) Download webparts.war
2) Deploy webparts.war(For how to deploy portlet, see portal server's document

Google Gadgets Portlet 0.1 Released

2006-10-06T22:04:00.000+09:00

Google Gadgets Portlet enables you to display Google Gadgets on a portlet.

To deploy this portlet:
1) Download googlegadgets.war
2) Deploy googlegadgets.war(For how to deploy portlet, see portal server's document)

If you want to add a new Gadget as a portlet, please add a new entry(like the following) to portlet.xml.


  <portlet id="DateTimeGoogleGadget">
    <portlet-name>DateTimeGoogleGadget</portlet-name>
    <display-name>Date &amp; Time</display-name>
    <description>Google Gadgets: Data and Time Gadget</description>
    <portlet-class>jp.sf.pal.googlegadgets.GoogleGadgetsPortlet</portlet-class>
    <expiration-cache>-1</expiration-cache>
    <init-param>
      <name>jp.sf.pal.googlegadgets.title</name>
      <value>Date &amp; Time</value>
    </init-param>
    <init-param>
      <name>jp.sf.pal.googlegadgets.code</name>
      <value>&lt;script src="http://gmodules.com/ig/ifr?url=http://www.google.com/ig/modules/datetime.xml&amp;up_color=blue&amp;synd=open&amp;w=320&amp;h=136&amp;title=Date+%26+Time&amp;border=%23ffffff%7C3px%2C1px+solid+%23999999&amp;output=js"&gt;&lt;/script&gt;</value>
    </init-param>
    <init-param>
      <name>jp.sf.pal.googlegadgets.gadgetUrl</name>
      <value>http://gmodules.com/ig/creator?synd=open&amp;url=http://www.google.com/ig/modules/datetime.xml</value>
    </init-param>
    <supports>
      <mime-type>text/html</mime-type>
      <portlet-mode>VIEW</portlet-mode>
      <portlet-mode>EDIT</portlet-mode>
    </supports>
    <supported-locale>en</supported-locale>
    <supported-locale>ja</supported-locale>
    <resource-bundle>jp.sf.pal.googlegadgets.resources.GoogleGadgetsResources</resource-bundle>
    <portlet-info>
      <title>Date &amp; Time</title>
      <short-title>Date &amp; Time</short-title>
      <keywords>Date,Time,Google,Gadgets</keywords>
    </portlet-info>
  </portlet>

"jp.sf.pal.googlegadgets.title" is Portlet's title. "jp.sf.pal.googlegadgets.code" is a code of Gadget. "jp.sf.pal.googlegadgets.gadgetUrl" is an URL to modify the gadget code.

If you create an interesting Gadget entry, please send it to me :)

PAL Portal 1.0 Beta 1 Released

2006-10-03T06:47:00.000+09:00

PAL Portal is JSR 168 compliant portal server. This portal is Jetspeed2 based server and includes portlets which PAL project provides.

How to install:
1. Download PALPortal-install-1.0-beta1.jar and PALPortal-portletpack-1.0-beta1.zip from https://sourceforge.jp/projects/pal/files/?release_id=22030#22030
2. Run installer
$ java -jar PALPortal-install-1.0-beta1.jar
Since the installer asks about a location of a portlet pack, specify a path of PALPortal-portletpack-1.0-beta1.zip
3. Run PAL Portal to execute /bin/startup.[sh|bat]
4. Access http://localhost:8080/palportal to display PAL Portal. Information about Administrator's username/password is admin/admin.

How to uninstall:
1. Delete the install directory,

Japanese Map Portlet 0.1 Released

2006-09-25T12:01:00.000+09:00

Japanese Map(jmap) Portlet is JSR 168 portlet to provide a map data for Japan. The map data is provided by ALPSLAB. For the detail about a license of the map data, please check ALPSLAB's site.

To deploy this portlet:
1) Download jmap.war
2) Deploy jmap.war(For how to deploy portlet, see portal server's document)

It would be highly appreciated if you could send a feedback to us :)

Blog Portlet 1.4 Released

2006-09-20T23:06:00.000+09:00

Blog Portlet is JSR 168 portlet to manage your blog(including comment and trackback features). This release supports Jetspeed2 and JBoss Portal(Not supported Liferay, I found some issues..).

To deploy this portlet:
1) Download blog.war
2) Deploy blog.war(For how to deploy portlet, see portal server's document)

Note:
- For JBoss Portal, please see this post.
- If you encountered "PermGen space" exception, please see this post.

It would be highly appreciated if you could send a feedback to us :)

Notepad Portlet 0.3 Released

2006-09-15T21:12:00.000+09:00

Notepad Portlet is JSR 168 portlet to provide notepad feature. This release supports Jetspeed2, Liferay and JBoss Portal! Since this portlet is JSR 168 compliant, it will work on others.

To deploy this portlet:
1) Download notepad.war
2) Deploy notepad.war(For how to deploy portlet, see portal server's document)

Note:
- For JBoss Portal, please see this post.
- If you encountered "PermGen space" exception, please see this post.

It would be highly appreciated if you could send a feedback to us :)

ToDo List Portlet 0.3 Released

2006-09-15T21:06:00.000+09:00

ToDo Portlet is JSR 168 portlet to enable you to manage your todo list. This release supports Jetspeed2, Liferay and JBoss Portal! Since this portlet is JSR 168 compliant, it will work on others.

To deploy this portlet:
1) Download todolist.war
2) Deploy todolist.war(For how to deploy portlet, see portal server's document)

Note:
- For JBoss Portal, please see this post.
- If you encountered "PermGen space" exception, please see this post.

It would be highly appreciated if you could send a feedback to us :)

Address List Portlet 0.3 Released

2006-09-14T12:05:00.000+09:00

This portlet help you to manage your address list on your Portal. This release supports Jetspeed2, Liferay and JBoss Portal! Of cource, since this portlet is JSR 168 compliant, it will work on others.

To deploy this portlet:
1) Download addresslist.war
2) Deploy addresslist.war(For how to deploy portlet, see portal server's document)

Note:
- For JBoss Portal, please see this post.
- If you encountered "PermGen space" exception, please see this post.

If you see "PermGen space"..

2006-09-14T06:54:00.000+09:00

If you encountered "java.lang.OutOfMemoryError: PermGen space", set Java options. For example, I'm using the following options:


JAVA_OPTS="$JAVA_OPTS -Xmx256m -Xms256m -XX:PermSize=256m -XX:MaxPermSize=256m"

Please tune them for your environment :)

VFS Portlet 1.2 Released

2006-09-13T21:15:00.000+09:00

This release supports Jetspeed2, Liferay and JBoss Portal! Using this portlet, you can access various file system on your Portal. This portlet enables you to access file systems(ex. local file system) via commons-vfs. So, basically, this portlet will support file systems supported by commons-vfs(but I checked only a local file system..).

To deploy this portlet:
1) Download vfs-portlet.war
2) Deploy vfs-portlet.war(For how to deploy portlet, see portal server's document)

Note: for JBoss Portal, please see this post.

If you want user to access only some specified paths, you can set the following init param in portlet.xml:


        <init-param>
            <name>accept-paths</name>
            <value>.*</value>
        </init-param>

How to Deploy Our Portlet to JBoss Portal

2006-09-13T21:13:00.000+09:00

Some PALab's portlets support JBoss Portal(All portlet will support it..). To deploy PALab's portlet which uses JSF implementation(Teeda) to JBoss Portal(JBoss Portal has embedded MyFaces issue..), please see the following instruction:

1) Remove jsf-libs directory


$ cd jboss-portal-2.4.0
$ mv server/default/deploy/jbossweb-tomcat55.sar/jsf-libs/ .

2) Copy Jar files to server/default/deploy/ directory


$ cp jsf-libs/commons-beanutils.jar jsf-libs/commons-codec-1.2.jar jsf-libs/commons-digester-1.6.jar jsf-libs/jstl.jar jsf-libs/myfaces-* server/default/deploy/

3) Remove the following entry in server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml


      <init-param>
         <description>MyFaces tlds</description>
         <param-name>tagLibJar0</param-name>
         <param-value>jsf-libs/myfaces-impl.jar</param-value>
      </init-param>

4) Deploy PALab's portlet :)

Updating Portlets

2006-09-12T12:03:00.000+09:00

Currently, some portlets we provide do not work on portals other than Jetspeed2 correctly :( But we have MyFaces Bridge 0.8 release now! After replacing with MyFaces Bridge 0.8, they will work on all portal(I think..). So, I'm updating them..

MyFaces Bridge 0.8 Released

2006-09-12T12:01:00.000+09:00

MyFaces Bridge 0.8 was released! (I think) it supports Tomahawk 1.1.3 on ALL portal server(dependencies to a special feature for Portal, such as Jetspeed2 HeaderResource, were removed). Using this portlet filter, you can use Upload component and some components that uses JavaScript and CSS. For the test environment, I checked it on Jetspeed2, Liferay and JBoss Portal with IE and/or Firefox. If you have a problem, let us know.

To use MyFaces Bridge:
1) Add portals-bridges-portletfilter-1.0.jar, bridges-myfaces-0.8.jar, commons-fileupload-1.1.jar and commons-io-1.1.jar to /WEB-INF/lib
2) Modify portlet.xml

For example, if you use the following portlet.xml,


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
       <portlet-class>
           jp.sf.pal.vfs.portlets.VFSPortlet
       </portlet-class>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

change it to:


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
        <portlet-class>org.apache.portals.bridges.portletfilter.FilterPortlet</portlet-class>
        <init-param>
            <name>portlet-class</name>
            <value>jp.sf.pal.vfs.portlets.VFSPortlet</value>
        </init-param>
        <init-param>
            <name>portlet-filters</name>
            <value>jp.sf.pal.tomahawk.filter.ExtensionsPortletFilter</value>
        </init-param>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

Note: you need to set "server" as javax.faces.STATE_SAVING_METHOD in web.xml. Currently, "client" is not supported.

For Portals Portlet Filter, please see Apache Portals Bridges.

Thanks!

Updated MyFaces Bridge in CVS

2006-09-09T09:43:00.000+09:00

MyFaces Bridge was updated in CVS. The current code will support all portal! I checked it on Jetspeed2 and Liferay. Check it out!!

MyFaces Bridge Refactoring

2006-09-04T12:18:00.000+09:00

I modified MyFaces Bridge in CVS. The latest code does not need portal's special feature, like Jetspeed 2 HeaderResource component, to support JavaScript and CSS with Tomahawk's AddResource. If you want to this bridge on your portal server, you need to create a class which wraps RenderResponse implementation class for the portal. Currently, MyFaces Bridge has a wrapped class for J2(I think, if your portal server is based on Pluto, copying J2 wrapped class, it will work). If I have time, I'll create it for Liferay and JBoss Portal. Of course, your contribute is very welcome.

Thanks,
shinsuke

Search Engine Selector Portlet 0.1 Released

2006-08-30T11:57:00.000+09:00

Search Engine Selector Portlet is JSR 168 portlet to dispatch your requested words to a selected search engine. You can deploy this portlet to JSR 168 compliant portal server.

To deploy this portlet:
1) Download searchselector.war
2) Deploy searchselector.war(For how to deploy portlet, see portal server's document)

If you want to add/modify/delete listed search engines, you can modify the configuration file(/WEB-INF/classes/jp/sf/pal/searchselector/SearchSelector.dicon). For example, if you want to add Yahoo Search Engine, add red characters:


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//SEASAR2.1//DTD S2Container//EN"
    "http://www.seasar.org/dtd/components24.dtd">
<components>

    <component name="SearchEngineFactory"
        class="jp.sf.pal.searchselector.engine.SearchEngineFactory">
        <arg>
            {YahooEngine, GoogleEngine, YahooJapanEngine, InfoseekRakutenEngine,
            MarsFlagEngine, GooEngine, FreshEyeEngine, RakutenIchibaEngine}
        </arg>
    </component>

    <!-- SEARCH_WORD is replaced with an actual word -->

    <component name="YahooEngine"
        class="jp.sf.pal.searchselector.engine.SearchEngine">
        <property name="id">"YahooEngine"</property>
        <property name="name">
            #{"en" : "Yahoo!", "ja" : "Yahoo!"}
        </property>
        <property name="actionUrl">
            "http://search.yahoo.com/search?p=SEARCH_WORD"
        </property>
        <property name="encoding">"UTF-8"</property>
    </component>
...

For information about .dicon file, please see http://www.seasar.org/en/

Thanks!

ToDo List Portlet 0.2 was released!

2006-08-26T17:29:00.000+09:00

ToDo Portlet is JSR 168 portlet to enable you to manage your todo list. You can deploy this portlet to JSR 168 compliant portal server.

To deploy this portlet:
1) Download todolist.war
2) Deploy todolist.war(For how to deploy portlet, see portal server's document)

Note: The tested environment is Jetspeed2.

Thanks!

JStock Portlet 0.2 Released

2006-08-17T09:02:00.000+09:00

This portlet is JSR 168 compliant and provides stock information for Japanese market. It is much appreciated if you can provide any feedback to us :)

Weather Portlet 0.3 Released

2006-08-17T08:21:00.000+09:00

This is JSR 168 Portlet to provide weather information for Japan, not world-wide location. For Japanese user, some weather portlets(ex. a portlet provided as a sample) is useless. Because many users do not want weather information of a airport.. But this portlet will provide valuable information for each city in Japan!

VFS Portlet 1.1 Released

2006-08-11T06:30:00.000+09:00

Do you want to access various file system? If yes, please try this portlet. This portlet enables you to access file systems(ex. local file system) via commons-vfs. So, basically, this portlet will support file systems supported by commons-vfs(but I checked only a local file system..).

To deploy this portlet:
1) Download vfs-portlet.war
2) Deploy vfs-portlet.war(For how to deploy portlet, see portal server's document)

If you want user to access only some specified paths, you can set the following init param in portlet.xml:


        <init-param>
            <name>accept-paths</name>
            <value>.*</value>
        </init-param>

MyFaces Bridge 0.7 released!

2006-08-08T21:13:00.000+09:00

MyFaces Bridge 0.7 was released today :) It supports Tomahawk 1.1.3. Using this library, you can use Upload component and some components that uses JavaScript. For MyFaces bridge, the tested environment is Teeda(JSF implementation) and Jetspeed2(If you can run it on other environment, please let me know!). I think that MyFaces Bridges runs on any JSF implementation. If you have a problem, let us know.

To use MyFaces Bridge:
1) Add portals-bridges-portletfilter-1.0.jar and bridges-myfaces-0.7.jar to WEB-INF/lib
2) Modify portlet.xml

For example, if you put the following portlet.xml,


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
       <portlet-class>
           jp.sf.pal.vfs.portlets.VFSPortlet
       </portlet-class>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

change it to:


<portlet-app id="vfs-portlets" version="1.0">
   <portlet id="VFSNavigator">
       <description>VFS Navigator</description>
       <portlet-name>VFSNavigator</portlet-name>
       <display-name>VFS Navigator</display-name>
        <portlet-class>
            org.apache.portals.bridges.portletfilter.FilterPortlet
        </portlet-class>
        <init-param>
            <name>portlet-class</name>
            <value>jp.sf.pal.vfs.portlets.VFSPortlet</value>
        </init-param>
        <init-param>
            <name>portlet-filters</name>
            <value>
                jp.sf.pal.tomahawk.filter.ExtensionsPortletFilter
            </value>
        </init-param>
       <init-param>
           <name>view-page</name>
           <value>/jsp/ListView.jsp</value>
       </init-param>
       <supports>
           <mime-type>text/html</mime-type>
           <portlet-mode>VIEW</portlet-mode>
       </supports>
       <portlet-info>
           <title>VFS Navigator</title>
           <short-title>VFS</short-title>
       </portlet-info>
   </portlet>
</portlet-app>

That's it! For Portals Portlet Filter, please see Apache Portals Bridges.

Thanks!

Updated MyFaces Bridge in CVS

2006-08-07T12:27:00.000+09:00

MYFACES-434 is bothering many Portlet developers, and it's still open bug! So, PAL project provides MyFaces Bridge library that supports a file upload and resources, such as CSS and JavaScript, in head tag. But MyFaces Bridge 0.6 does not support the latest Tomahawk component.. So, I updated it in CVS! Now, it'll support Tomahawk 1.1.3 and be released soon..

Thanks!

Notepad Portlet 0.2 Released

2006-08-05T07:54:00.000+09:00

Notepad Portlet is JSR 168 portlet to provide notepad feature. You can deploy this portlet to JSR 168 compliant portal server.

To deploy this portlet:
1) Download notepad.war
2) Deploy notepad.war(For how to deploy portlet, see portal server's document)

Thanks!

What is "Portal Application Laboratory"?

2006-08-05T07:34:00.000+09:00

"Portal Application Laboratory" is Open Source Community to create useful Portal Server and Portlet based on the standard of JSR-168 Java Portlet API. We are developing and providing them at http://sourceforge.jp/projects/pal/.