Letzte Blogger

Olaf Kock

Staff
90 Nachrichten
18. Dezember 2014

David Kubitza

2 Nachrichten
14. Dezember 2014

Meera Prince

19 Nachrichten
4. Dezember 2014

James Falkner

Staff
100 Nachrichten
2. Dezember 2014

Juan Fernández

Staff
17 Nachrichten
28. November 2014

Andrea Di Giorgi

2 Nachrichten
26. November 2014

Gregory Amerson

Staff
26 Nachrichten
25. November 2014

Cody Hoag

Staff
6 Nachrichten
25. November 2014

Duke H

Staff
2 Nachrichten
24. November 2014

Nicholas Gaskill

Staff
1 Nachrichten
21. November 2014

Announcement: Liferay Faces 4.2.0-m2 Released

Company Blogs 26. September 2014 Von Neil Griffin Staff

On September 26, 2014 Liferay released the 2nd Milestone of Liferay Faces 4.2.0:

Liferay Faces 4.2.0-m2 JSF 2.2 + Liferay Portal 6.2 Release Notes


All New Showcase

The Liferay Faces Showcase has is hosted at www.liferayfaces.org and features a suite of new Java-based JSF components, many of which utilize AlloyUI and can be used in either webapps or portlets.

Responsive JSF

  • Since AlloyUI relies on Twitter Bootstrap, bootstrap-responsive.min.css is automatically included as a @ResourceDependency
  • Developers can design responsive layouts using the alloy:row component
  • There is a "responsive" attribute (defaults to true) on alloy:inputDate and alloy:inputTime so that they use the native date/time pickers on mobile displays
  • The portal:navBar component is responsive as well, turning itself into a button with a popup menu for smaller (mobile) displays

Download Instructions

Since the 4.2.0-m2 release is not General Availability (GA), the JAR artifacts are *not* published at Maven Central. Instead, they are published at the new Liferay Previews Nexus Repository along with the demo portlets.

Maven Project Dependencies

<dependencies>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-alloy</artifactId>
    <version>4.2.0-m2</version>
  </dependency>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-bridge-impl</artifactId>
    <version>4.2.0-m2</version>
  </dependency>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-portal</artifactId>
    <version>4.2.0-m2</version>
  </dependency>
</dependencies>
<repositories>
  <repository>
    <id>liferay-previews</id>
    <url>
      https://repository.liferay.com/nexus/content/repositories/liferay-previews
    </url>
  </repository>
</repositories>

Ivy Project Dependencies

<dependencies>
  <dependency org="com.liferay.faces" name="liferay-faces-alloy" rev="4.2.0-m2" />
  <dependency org="com.liferay.faces" name="liferay-faces-bridge-impl" rev="4.2.0-m2" />
  <dependency org="com.liferay.faces" name="liferay-faces-portal" rev="4.2.0-m2" />
</dependencies>
...
<resolvers>
  <ibiblio m2compatible="true" name="liferay-previews"
    root="https://repository.liferay.com/nexus/content/repositories/liferay-previews" />
</resolvers>

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Stability

This 4.2.0-m2 release is a technology preview that is suitable for development purposes but should not be used in a production environment. It will not be supported under the Liferay EE subscription until it reaches GA (General Availability) status.

Support For JSF 2.2 and Liferay Portal 6.2

  • This release of Liferay Faces is compatible with JSF 2.2

  • If deploying portlets to Liferay Portal 6.2, then developers should read the new Migrating From Liferay Faces 3.1 to Liferay Faces 3.2/4.2 section in the Developer's Guide. Specifically, JSF portlets require the following option in the WEB-INF/liferay-portlet.xml descriptor: <requires-namespaced-parameters>false</requires-namespaced-parameters>

Tomcat 7 Only

Developed under JSR 344, JSF 2.2 is part of the larger Java EE 7 specification from the JCP. Even though Java EE 7 includes technologies like CDI 1.1 and Servlet 3.1, JSF 2.2 only depends on Java EE 6 technologies like CDI 1.0 and Servlet 3.0. This means that JSF 2.2 webapps and portlets can be deployed in Java EE 6 (Servlet 3.0) servlet containers such as Tomcat 7. However, Java EE 6 full-profile application servers such as GlassFish 3.2, JBoss 7.1, and WebLogic 12c bundle JSF 2.1 and cannot be upgraded to JSF 2.2. At the time of this writing, Liferay, Inc. has not released any Liferay Portal 6.1/6.2 bundles with Java EE 7 servers such as Tomcat 8, GlassFish 4.0 or JBoss/WildFly 8. Therefore this milestone has only been tested for compatibility with Liferay Portal 6.1/6.2 on Tomcat 7.
 

Roadmap

The Liferay Faces team is hard at work adding new components and new features so that we can achieve BETA status in our next release. Stay tuned!
 

Feedback Requested

If you find any problems with this release, please post a message in the Liferay Faces forums.

The Future is Bright for JSF

Company Blogs 5. August 2014 Von Neil Griffin Staff

