Search Results

All Results 107
Ordenar por
Resource Type
Deployment Approach
Capability
Feature
Payment Integration Client Extension Reference
Payment Integration Client Extension Reference Payment Integration Client Extension YAML Reference FieldValueDescription keyliferay-sample-commerce-payment-integrationSpecifies the unique key for...
Implementing a Custom Notification Type
Implementing a Custom Notification Type You can configure Liferay Commerce to send email notifications for a variety of event triggers in your store. When there's no out-of-the-box notification...
Implementing a Custom Low Stock Activity
Implementing a Custom Low Stock Activity Here, learn how to add a custom low stock activity by implementing the CommerceLowStockActivity interface. Low stock activities are actions happen...
Implementing a Custom Checkout Step
Implementing a Custom Checkout Step This tutorial shows you how to add a custom checkout step by implementing the CommerceCheckoutStep interface. A checkout step represents one screen of the...
Implementing a New Payment Method
Implementing a New Payment Method This tutorial shows you how to add a new payment method by implementing the CommercePaymentMethod interface. Payment methods represent various ways customers can...
Promotions
Promotions There are three discount rules available out-of-the-box with Liferay. But you can also use the extension point to add your own custom rules.
Implementing a New Tax Engine
Implementing a New Tax Engine This tutorial shows you how to add a new tax engine by implementing the CommerceTaxEngine interface. A tax engine performs the calculation for taxes when a...
Using Client Extensions
Using Client Extensions Liferay DXP 2024.Q1+/Portal GA112+ Using client extensions, you can extend Liferay without using OSGi modules. Deploy them to any Liferay environment, whether you host it...
Using the Payment Integration Client Extension
Using the Payment Integration Client Extension Liferay DXP 2024.Q1+/Portal GA112+ You can use a client extension to integrate with a new payment method in Liferay. This client extension from the...
Portlets
Portlets Liferay DXP started off as a portal server for Java-based web applications called portlets (see JSR 168, JSR-286, and JSR-362). Portlets process requests and generate responses like any...
Portlet 3.0 API Opt In
Portlet 3.0 API Opt In A portlet must specify version 3.0 to opt in to the Portlet 3.0 API. The 3.0 Portlet API version can be specified in the following ways. Standard Portlet @PortletApplication...
Portlet Descriptor to OSGi Service Property Map
Portlet Descriptor to OSGi Service Property Map Here's a map of portlet XML descriptor values to OSGi service properties for publishing OSGi Portlets. The properties centralize and simplify portlet...
Portlet IDs
Portlet IDs Below is a listing of the portlet IDs for the default portlets in Liferay DXP. You can use these IDs to embed portlets in your theme's sitemap. Collaboration PortletID...
Reference
Reference
Invoking Actions with MVC Portlet
Invoking Actions with MVC Portlet A portlet's Action phase applies state changes. You can bind your portlet's action-handling methods to UI components using portlet action URLs. They are...
Rendering Views with MVC Portlet
Rendering Views with MVC Portlet If you want users to access your portlet's views, you must implement navigation to them. Portlet render URLs help you do this. Here you'll deploy an example...
Reference
Reference
Using Bean Portlet
Using Bean Portlet Portlet 3.0, the JSR 362 standard, features a style of portlet development called Bean Portlets that use Contexts and Dependency Injection (CDI). Bean Portlets fully leverage all...
Liferay Faces Alloy
Liferay Faces Alloy Liferay Faces Alloy is distributed in a .jar file. You can add Liferay Faces Alloy as a dependency to your portlet projects, to use AlloyUI in a way that is consistent with JSF...
MVC Action Command
MVC Action Command MVC Action Commands handle actions as separate classes. With Action Commands, you can organize action logic in MVCPortlets that have many actions. Action URLs in the portlet's...