If you're looking for an even easier way to deploy Webspace, look no further than the recently-released Sun GlassFish Web Space Server Virtual Machine (VM) Template.  This project pulls together many of Sun's open source components, and provides a simplified, pre-configured virtual image containing GlassFish Webspace Server, GlassFish Enterprise Server, MySQL, and OpenSolaris (Just Enough), in multiple virtual image formats. 

Ready, Set, (deploy) and Go!

As part of the the WebSpace Server 10 release, Ed Ort (from java.sun.com) and I sat down to do a deep dive webcast for GlassFish WebSpace Server. Parts 1 and 2 were originally published a few weeks ago. Now, parts 3 and 4 are now available and cover development tooling, and end user social collaboration techniques. Enjoy!

The user-oriented site webspace.dev.java.net  has had download links for a while for our Community and Milestone builds.  Now available are CDDL-based downloads of the 10.0 Final Release, which means you can download without having to have an SDN account or accept the Sun License Agreement.  The binaries are licensed under CDDL.  So easy to use!

The WSRP 2.0 FCS binary is now available for download from the OpenPortal WSRP project download page and has implemented all the WSRP 2.0 mandatory and most of the optional features. This project binary is being shipped into the below release vehicles apart from the above standalone install which the project provides as a wsrp-configurator.jar

Glassfish Web Space Server comes with its own out of the box Content Management Sytem(CMS). The WebSpace CMS comprises of the following features :

1. Document Management.
2. Image Management.
3. Web Content Management.

To know more about CMS in Web Space Server, read the following article :

http://blogs.sun.com/prakashKLV/entry/content_management_system_in_glassfish

To start adding web content using CMS in Web Space Server, read the following articles :

http://blogs.sun.com/prakashKLV/entry/adding_content_to_portal_page

http://blogs.sun.com/prakashKLV/entry/structures_templates_and_web_content

Stay tuned and visit this blog for latest articles on CMS in glassfish Web Space Server.

Web Space Server coverage links during the GlassFish Portfolio launch!

Web Space Server has out-of-box localization for 22 languages , out of which Sun provides localization support for Japanese (ja) and Simplified Chinese (zh_CN). Remaining languages are community driven.Also it has been Internationalized which allow localization in new languages which does not shipped out of box.

For further details on Localization (L10n) , Refer my personal blog entry :  Web Space Server - Localization

Sun GlassFish Web Space Server 10.0 has been released today [download].  It is Sun's next-generation portal server platform. It enables businesses large and small to pull together applications and content from a variety of Web-based and internal sources and present them as a unified, customizable portal on Web browsers, kiosks, and mobile devices.  It is part of a larger Portfolio of software being released today as part of the GlassFish Portfolio.

Web Space Server started out about a year ago with a partnership with Liferay Portal to join forces to develop the core portal in the Liferay community. Web Space Server is Sun's first product based on this effort and common code base. You may still run across instances of the term Project WebSynergy - this was Sun's internal codename for the project before it was released.

Standards such as JSR 168, JSR 286, JSR 170, and WSRP 2.0 provide a solid foundation on which to build a modern web 2.0 enterprise application platform, using lightweight web-oriented architectures, and powerful developer tools to create a rich ecosystem for developers, integrators, administrators, and now users to collaborate and innovate with.

A new user-oriented site webspace.dev.java.net  has been established.  This site will house information most useful to administrators and end users of Web Space Server, including download and documentation links, community support forums, email lists, wiki content, and other useful information.

New community builds and milestones of Web Space Server will continue to be released to deliver new features and fix bugs.  This release is marked 10.0 to indicate it is a (r)evolutionary step from previous portal efforts, such as Portal Server 7.2.

The WebSyner--err--Web Space team is proud to bring you this first release, and hope you will like it as much as we do!

Chris Reemts has found that relocating a WebSynergy-on-GlassFish installation is possible by following a few simple steps:

Moving a WebSynergy+GlassFish installation from one directory to another on OpenSolaris

---

The following are the actions I took to move an install of the MileStone 4 build of WebSynergy on OpenSolaris.

• The installed location was: IL == /export/home/demo/Desktop/
• The new location is: NL == /export/home/demo/

To move (NOTE: It is a good idea to save a copy of any files before editing):

• Move the entire web* folder from IL to NL – I used the file browser to do this
• Modify NL/web*/glass*/bin/asadmin
  • 1.Open in a text editor
  • 2.Line 7 contains a path --- correct this path to the new location
  • 3.Save