Today's JSF

JavaServer Faces (JSF) is a Java EE standard technology that enjoys wide support with Java EE application servers including JBoss AS/WildFly, Oracle WebLogic, and IBM WebSphere. In addition, JSF developers benefit from tooling support built-in to Eclipse, NetBeans, and IntelliJ. Over the years, JSF has received many features and improvments thanks to dedicated JCP Expert Groups led by Ed Burns and innovative ideas contributed from open source projects.

JSF component suites like ICEfaces, PrimeFaces, and RichFaces offer a plethora of UI components and advanced features, all built on top of the core JSF standard. Each of these component suites boasts an online "showcase" type of webapp that shows how to use the components in typical use-cases.

JSF 2.0/2.1 was released with Java EE 6 and was well received by developers thanks to the addition of standards-based Ajax features and the adoption of Facelets as the standard templating engine. JSF 2.2 was released with Java EE 7 and added fantastic new features like Faces Flows.

JSF Portlets

Thanks to JSR 329, JSF is fully compatible with Portlet 2.0, another standard from the JCP. The Liferay Faces project is supported under Liferay EE and provides a standards-compliant JSF portlet bridge. With added support from Liferay IDE, developers can easily deploy JSF portlets built with ICEfaces/PrimeFaces/RichFaces within Liferay Portal. In addition, Liferay, Inc. has a technology partnership with ICEsoft and a partnership with PrimeTek in order to support our mutual customers.

Tomorrow's JSF

Recently, Liferay announced a major upgrade to Liferay Faces, which includes support for JSF 2.2 and a suite of JSF components for AlloyUI. ICEsoft has announced ICEfaces 4.0, and the PrimeTek blog has frequent updates on PrimeFaces 5.1. The new Portlet 3.0 standard is being developed under JSR 362 and features optimized support for JSF. Finally, Ed Burns announced Oracle's intention to file a new JSR for JSF 2.3.

The future is bright indeed for JSF. smiley

-- Neil

Liferay Faces Project News - July 2014

Company Blogs 21. Juli 2014 Von Neil Griffin Staff

Liferay Faces Showcase

The Liferay Faces team has been hard at work on the new Liferay Faces Showcase which demonstrates the new JSF components we are developing. Many of the components utilize Liferay's AlloyUI technology (which is based on YUI3 and Twitter Bootstrap).

Component Design Features:

  • The new AlloyUI JSF components will work with Liferay Faces 4.2 (JSF 2.2) and Liferay Faces 3.2 (JSF 2.1)
  • Although the new AlloyUI JSF components require Liferay Portal 6.2, they will also work in a plain webapp!
  • When running in a plain webapp, the new AlloyUI JSF components provide the YUI3 and AlloyUI 2.0.0 JavaScript resources automatically.
  • Our goal is to have the new AlloyUI JSF components be able to exist in the same JSF view as ICEfaces/PrimeFaces/RichFaces components. This should be technologically possible since this was one of the original design goals of JSF, and the other component suites are based on jQuery.

Stay tuned for a technology preview in the coming weeks! smiley

Facelet Tag Library Namespaces

Liferay Faces is an umbrella project that is comprised of several sub-projects. In order to make it easier to identify which components are associated to a sub-project, we decided to simplify the Facelet Tag Library namespaces:

Namespace Prefix Sub-Project
alloy: Liferay Faces Alloy
bridge: Liferay Faces Bridge
portal: Liferay Faces Portal 

Team Members

Back in January of 2014, Liferay's Bruno Basto became a contributor to our team by helping us develop a code generator for AlloyUI JSF components.

Since then Kyle Stiemann has made the code generator more robust which has strengthened the overall quality of the software. Kyle has also developed JSF components like alloy:button, alloy:commandButton, alloy:icon, alloy:inputDate, and alloy:panelGroup.

Vernon Singleton has developed JSF components like alloy:outputText, alloy:outputRemainingChars, alloy:selectOneRadio, alloy:selectStarRating, alloy:selectThumbRating, and alloy:accordion.

I've been working on the Showcase portlet itself, and also developing components like alloy:inputSourceCode, alloy:tabView, etc. Working on the Showcase has been lots of fun because it is built with Liferay Faces.

Again, stay tuned for our technology preview in the coming weeks!smiley

-- Neil


Left to right: Bruno Basto, Kyle Stiemann, Vernon Singleton, and Neil Griffin

Announcement: Liferay Faces 4.x M1 Released

Company Blogs 3. März 2014 Von Neil Griffin Staff

On March 1, 2014 Liferay released the 1st Milestone of Liferay Faces 4.x:

Liferay Faces 4.2.0-m1 JSF 2.2 + Liferay Portal 6.2 *NEW* Release Notes
Liferay Faces 4.1.0-m1 JSF 2.1 + Liferay Portal 6.1 *NEW* Release Notes

Download Instructions

Since the 4.2.0-m1 and 4.1.0-m1 releases are not General Availability (GA), the JAR artifacts are *not* published at Maven Central. Instead, they are published at the new Liferay Previews Nexus Repository along with the demo portlets.

