configuration files under osgi/config

configuration files under osgi/config can be system-wide or portlet level configuration

Comments

Post a Comment

Popular posts from this blog

AWS Web App 3-tier Architecture

Image
1. A user will query Route 53 for an alias record. 2. Using the alias record, the user will go straight to Elastic Load Balancer which is in the public subnet as it has to be accessible from the World Wide Web(WWW). 3. Behind the ELB, There is the Auto Scaling Group. In order for the ASG to be highly available, it is split between two Availability Zones. The ASG spins up EC2 instances (4 instances and two in each AZ in the diagram). 4. The ELB spreads out the load onto each instance. Instances can be added as scale-out or removed as scale-in which allows the ASG to be responding to high traffic or low traffic. 5. The instances usually talk directly to RDS (Relational Database Service) database to do some operations. For resilience to failure, RDS master has RDS slave (standby replica) using cross-AZ replication. If the master RDS db fails, the application automatically fall over to RDS slave. 6. ElastiCache cluster (mainly Redis) allow the application to read stuff o...
Read more

default frontend success message from action command

SessionMessages.add(actionRequest, SessionMessages.KEY_SUFFIX_HIDE_DEFAULT_SUCCESS_MESSAGE); "javax.portlet.init-param.add-process-action-success-action=false" Component properties on portlet Is this to disable the default liferay frontend success popover thing? By convention we've been doing that in the component properties on the portlet.
Read more