• Modify NL/web*/glass*/config/asenv.conf
  • 1.Almost every line has a path that you need to change to the new locations path
  • 2.Save
• Modify NL/web*/glass*/domains/domain1/config/sun-acc.xml
  • 1.You may have a domain name different from domain1
  • 2.Line 26 value is a path --- correct this path to the new location
  • 3.Save
• Modify NL/web*/glass*/domains/domain1/jbi/config/jbi-registry.xml
  • 1.You may have a domain name different from domain1
  • 2.Lines 19, 20, 25, 26, and 30 need the path corrected to the new location

---

This allows, for example, one to relocate a full install from one server to another (if using GlassFish V2, the destination machine must be the same OS/architecture). Nice work Chris!

Recently we have defined a common way to do I18n and L10n in WebSynergy. This process will be used for I18n/L10n during development of WebSynergy. It can also be used to develop new porlet with taking advantage of existing UI Tag lib and Language util class for I18n/L10n.

Details can be found on my personal blog entry .

As you know, in May of this year, Sun and Liferay announced a partnership to jointly develop next generation enterprise portal technology.  The Sun portal team has since begun the rollout of Project WebSynergy, codename for the initiative to release a product based on this common technology.

The Project WebSynergy team is now proud to make its Stable Build 2 available for download!  This release represents a significant milestone for the project, incorporating a number of new features, improvements, and a general enhancements over the last stable build (which was made available in May @ JavaOne).

Some of the things to look for in SB2:

• Release Stability and Cadence

The primary goal of this release was to establish regular builds (which you will start seeing regularly, not once every 2 months), get testing frameworks in place and automated (as soon as the public site, see below, is setup, automated test results will be posted as well), and establish basic hooks/frameworks in the Liferay community for future builds/releases to take advantage of.  As mentioned in my previous post, this is a Stable Build (as opposed to a Community Build or Commercial Release).

• Portlet Container 2.0

The OpenPortal Portlet Container is a fully compliant implementation of the Portlet 2.0 (JSR 286) specification. It also implements many optional features such as expiration and validation caching, support for aliases in eventing and public render parameters, and support for wildcards in eventing. WebSynergy development tools have complete support for JSR 286 and Portlet Container 2.0.

• WSRP 2.0 Consumer Support & Admin Application
  

WSRP 2.0 Consumer support is now available.  In addition, a WSRP consumer administration application is available in WebSynergy that enables managing multiple WSRP Consumers. For more information, read the blog post.

• Mirage/Journal

Liferay Portal has been modified to use the Mirage API. This API enables WebSynergy to use JCR-compliant repository.

• Roller Blog Application

The Roller Blog app provides integration with Roller Weblogger version 4.0. Using this app, portal users can create and manage blogs on a Roller 4.0 server.

• Simple API for Workflow

The Simple API for Workflow (SAW) feature is integrated into the Project WebSynergy SB 2 stable build. A sample Expense Report portlet provided with this feature showcases a typical enterprise Expense Report Application that involves human workflow. You can use SAW to connect to a business process engine such as the Java Composite Application Platform Suite provides the workflow functionality to the Expense Report portlet.

• Presence

For more information on this feature, see this article on the Liferay wiki. In upcoming Project WebSynergy builds, new applications using this infrastructure will provide a more presence-aware Portal to end users.

• Semantic

Core semantic processing libraries and utilities have been integrated into the portal. In the upcoming Project WebSynergy builds, the communities in the Liferay Portal Communities use this feature to provide a semantically rich experience to end users.

This build represents another in a series of binary releases of this project leading up to Sun's commercial release.  The product based on this project is also being renamed (Project WebSynergy is the internal codename), and we really don't want to have name confusion between the free-to-use, open source version and commercially supported version, so the external site presence (as described in my previous post) does not yet exist.  This should be resolved in the 14 days.

Note on GlassFish v3 - Project WebSynergy is available on GlassFish v2.  In the coming days, we expect to also make available a v3-based bundle based on GlassFish v3 TP2.

The OpenPortal WSRP Project consumer is now integrated into Liferay Portal. The next stable release of Liferay Portal is expected to have both the OpenPortal WSRP producer and consumer integrated in it.

Checkout the following posts for detailed information on this integration.

1. OpenPortal WSRP 2.0 Consumer in Liferay
2. Testing WSRP 2.0 interoperability in Liferay
   

Stay tuned on the OpenPortal WSRP Project mailing list for more information w.r.t to this integration.  