Maven Project Dependencies

<dependencies>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-alloy</artifactId>
    <version>4.2.0-m1</version>
  </dependency>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-bridge-impl</artifactId>
    <version>4.2.0-m1</version>
  </dependency>
  <dependency>
    <groupId>com.liferay.faces</groupId>
    <artifactId>liferay-faces-portal</artifactId>
    <version>4.2.0-m1</version>
  </dependency>
</dependencies>
<repositories>
  <repository>
    <id>liferay-previews</id>
    <url>
      https://repository.liferay.com/nexus/content/repositories/liferay-previews
    </url>
  </repository>
</repositories>

Ivy Project Dependencies

<dependencies>
  <dependency org="com.liferay.faces" name="liferay-faces-alloy" rev="4.2.0-m1" />
  <dependency org="com.liferay.faces" name="liferay-faces-bridge-impl" rev="4.2.0-m1" />
  <dependency org="com.liferay.faces" name="liferay-faces-portal" rev="4.2.0-m1" />
</dependencies>
...
<resolvers>
  <ibiblio m2compatible="true" name="liferay-previews"
    root="https://repository.liferay.com/nexus/content/repositories/liferay-previews" />
</resolvers>

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Stability

This 4.x M1 release is based off the stable codebase of the 3.x GA5 release. The main difference is support for JSF 2.2 and new demo portlets (see below). This M1 (Milestone) release is suitable for development purposes, however 4.x will not be supported under the Liferay EE subscription until it reaches GA (General Availability) status.

Support For JSF 2.2

  • This is the first release of Liferay Faces that is compatible with JSF 2.2

  • If deploying portlets to Liferay Portal 6.2, then developers should read the new Migrating From Liferay Faces 3.1 to Liferay Faces 3.2/4.2 section in the Developer's Guide. Specifically, JSF portlets require the following option in the WEB-INF/liferay-portlet.xml descriptor: <requires-namespaced-parameters>false</requires-namespaced-parameters>

Tomcat 7 Only

Developed under JSR 344, JSF 2.2 is part of the larger Java EE 7 specification from the JCP. Even though Java EE 7 includes technologies like CDI 1.1 and Servlet 3.1, JSF 2.2 only depends on Java EE 6 technologies like CDI 1.0 and Servlet 3.0. This means that JSF 2.2 webapps and portlets can be deployed in Java EE 6 (Servlet 3.0) servlet containers such as Tomcat 7. However, Java EE 6 full-profile application servers such as GlassFish 3.2, JBoss 7.1, and WebLogic 12c bundle JSF 2.1 and cannot be upgraded to JSF 2.2. At the time of this writing, Liferay, Inc. has not released any Liferay Portal 6.1/6.2 bundles with Java EE 7 servers such as Tomcat 8, GlassFish 4.0 or JBoss/WildFly 8. Therefore this milestone has only been tested for compatibility with Liferay Portal 6.1/6.2 on Tomcat 7.
 

JSF 2.2 Component Suites

Portlets can be developed with JSF 2.2 component suites including Liferay Faces Alloy and PrimeFaces 4.0. Future milestones will include planned support for ICEfaces 4.0 and RichFaces 5.0 portlets.
 

JSF 2.2 Feature Demos

In order to test JSF 2.2, we developed the following new demo portlets:

Roadmap

The Liferay Faces team is hard at work developing JSF components and a Showcase for AlloyUI 2.0. Stay tuned!
 

Feedback Requested

If you find any problems with this release, please post a message in the Liferay Faces forums.

Announcement: Liferay Faces 3.x / 2.x GA5 Released

Company Blogs 19. Februar 2014 Von Neil Griffin Staff

On February 15, 2014 Liferay released the 5th General Availability (GA) version of Liferay Faces:

Liferay Faces 3.2.4-ga5 JSF 2.1 + Liferay Portal 6.2 *NEW* Release Notes
Liferay Faces 3.1.4-ga5 JSF 2.1 + Liferay Portal 6.1 Release Notes
Liferay Faces 3.0.4-ga5 JSF 2.1 + Liferay Portal 6.0 Release Notes
Liferay Faces 3.0.4-legacy-ga5 JSF 2.1 + Liferay Portal 5.2 Release Notes
Liferay Faces 2.2.4-ga5 JSF 1.2 + Liferay Portal 6.2 *NEW* Release Notes
Liferay Faces 2.1.4-ga5 JSF 1.2 + Liferay Portal 6.1 Release Notes

