VFS Portlet 1.３ Released

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>

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".

Portlet Output Optimizer 0.1 released

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

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>

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.1 release

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

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

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.