Since May, we have been working on establishing the project in more concrete forms, establishing an online presence, producing regular builds, and releasing source code.  In the next month or so you should see the results of this groundwork.  In the meantime, I'll keep you updated on where we are at (in addition to making builds and source available, see below).  This "Part 1" will cover Community and Roadmap.  In future parts, we'll cover items such as architecture, build structure and distribution contents, feature deepdives, and other technical interests.

Most of the work to date has been over at the Sun Liferay community, integrating components (e.g. Portlet Container), and new features (e.g. Message Board improvements) needed for WebSynergy.  As the project evolves, additional features will be developed and used in WebSynergy proper and ultimately be part of a commercial offering.

Community

OpenPortal consists of a number of projects.  Each of these projects delivers a certain set of functionality, and Sun (as well as anyone else who wishes) produces a commercial offering based off of the available source.

1. portal.dev.java.net - Core portal software, from which Sun's commercial Portal Server 7.x vintage is derived.  In addition, patches to 7.x will be generated for 7.x from this project's source.  No changes planned.
2. <name>.dev.java.net - Parent project of Project WebSynergy, from which Sun will derive a commercial offering.  Source and regular builds will appear here once the site is operational.  The name of this site is TBD.
   
3. [mirage,saw,wsrp,ruon,swa,portlet-container,jsfportletbridge].dev.java.net -  Projects delivering major functionality, consumed by both Sun Portal Server 7.x and WebSynergy.  No changes planned.
4. portalpack.netbeans.org - NetBeans & Eclipse plugins for developing portlets.  No changes planned.

In short, we are adding a new project to OpenPortal to represent the core of WebSynergy, since it is so very different from the 7.x vintage.  OpenPortal is also now a proper part of the larger GlassFish community (which means association with a vibrant and growing open source community).

Roadmap

For WebSynergy, we are going to take a different tact: make things available early and often.  Because project community members are now using the latest open source code to develop new features before Sun has released its latest commercial offerings, some consumers are finding that they would rather have features earlier, even if long-term support is not available. In response to this demand from both Sun Java System Portal Server customers, and the OpenPortal community, we will be producing builds with varying support options, much more frequently than in the past --as often as bi-weekly.  This will give customers a chance to get working code immediately, and pay only for the support they really need (or use the freely available builds with no support).  This kind of a model is being adopted in other projects (e.g. OpenSSO), so its function may already be familiar to you.

There are three types of builds that will be made available based on Project WebSynergy:

1. Community Build: Lightly tested, new features likely to be incomplete or have issues. Entirely supported by Community. New community builds generally available approximately 2-3 times a month.
2. Stable Build: Higher amount of testing. Complete documentation. Available roughly every 6-8 weeks.
3. Commercial Release - Highest amount of testing, complete documentation, commercial support available. Suitable for long term enterprise deployments. Frequency varies.
   

The demo that was made available at JavaOne represented the first Stable Build (SB1). SB2's plan is to be available this  onth, with an expected date for the first Commercial Release in the first quarter of 2009. Before SB2, there may be a community build (I had implied it would be this week, but a few of the features going into Liferay are still under code review, and not ready yet).

As indicated in the original announcement, we are not maintaining a fork. Instead, various components will be developed in WebSynergy, some of which will be integrated upstream (e.g. in Liferay) as needed, and a commercial release (and associated sustaining tail) will be initiated for each Commercial Release.  This is depicted in the below illustration (click on the image to get a larger version!).

What you should get out of this image:

1. The names of the components and releases and dates are all subject to change :-)
   
2. There is no fork.  Each release is based off of a specific point in time of all components, including Liferay.  For the next release(s), new snapshots are taken, and the old ones ignored.
3. Bugfixes bi-directionally flow between WebSynergy and Liferay before and after each Commercial Release. 
   

Stay tuned for part 2 and for the new WebSynergy site and builds to go live soon!

The JSR 286 (Portlet 2.0) specification has been released. Congratulations to Stefan Hepper, the spec lead of JSR 286 and the rest of the expert group. It has been a pleasure working with all on this JSR.

The main features of this JSR include

• Eventing
• Public Render Parameters
• Resource Serving
• Portlet Filters
• Validation based caching
• Request Dispatcher Include & Forward from all lifecycle
• Container Runtime Options
• Enhanced Tag Library
  

OpenPortal Portlet Container 2.0, which is a fully compliant implementation of the Portlet 2.0 (JSR286) specification, has been released. Check my blog for more details.