Project Links

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Support For Liferay Portal 6.2

  • This is the first release of Liferay Faces that has been certified as being compatibile with the new Liferay Portal 6.2 CE GA1 and 6.2 EE GA1 release

  • Developers can use version 3.2.4-ga5 for JSF 2.1, or version 2.2.4-ga5 for JSF 1.2

  • In order to upgrade portlets to Liferay Portal 6.2 compatibility, the DTD version numbers inside the of the Liferay XML descriptors should be updated:
    <!DOCTYPE display PUBLIC "-//Liferay//DTD Display 6.2.0//EN" "http://www.liferay.com/dtd/liferay-display_6_2_0.dtd">
    
    <!DOCTYPE hook PUBLIC "-//Liferay//DTD Hook 6.2.0//EN" "http://www.liferay.com/dtd/liferay-hook_6_2_0.dtd">
    <!DOCTYPE liferay-portlet-app PUBLIC "-//Liferay//DTD Portlet Application 6.2.0//EN" "http://www.liferay.com/dtd/liferay-portlet-app_6_2_0.dtd">
  • Developers should read the new Migrating From Liferay Faces 3.1 to Liferay Faces 3.2/4.2 section in the Developer's Guide. Specifically, JSF portlets require the following option in the WEB-INF/liferay-portlet.xml descriptor:

    <requires-namespaced-parameters>false</requires-namespaced-parameters>
  • The feature in Liferay Faces Bridge that detects duplicate versions of JSF resources in the <head>...<head> section of the portal page does not work with the out-of-the-box Liferay+Tomcat bundle. The reason why is because Liferay Portal 6.2 has a revamped "parallel rendering" engine that attempts to render portlets in parallel (rather than in serial) by default. Developers can add p_p_parallel=0 to the initial HTTP GET portal page URL to disable parallel rendering on a page-by-page basis, or it can be disabled globally by setting the value of the following property in the portal-ext.properties file:
    layout.parallel.render.enable=false
  • The following JSF Portlet Maven Archetypes have been updated to use version 3.2.4-ga5 Maven dependencies:
  • In addition, the JSF Portlet Ivy Templates in the Plugins SDK have been updated to use version 3.2.4-ga5 Ivy dependencies.
  • Liferay IDE 2.0 lets developers choose either Maven or Ivy as the project build type. New projects will be created from the aforementioned JSF Portlet Maven Archetypes and Ivy Templates will be used automatically when new JSF portlets are created via the wizard. 

Release Stats

This is a maintenance release that has 35+ bug fixes and 15+ features/improvements.

WebLogic 12c / 11g

Version 3.2.4-ga5 is compatible with WebLogic 12c. Version 3.1.4-ga5 is compatible with WebLogic 11g.
 

Documentation Changes

The Liferay Faces documentation was converted to MarkDown and is now Chapter 4 of the Liferay Portal 6.2 Developer Guide. We have plans to convert many of the Liferay Faces wiki articles MarkDown as well. When complete, they will be integrated into the "Installation and Setup" chapter of the Liferay Portal 6.2 User Guide. For now, please continue to reference the Liferay Faces Wiki.
 

New Demo: primefaces4-portlet

In order to test PrimeFaces 4.0, we developed a new primefaces4-portlet demo.
 

Thank You

Thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

Three Cheers for JSF 2.2 Faces Flows

General Blogs 18. Dezember 2013 Von Neil Griffin Staff

Introduction

Java EE 7 includes the new JSR 344 (JSF 2.2) standard and provides developers with new features like Resource Library Contracts, HTML5 Friendly Markup, and Faces Flows. The Liferay Faces team is hard at work at providing 1st class support for JSF 2.2 in Liferay Faces 4.x including the following new portlet demos:

Webinar: Modern JSF Development

I recently had the privledge of showing these demos during a Liferay LIVE webinar titled Modern JSF Development. The webinar will be archived in a few weeks.

Personally I have to say that Faces Flows is my favorite feature in JSF 2.2. In fact, during the webinar one of the attendees wrote:

Wow.. Flows is a natural fit in Liferay... Excellent!

What Makes Faces Flows So Great?

Faces Flows is a standards-based Java EE feature that builds upon the lessons learned from projects like ADF Task Flows, Spring WebFlow, and Apache MyFaces CODIIt provides a way of connecting JSF views together and scoping data accordingly via the new @FlowScoped annotation and CDI.

@FlowScoped vs @ConversationScoped

The new JSF @FlowScoped annotation depends on CDI. At first glance it might seem similar to the CDI @ConversationScoped annotation, but it is a much better "fit" for JSF webapps/portlets because the developer doesn't need to make awkward programmatic calls to Conversation.begin() and Conversation.end() in a PhaseListener to make things work. Instead, beans annotated with @FlowScoped are created and destroyed automatically when the user navigates in and out of flows. In addition, developers can easily orchestrate sub-flows spawned from a parent flow and pass data between them using outbound and inbound parameters.

Let's take a closer look by examining the JSF2 Faces Flows Portlet demo...

Defining Flows

The portlet contains a main flow named "booking" and a sub-flow named "survey". The user (customer) books travel with Facelet views that are collected together in the "/booking" directory, and optionally completes a survey with Facelet views that are in the "/survey" directory.

As stated earlier, flows can pass data to each other using outbound and inbound parameters. If the customer takes the optional survey, then the customer's info is passed as an outbound parameter as defined in /booking/booking-flow.xml and received as an inbound parameter as defined in /survey/survey-flow.xml

Activating The Booking Flow

The initial view displayed by the portlet is /views/portletViewMode.xhtml

Simply clicking on the "Enter Booking Flow" button activates the "booking" flow:

<h:commandButton action="booking" value="#{i18n['enter-booking-flow']}">
	<f:ajax execute="@form" />
</h:commandButton>

Since the value of the action attribute is "booking", JSF will use convention-over-configuration to determine the target view for navigation. If it can't find a file named booking.xhtml in the same directory, it will attempt to find a directory named "/booking" and navigate to the view named /booking/booking.xhtml

Automatic Bean Scope Management by CDI

The portlet contains two model beans annotated with @FlowScoped:

When EL expressions like #{bookingFlowModelBean} or #{surveyFlowModelBean} are encountered by JSF in a Facelet view, the EL resolver chain will ask CDI to create an instance of BookingFlowModelBean.java or SurveyFlowModelBean.java respectively. Additionally, CDI will call any methods annotated with @PostConstruct such as BookingFlowModelBean.postConstruct() and SurveyFlowModelBean.postConstruct().

When the user navigates out of the "booking" flow or "survey" flow, then CDI will call any methods annotated with @PreDestroy such as BookingFlowModelBean.preDestroy() and SurveyFlowModelBean.preDestroy().

Final Thoughts

JSF portlet developers finally have a standards-based feature for creating wizard-like portlets. Gone are the integration headaches of making 3rd party flow add-ons work inside a portlet environment. The @FlowScoped annotation provides an elegant programming model and makes @ConversationScoped obsolete in many JSF use-cases. In addition, navigation between views can be fully ajaxified via f:ajax without writing any JavaScript.

All I can say is THREE CHEERS for Faces Flows!

+1 +1 +1 (pronounced Hip Hip Hooray in the olden days)

 

Announcement: Liferay Faces 3.1.3-ga4 Released

Company Blogs 6. September 2013 Von Neil Griffin Staff

On September 5, 2013 Liferay released the 4th General Availability (GA) release of Liferay Faces:

  • Liferay Faces 3.1.3-ga4 (JSF 2.1 + Liferay 6.1.x -- including 6.1.2 CE and 6.1.30 EE)
  • Liferay Faces 3.0.3-ga4 (JSF 2.1 + Liferay 6.0.x)
  • Liferay Faces 3.0.3-legacy-ga4 (JSF 2.1 + Liferay 5.2.x)
  • Liferay Faces 2.1.3-ga4 (JSF 1.2 + Liferay 6.1.x)

Project Links

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Release Highlights

This is a maintenance release that has 35+ bug fixes25+ improvements, and 5+ new features. For full details, please refer to the Release Notes. This is the first release of Liferay Faces that has been certified as being compatibile with the new Liferay Portal 6.1.2 CE GA3 and 6.1.30 EE GA3 releases.
 

VDLDocs

The Facelet taglib documentation has been moved out of the PDF documentation directly into the taglib files and Facelet Composite Component files. We are now using the vdldoc project to generate View Description Language (VDL) documentation: http://docs.liferay.com/faces/3.1/vdldoc/
 

Updated Wiki Articles

Many of the Liferay Faces wiki articles have been updated with instructions for deploying JSF portlets on various servers ( GlassFish, Jetty, JBoss AS, Resin, Tomcat, WebLogic, and WebSphere) as well as upgrading Mojarra and Weld.
 

New Demo: jsf2-spring-portlet

In order to test the Spring Framework, we developed a new jsf2-spring-portlet demo that shows how to use annotations like javax.inject.Injectjavax.inject.Named, and org.springframework.context.annotation.Scope("request").
 

Critical Bug Fixes / Improvements

It is no longer necessary to specify the Mojarra ConfigureListener or the Liferay Faces BridgeSessionListener in the WEB-INF/web.xml descriptors of portlets. In addition, the following is a list if critical bug fixes / improvements:

  • [FACES-1706] - Upgrade 3.1.x and 2.1.x branches from Liferay Portal 6.1.1 to Liferay Portal 6.1.2 API
  • [FACES-1656] - Provide ability to discover Mojarra InjectionProvider during execution of the JSF lifecycle
  • [FACES-1655] - Enable zero-config of com.liferay.faces.bridge.servlet.BridgeSessionListener by registering it in liferay-faces-bridge-impl!META-INF/bridge.tld
  • [FACES-1664] - Develop shared library modules for WebLogic
  • [FACES-1675] - Add reference to jsf shared library to weblogic.xml descriptors
  • [FACES-1619] - UnsupportedOperationException when trying to add JSF portlets to a portal page dynamically
  • [FACES-1674] - Resource libraries/collections are not marked as being added to the <head>...</head> section of the portal page
  • [FACES-1713] - liferay-ui:input-editor does not store aui:script text in WebKeys.AUI_SCRIPT_DATA request attribute during ajax requests on versions of Liferay Portal prior to 6.1.2/6.1.30