WSRP 2.0 offers Leasing of Portlets as part  of the specification. Leasing is the process by which a Consumer registers with a Producer for a specified time period, after which the Consumer Registration is rendered invalid. Lifetime is an optional parameter in the Registration offered by V2 producers. The OpenPortal WSRP project (Sun's open source implementation of WSRP ) has implemented this feature using the Open Source Portlet Container 2.0 . Check this wiki page for more information on portlet leasing.

Here's a primer on using the Leasing feature.. 

I would like to welcome Sytze van Koningsveld who has become an active contributor to the Eclipse Portalpack project. I was tied up with a lot of projects that I am involved in, and was not getting enough time to work on the Eclipse Portalpack. Sytze has shown keen interest in working with the Eclipse Portal Pack and we will be working together to take things forward. So please welcome him aboard the project.

 A small bit of information about Sytze in his own words :

"Sytze van Koningsveld was born in the Netherlands and has an MSc. degree in physics, works for over 10 years as a software developer mainly using Java. His programming experience ranges from Linux, COM and Corba to MDA, Jini, Eclipse plugins to portal web development with Spring and Hibernate. His current employer is Royal Dutch KLM in the Netherlands. You can reach him at sytzevk [AT] netscape [DOT] net."

Portal Server 7.2 is now available [download]. Based on the OpenPortal project, this release has several new features such as Delegated Administration, Google Gadget support, and JSR 286 / Portlet 2.0 support.

Looking ahead, Project WebSynergy [earlier post, info, download] is combining the efforts of Sun Portal and Liferay, and producing a lightweight, modular framework for developing and deploying next-gen webapps targeting the web 2.0 crowd. Looking forward to seeing this partnership in action!

For more information, visit the Sun/Liferay Community Page.

 

We had recently started work on semantic enabling Project WebSynergy's community feature.

Read my blog on that.

For doing this we had to extend the existing table structure by adding new columns
and  also creating new tables.

In this blog I will show how easy it is do this using
Project WebSynergy's ServiceBuilder framework 

The use case for this example will be to add an ontologyId column
to the existing BlogsEntry table.
We would also create a new BlogsEntryOntologyMapping Table. 

Open the
<synergy-workspace>\e2demo\synergy\liferay\patch\portal-impl\src\com\liferay
\portlet\blogs\service.xml
in your favorite IDE (we would recommend NetBeans)

Each <entity> tag corresponds to a table in the DB.

To add "OntologyId" column to the BlogsEntry table
add the following in <entity name="BlogsEntry"> </entity> tag

<column name="ontologyId" type="String" />

We can also add a finder method corresponding to the column that we have just added.
Using this the callers can get the blog entries corresponding to an ontologyId.

        <finder name="OntologyId" return-type="Collection">
            <finder-column name="ontologyId" />
        </finder>
This would generate a findByOntologyId() in the BlogsEntryPersistence
and BlogsEntryPersistenceImpl.

To add a new BlogsEntryOntlogyMapping table add the following 

 <entity name="BlogsEntryOntlogyMapping" local-service="true" remote-service="true">
        <column name="entryId" type="long" primary="true" />
        <column name="ontologyId" type="long" />
    </entity>

Next we need to add getBlogEntriesByOntologyId() to the BlogsEntryLocalServiceImpl class.

public List getBlogEntriesByOntologyId(String ontologyId) throws SystemException{ 

             List blogtnriesList = blogsEntryPersistence.findByOntologyId(ontologyId);

return blogtnriesList;

} 

You will get a compilation error on the blogsEntryPersistence.findByOntologyId(ontologyId) line.
This is because the method is still not added to the BlogsEntryPersistence interface.

But dont mind that as of now :)

After making these changes,
cd to <synergy-workspace>\e2demo\synergy\liferay\portal\portal-impl
in the command prompt and run the following ant script.

ant build-service-portlet-blogs 

This generates all the service, util, persistence and  factory classes that are relevant to Blogs.

Open the <synergy-workspace>\e2demo\synergy\liferay\portal\portal-service\src\com\liferay\portlet\blogs \service\persistence\BlogsEntryPersistence, you will find that the findByOntologyId() is newly generated.

Open the <synergy-workspace>\e2demo\synergy\liferay\portal\portal-service\src\com\liferay\portlet\blogs\ service\BlogsEntryLocalService and BlogsEntryLocalServiceUtil, you will find that the getBlogEntriesByOntologyId() is newly generated.