Thank You

Thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

Maven Tip: Activating Profiles With Multiple Conditions

General Blogs 10. August 2013 Von Neil Griffin Staff

When working with Maven profiles, sometimes you need to activate a profile when multiple conditions are true. Although the <activation> element in pom.xml lets you specify more than one condition, the conditions are evaluated with the OR operator rather than the AND operator.

When Maven executes profiles, it executes them in the following manner:

  • Profiles that were specified with the "-P" command line switch, according to their order of appearance in the pom
  • All other profiles that might conditionally activate, such as profiles that activate based on the existence of a file in the current module

Using this knowledge of profile execution, I came up with a way of activating profiles when multiple conditions are true, based on the presence of a temporary file whose name has one or more property values.

HOWEVER... this only works when Maven is executed in a directory that contains a parent pom. It does not work in a sub-module (like a war project), because the temporary file is created after all of the profiles have been activated.

Example: Only include Xerces as a dependency for portlet WAR projects that are to be deployed on WebLogic:

<profiles>
    <!-- The following profile must appear before other profiles -->
    <!-- and is activated only when WEB-INF/portlet.war is found -->
    <profile>
        <id>activate-portlet-war</id>
        <activation>
            <file>
                <exists>src/main/webapp/WEB-INF/portlet.xml</exists>
            </file>
        </activation>
        <build>
            <plugins>
                <plugin>
                    <artifactId>maven-antrun-plugin</artifactId>
                    <executions>
                        <execution>
                            <phase>generate-resources</phase>
                            <goals>
                                <goal>run</goal>
                            </goals>
                            <configuration>
                                <target>
                                    <touch file="target/${app.server.type}-portlet-war-activation.tmp" />
                                </target>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>
            </plugins>
        </build>
    </profile>
    <!-- The following profile is activated with "-P weblogic" on the command line -->
    <profile>
        <id>weblogic</id>
        <properties>
            <app.server.type>weblogic</app.server.type>
        </properties>
    </profile>
    <!-- The following profile is activated only for weblogic portlet wars -->
    <profile>
        <id>weblogic-portlet-war</id>
        <activation>
            <file>
                <exists>target/weblogic-portlet-war-activation.tmp</exists>
            </file>
        </activation>
        <dependencies>
            <dependency>
                <groupId>xerces</groupId>
                <artifactId>xercesImpl</artifactId>
                <version>2.11.0</version>
            </dependency>
        </dependencies>
    </profile>
</profiles>

This is an approach that can be used in Maven 2/3. Perhaps MNG-4565 will be implemented as a feature in some future version of Maven.

Running Windows XP Professional with VMWare Fusion and Multiple Processors

General Blogs 2. August 2013 Von Neil Griffin Staff

I was recently installed a ".vmdk" image into VMware Fusion on a MacBook Pro with multiple processor cores. The operating system in the image was Windows XP Professional with Service Pack 3. After I installed the image, I assigned 4 processors to the VM using VMWare Settings. But after I started the VM, I noticed that the XP Task Manager was showing only 1 processor.

I did some searching on the web and found that XP Professional supports multiple processors, but the VMware Community forums had a lot of unanswered questions. Finally I found a VMware Knowledge Base article titled Modifying the Hardware Abstraction Layer (HAL) for a Windows virtual machine (1003978) that provided some guidance.

In the Device Manager, I double clicked on the "Computer" node in the tree and it expanded to show a "Single Processor PC" node. I then right clicked on that node and left clicked on "Update Driver" and after a reboot, it showed "Multiprocessor PC" and the Task Manager was showing multiple CPUs.

You can verify this further by following these steps:

  • Open Windows Explorer
  • Navigate down to C:\WINDOWS\system32
  • Right click on the hal.dll file and left click on "Properties"
  • Click on the Version tab
  • Click on the Internal Name list item

If the value is halmacpi.dll then the Windows HAL is setup for multiple processors.

Hope this helps somebody in the future so that they don't have to spend as much time on this as I did.

Announcement: Liferay Faces 3.1.2-ga3 Released

Company Blogs 3. Juni 2013 Von Neil Griffin Staff

On June 1, 2013 Liferay released the 3rd General Availability (GA) release of Liferay Faces:

  • Liferay Faces 3.1.2-ga3 (JSF 2.1 + Liferay 6.1.x)
  • Liferay Faces 3.0.2-ga3 (JSF 2.1 + Liferay 6.0.x)
  • Liferay Faces 3.0.2-legacy-ga3 (JSF 2.1 + Liferay 5.2.x)
  • Liferay Faces 2.1.2-ga3 (JSF 1.2 + Liferay 6.1.x)

Project Links

Version Scheme

Please refer to the Liferay Faces Version Scheme wiki article for a detailed explanation of the version numbering.

Release Highlights

This is a maintenance release that has 50+ bug fixes20+ improvements, and 10+ new features. For full details, please refer to the Release Notes.
 

New Feature: CDI Support

One of the exciting new features in this release is support for Contexts and Dependency Injection (CDI), thanks to the new Liferay CDI Portlet Bridge. We developed a new jsf2-cdi-portlet demo that shows how to use annotations like javax.inject.Injectjavax.inject.Named, and javax.enterprise.context.RequestScoped. For more information, refer to the new Developing JSF Portlets with CDI wiki article.
 

Critical Bug Fixes

  • [FACES-224] JSF 2.x f:viewParam feature not working due to RenderRequestPhaseListener stopping lifecycle phase execution after RESTORE_VIEW phase
  • [FACES-257] Bridge generates URLs that can be incompatible with Liferay friendly URLs
  • [FACES-1463] References to BridgeRequestScope instances causing memory leak
  • [FACES-1470] Memory leak for RequestScoped, SessionScoped, and ViewScoped managed-beans when running under Mojarra + JBoss AS
  • [FACES-1496] Memory leak with Mojarra and JSF2 resources
  • [FACES-1591] ViewExpiredException when Ajax is used on WebLogic

Testing

We have strengthened our commitment to quality with a new suite of automated integration tests that utilize Selenium via Arquillian. The tests exercise the Liferay Faces demo portlets and also verify bug fixes with issue tester portlets. For example, the FACES-257 Selenium Test exercises the FACES-257-portlet in order to verify that f:viewParam is working in conjuntion with Liferay friendly URLs.

Thank You

Thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

JSFCentral Interview: Neil Griffin on Liferay Projects, Portlets, and JSF

Company Blogs 16. Januar 2013 Von Neil Griffin Staff

I really enjoyed the JSFCentral Interview by Kito Mann. The podcast was posted on December 06, 2012.

 
Some of the topics we discussed:
  • Liferay Portal
  • Liferay Faces
  • JSR 329
  • CDI

Contributing to Liferay Faces

Company Blogs 21. Dezember 2012 Von Neil Griffin Staff

Note: This blog post has been moved to the Liferay Faces Wiki.

Announcement: Liferay Faces 3.1.1-ga2 Released

Company Blogs 12. Dezember 2012 Von Neil Griffin Staff

On December 11, 2012 Liferay released the 2nd General Availability (GA) release of Liferay Faces:

  • Liferay Faces 3.1.1-ga2 (JSF 2.0/2.1 + Liferay 6.1.x)
  • Liferay Faces 3.0.1-ga2 (JSF 2.0/2.1 + Liferay 6.0.x)
  • Liferay Faces 2.1.1-ga2 (JSF 1.2 + Liferay 6.1.x)

Project Links

Version Scheme

For information on the Liferay Faces Version Scheme, refer to the Liferay Faces Wiki article.

Release Highlights

This is a maintenance release that fixes several bugs including a memory leak (documented in FACES-1445). Liferay recommends that all JSF portlet projects be upgraded to this new version. Please refer to the Release Notes for more information.

Thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

Announcement: PrimeFaces Technology Partnership

Company Blogs 31. Oktober 2012 Von Neil Griffin Staff

Liferay has entered into a new technology partnership with PrimeTek Informatics, maker of PrimeFaces.

Customers who have purchased Liferay EE and PrimeFaces PRO now enjoy the benefit of a communication channel between our companies, so that technology issues can be resolved in accordance with corresponding Service Level Agreements (SLAs). In addition, this partnership will ensure that our mutual customers will be able to develop PrimeFaces portlets that can be used in conjunction with the Liferay Faces Alloy component suite.
 

Please vote for Liferay to serve on the JCP Executive Committee

Company Blogs 28. Oktober 2012 Von Neil Griffin Staff

UPDATE: 10/30: Congratulations to the London Java Community and to CloudBees! And thanks to everyone who voted for Liferay.
 

UPDATE 10/19: Liferay Sr. Software Architect Ray Augé spoke on behalf of Liferay on the "Meet the EC Candidates" call. You can listen to Ray on the MP3 recording from 19m 50s - 23m 35s.
 

This year Liferay is running for election to serve on the JCP Executive Committee. To my great surprise, Liferay nominated me to be the company's representative. I'm truly honored to be nominated, and if we are elected, we will endeavor to serve the Java community well.
 
Here is the company description that we submitted for the 2012 Executive Committee Nominations page:
 
Liferay is an open source software company that is dedicated to the success of the Java platform. As a privately held company, we are free from investor pressures which in turn makes us free to serve the best interests of our 70,000+ member community. We have benefitted greatly from the contributions and feedback of our community members and strongly believe in open/transparent processes. We will strive to contribute this experience if we are elected to serve on the JCP Executive Committee.
 
We also submitted a brief Position Statement.
 
If you are a member of the JCP, please cast your vote for Liferay! The voting period is from October 16, 2012 - October 29 2012. We would treasure your vote and would be honored to serve.
 
Thank you,
 
Neil
 

Announcement: Liferay Faces in Maven Central

Company Blogs 31. August 2012 Von Neil Griffin Staff