Now you can call the BlogsEntryLocalServiceUtil .getBlogEntriesByOntologyId() from any portlet class or jsp,
you will get the blog entries that the specific ontologyId applied to that.

Next the changes have to be made in the db scripts.

For this run ant build-db in the command prompt that you opened before.

Open the <synergy-workspace>\e2demo\synergy\liferay\portal\sql\portal-tables.sql and <synergy-workspace>\e2demo\synergy\liferay\portal\sql\create-*.sql.

You will find that the scripts have been suitably modifled.

For the changes to be reflected on the DB (could be MySQL, HSQL, etc),
drop the existing tables under lPortal database if any, and re-start the server.
The ontologyId column would be added to the BlogsEntry Table and BlogsEntryOntologyMapping table would have been created.

Extending Project WebSynergy's tables is as simple as this. You can extend this example to any other feature like wiki, bookmarks, etc.

 

The SAW feature in OpenPortal is intended to offer a generic workflow API, to perform human workflow interaction with various workflow engines. This generic workflow API will ship with a default implementation for Java Composite Application Platform Suite. Currently, the Workflow API, Workflow Tag Library, Sample portlets, and Tooling Plugins for developer IDE's are provided in the SAW home page.

In this screencast, you will learn how to:

1. Perform human workflow interaction with Java Composite Application Platform Suite workflow engine
2. Add SAW plug-in in NetBeans IDE,
3. Create a simple web application using the drag and drop features in SAW plug-in 
4. Create a simple a simple SAW portlet, which lists tasks based on task ID
   

 

  

 

The community feature of Project WebSynergy has been semantically enabled. This is a preview version of that.
This is taking the first step towards Web3.0 enablement.

So whats the Semantic Web ??
The semantic web is an evolving extension of the world wide web, in which web content can be expressed not only in a natural language but also in a format that can be read and used by machines for processing the information. It is w3c recommendation.

As a human when we write and read a blob of text, we know what it means but a machine reading a bunch of characters has no idea as to what it means. 

For the machine to be as intelligent as humans to decipher similar information from the text, there has to be some kind of information that the machine has to be provided with. This "extra" information is traditionally provided as meta-data in the form of tags, microformats or some other means. A much more structured and scientific way of applying metadata to a blurb of text is via what is called an ontology.

The community feature of Project WebSynergy allows you to add blog entries, wiki pages and message boards.

Refer to my blog on how to create a community in Project WebSynergy.
For an idea of what a Semantic Community Portal is, see here.

In a Project WebSynergy community, when the user creates a blog entry or a wiki page, he/she can optionally associate it with an ontology element (which acts as the metadata).
When the user views the blog entry, the other semantically related blog entries and wiki pages are displayed. The search for the related entires is not a key word search, but a semantic search done by the reasoner. The semantic reasoner infers the related ontology elements and we can see the blog entries and wiki pages for which  the related ontology elements have been applied to.

An example of the Semantic Community Portal is shown in the screen-casts.

 

 This blog describes the steps to create a community in Project WebSynergy.

1. Login as admin@example.com/admin into Project WebSynergy
   Move your mouse over the "Welcome Admin User" message and click on Add Application
2. In the Add Application window that shows up, select the Communities under Community Section. You can also type "communities" in the search content text box. Click on "Add" or drag and drop the portlet into one of your tabs. The communitiy portlet is now added to your tab.
   
3. Click on Add Community button.
4. Enter name (say Synergy) and click on Save. The community is created with the name that you specified.
   Click on "Available Communities" sub-tab.
5. For the community that you just created, click on the "Actions" button and select "Manage Pages".
   Enter name for the community page (say MySynergyPage ) and click on "Add Page".
6. Click on View Pages.
   To this community page, you can add the any  portlets. For eg.
       Blog Portlet
       Blogs Aggregator Portlet
       Wiki Portlet
       Message Boards Portlet
   
7. All these portlets are available under the Colloboration section in Add Application window

The "MySynergyPage"that you have created, allows user to add / view blogs, wiki and message boards. 

The expense-report widget, that is delivered as a part of the Project WebSynergy bundle, models a typical workflow scenario  where SAW (Simple API for Workflow) could be used. In an organization, employees raise expense reports and submit them to the managers to be approved or rejected. Once submitted, the report triggers a workflow process(in a workflow engine like JavaCAPS), and becomes a pending task for the associated manager. When the manager approves/rejects the report, the report goes to the next step in the workflow process.

This widget has been integrated with a simple JavaCAPS workflow process. If a workflow engine is unavailable, the SAW calls to the  Workflow engine can be disabled using the preferences. If the call to the workflow engine is enabled without configuring the engine, it results in a system error.

 In addition to Workflow, this widget has the following features: 

•  JMaki - Uses JMaki Yahoo Datatable
  

•  Usage of ServeResource feature of JSR286 portlets for Ajax requests (For Displaying Report Details)

Click here to know more about this widget....

Here is a step-by-step screencast showcasing the widget.

     With the announcement of Project WebSynergy, the aggregation and presentation solution for most internet and enterprise applications looks to be heading in the right direction. A significant requirement for any such application is a good Content Management System (CMS). Check out this entry as to how Project Mirage is leveraged and used in WebSynergy. 

There is a preview version of the WebSynergy plug-in available at Portal Pack project site. This NetBeans plug-in supports portlet development and deployment on the new WebSynergy and also works with Liferay. For more details read here...

 

ProjectWebSynergy, will redifine the term portal. It will be a widget platform and will natively support other programming and web technologies, like Ruby and PHP. Java, Ruby and PHP widgets not only co-exist on a portal page, but also inter-communicate. And all this is made so easy using Portal Pack NetBeans plugins.

For more on this, read here. But wait..., if seeing is believing, visit us at the JavaONE 2008 booth if you are in San Francisco or the Bay area.
 

This year's JavaOne is in San Francisco the first week of May.  The OpenPortal community will have a big presence this year, and Sun's Portal Server will also be discussing upcoming features of it's Portal Server 7.2 release and beyond.  Don't miss it!  Also, everyone is invited to CommunityOne (registration/attendance is free).  GlassFish is also hosting the "GlassFish UnConference", an annual free event.   More to come on all of the above, so stay tuned.  Drop by and say Hi :)

Web Services for Remote Portlets (WSRP) specification version 2.0 has been approved as an OASIS standard. Here are the links to the approved specification.

1. HTML: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-cs-02.html
2. PDF: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-cs-02.pdf
3. XML Schema: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-types.xsd
4. WSDL:
• Interfaces: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-interfaces.wsdl
• Bindings: http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-bindings.wsdl

The OpenPortal WSRP Project implements the above all the mandatory and some of the major optional features defined in this specification and milestone 3 binary is available for download.

 

Another addition to the porlet-repository is the Suggest and Search Portlet . It is a JSR286 portlet that provides search related suggestions as the user types words and search results  from the web (using Ajax and serveResource)based on Yahoo Contextual Search and  Yahoo Web Search Service API.  The portlet makes REST client calls to the services, parses the results in XML /JSON format and displays them to the user. 

This has been tested on the Open Source Portlet Container 2.0. Check this blog post and  the wiki page for more details.

 

The OpenPortal WSRP Project v2 milestone 3 is now available for download.  The OpenPortal WSRP Project version 2.0 is now feature complete and will be OASIS WSRP specification compliant whenever the OASIS WSRP specification would be approved.

The OpenPortal WSRP v2 milestone 3 previews the following features, some defined in OASIS WSRP version 2.0 specification.

1. WSRP 2.0 getResource
2. WSRP 2.0 Caching
   1. Markup Caching
   1. Expiration Markup Caching
   2. Validation Markup Caching
      
   2. Resource Caching
   1. Expiration Resource Caching
   2. Validation Resource Caching
      
3. Tomcat 5.5 support
4. Migrated code to the latest WSRP 2.0 schema

You can download the OpenPortal WSRP version 2.0 milestone 3 from the project download page.

 

This is the last major milestone build from the OpenPortal WSRP Project, the future milestones are expected not to add any major new features to the WSRP version 2.0 implementation rather provide pluggable extensions mechanisms to consuming portals to implement some of the WSRP version 2.0 features such as Portlet Management, CC/PP etc.  

Here are some of the documents that are related to this milestone

1. Whats new in milestone 3
   
2. WSRP installation on Glassfish
3. Milestone 3 preview document
4. WSRP installation on Tomcat
5. WSRP User Guide
   

Stay tuned on the future milestones of the OpenPortal WSRP version 2.0 project. If you would like to keep track of future announcements and additions to the OpenPortal WSRP Project, please subscribe to the announce@wsrp.dev.java.net alias.

If you have questions on how to use the OpenPortal WSRP Project and other comments/suggestions/requests, we urge you to join the users@wsrp.dev.java.net alias.

Please report any issues that you encounter while trying OpenPortal WSRP version 2.0 milestone 3 to issues@wsrp.dev.java.net.