The new location for downloading Liferay Faces artifacts (JARs, WARs, etc.) is Maven Central.

As part of the migration of Liferay Faces from portletfaces.org to liferay.com, the repository.portletfaces.org Nexus repository is being phased-out. Now that the artifacts are in Maven Central, developer should remove the following repository from project pom.xml files:

<repositories>
  <repository>
    <id>maven2-repository-portletfaces.org</id>
    <url>http://repository.portletfaces.org/content/repositories/liferay-releases</url>
  </repository>
</repositories>

Announcement: Liferay Faces 3.1.0-ga1 Released

Company Blogs 22. August 2012 Von Neil Griffin Staff

UPDATE: Liferay Faces in Maven Central

On August 22, 2012 Liferay issued a press release announcing the first General Availability (GA) release of Liferay Faces:

  • Liferay Faces 3.1.0-ga1 (JSF 2.0/2.1 + Liferay 6.1.x)
  • Liferay Faces 3.0.0-ga1 (JSF 2.0/2.1 + Liferay 6.0.x)
  • Liferay Faces 2.1.0-ga1 (JSF 1.2 + Liferay 6.1.x)

Project Links

Version Scheme

For information on the Liferay Faces Version Scheme, refer to the Liferay Faces Wiki article.

Release Highlights

We recently announced that Liferay Faces Bridge Certified was certified as JSR 329 Compliant. As a result of this certification, we released a JSF 1.2 compatible version that that developers can use to migrate legacy portlets to Liferay Faces.

Once again, thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

Notes no longer available in Mail.app with Mountain Lion

Company Blogs 15. August 2012 Von Neil Griffin Staff

If you have used the "New Note" feature in Mail.app, then you may have noticed that the feature is gone in Mountain Lion. Although I was generally happy with the new Mountain Lion features, this completely disrupted my daily workflow process.

I used the Notes feature to create pseudo "Tasks" as part of a GTD type of workflow. This allowed me to keep tasks and email messages in different folders. Even though the feature is now gone, I found that I am still able to do the same type of thing with draft email messages. For example:

  • Create a new email message
  • Leave the recipient list blank
  • Give it a subject like "Task: Do this and that"
  • Type in some instructions in the email body
  • Save the email message as a Draft
  • Move the message from the Draft folder to some other folder, like "Today"

The only problem was that I wasn't able to edit the messages after I moved them out of drafts. As a workaround, it can still be edited by moving it temporarily back to drafts.

 

Announcement: Liferay Faces Bridge Certified as JSR 329 Compliant

Company Blogs 9. August 2012 Von Neil Griffin Staff

On behalf of Liferay, I'm pleased to announce that as of August 8, 2012, Liferay Faces Bridge (a sub-project of Liferay Faces) has been certified by Oracle as compliant with JSR 329.

JSR 329 is the "Portlet 2.0 Bridge for JavaServer™ Faces 1.2" specification by the JCP. Liferay Faces Bridge 2.1.x has received the official certification (since it is designed for Portlet 2.0 and JSF 1.2). Although Liferay Faces Bridge 3.1.x is designed for Portlet 2.0 and JSF 2.0, it also passes all of the tests in the JSR 329 Technology Compatibility Kit (TCK).

I'd like to extend my personal thanks to Michael Freedman of Oracle -- as the Chairman of the JSR 329 Expert Group, he spent countless hours working on the specification and TCK. He is also a wonderful mentor and friend.

Announcement: Liferay Faces 3.1.0-RC2 Released

Company Blogs 14. Juli 2012 Von Neil Griffin Staff

On behalf of Liferay, I'm pleased to announce the latest release of Liferay Faces:

  • Liferay Faces 3.1.0-RC2 (Compatible with Liferay 6.1.x)
  • Liferay Faces 3.0.0-RC2 (Compatible with Liferay 6.0.x)

Project Links

RC2 Status

The release has been designated RC2 (instead of GA1) because there have been significant changes since the release of RC1, and we wanted to be able to give the community time to kick the tires and provide feedback:

  1. FACES-1307: The new liferay-faces-bridge-api.jar artifact has replaced portlet-bridge-api.jar from Apache MyFaces
  2. FACES-1349: The new liferay-faces-util.jar artifact contains common classes/interfaces (see issue details for repackaging and renaming of classes)
  3. FACES-1286: The Public Render Parameters IPC feature has been modified in order to properly comply with the requirements of the JSR 329 Specification.
  4. FACES-1346: The new test/bridge-tck/bridge-tck-runner project provides run the JSR 329 TCK, and 100% of the TCK tests are passing in Liferay 6.1 and Pluto 2.0.3.

Release Highlights

We've been busy since the release of RC1 (about 45 days ago). The release notes provide summary of over 100 resolved issues, and as shown in the chart below, we've really gotten ahead of the curve.

Thanks to everyone in the community that reported issues, contributed patches, and participated in the forums!

Zeige 1 - 20 von 43 Ergebnissen.
Elemente pro Seite 20
von 3