Interesting and useful content is a necessity on any web site, particularly on those built around a Content Management System. However, this may not be the only necessity. Another necessity is making the browsing experience on your site pleasant for the visitor, and in this context, making the content easy to find. Having content on the front page of the site is one way to make it findable, but the amount of content is limited to a point before the page becomes unwieldy. In this article by J. Ayen Green, we will make it easier for site visitors to find our content in a number of ways.Read Making Content Findable in Drupal 6 in full
In this article by Wolfgang Niefert, you will learn about the Advanced data migration tools, xFusion Studio in particular. You will also get to know a few tips and recommendations which you could use in your own project.Read Data Migration Scenarios in SAP Business ONE Application- part 2 in full
In this article by Christer Edwards, we will explore FreeBSD Jails. FreeBSD Jails are a kernel-level security mechanism which allows you to safely segregate processes within a sandbox environment. Jails are commonly used to secure production network services like DNS or Email by restricting what a process can access. In the case of a malicious attack on one service, all other Jailed processes would remain secure. FreeBSD Jails securely limits, in an administratively simple way, the amount of damage an attacker can do to a server.Read Securing Network Services with FreeBSD Jails in full
In the previous part of the article by Jonathon Wong and Rupert Howell, we looked at Defining and creating a Java service, Service parameters, Special unchecked (unmatched) IN/OUT parameters, and Security-related programming. In this part, we will look at the following:
- Calling services from code (using dispatcher)
- IN/OUT parameter mismatch when calling services
- Sending feedback; standard return codes success, error and fail
- Implementing Service Interfaces
- Synchronous and asynchronous services
- Using the Service Engine tools
- ECAs: Event Condition Actions
In this two-part article by Jonathon Wong and Rupert Howell, we will be exploring the Service Engine. Services in OFBiz operate in a Service Oriented Architecture (SOA). These services not only have the ability to invoke other services internally, but can also be 'opened up' and invoked by remote applications using, amongst other methods, the widely adopted messaging protocol SOAP.
Besides serving as a platform for interoperability, OFBiz services also offer us additional capability to organize our code. The traditional organizational strategies in object-oriented Java were a great improvement over the procedural paradigm. Wrapping both methods and variables together into objects to form a powerful "behavioral model" for code organization (where object's methods and variables define their behavior). Similarly with OFBiz services we are able to bundle groups of behavior together to form a coherent "service". We can say that OFBiz services, in terms of code or software organization, operate at a higher level than Java object-oriented organizational strategies.
In this part, we will be looking at:
- Defining and creating a Java service
- Service parameters
- Special unchecked (unmatched) IN/OUT parameters
- Security-related programming
In this article by Dave Newton we will learn how to modify the built-in themes and templates of Struts 2. We'll introduce a requirement to a recipe entry screen to have some different behavior when there is a validation error. The default behavior now is to change the style of the label and print the error message above the field. We'd like to highlight the entire row as a gentle reminder that our user has left out something important.Read Themes and Templates with Apache Struts 2 in full
This is the second part of two-part article by Vivek Thakur on N-Layer Architecture with ASP.NET 3.5. In the first part we saw the need for a 3-layered solution and examined ER-diagrams, domain models and UML. In this part we will we will explore a 1-tier 3-layer Architecture using a Domain Model and Object Data Source Controls.Read ER Diagrams, Domain Model, and N-Layer Architecture with ASP.NET 3.5 (part2) in full
In this article by Munwar Sharrif, you will learn about the basic features of creating, editing, and managing content in Alfresco by using Alfresco Explorer. With Alfresco, you can manage any type of document, such as HTML, text, XML, Microsoft Office documents, Adobe PDF, Flash, scanned images, multimedia, and video files. You will also understand the concepts of creating and using categories and smart spaces. By the end of this article, you will have also learned how to create spaces and load them with documents.Read Implementing Document Management in Alfresco 3- part1 in full
In this two-part article by Vivek Thakur, we will learn about ER Diagrams, Domain Model, and N-Layer Architecture with ASP.NET 3.5. The 1-tier 1-layer architecture is the default style in ASP.NET and Visual Studio 2005/2008. To overcome the limitations of this style, we can further break the application code into n-layers, where the number "n" actually depends on the project requirements.
In this article we will:
- Learn the 2-layer style
- Understand ER diagrams
- Understand what a domain model is, and what UML relationships are
- Learn the 3-layer style
- Learn about object data source controls
In the previous part of the article by Sami Salkosuo, we mainly focused on creating a dynamic user interface. In this part, we will implement Tables, List, and Field Completion.Read DWR Java AJAX User Interface: Basic Elements (Part 2) in full
In this two-part article by Sami Salkosuo, we will develop samples based on DWR, which show how to dynamically change the common user interface elements such as tables and lists as well as field completion. The section on dynamic user interfaces shows how to get started with a DWR application, and it presents a user interface skeleton that will be used to hold the tables and lists sample, and the field completion (aka. autosuggest/autocomplete) sample.
The following are the sections in this article:
- Creating a Dynamic User Interface—starts with creating a web project and a basis for samples mentioned in this article
- Implementing Tables and Lists—shows us how to use DWR with them
- Implementing Field Completion—has a sample for typical field completion
In this article by Ronald Rood, we will see how events that are generated by a job or a chain step can be intercepted to enable the monitoring of jobs. After that, we will see how we can use events to start a job that is waiting for an event.Read Events in Oracle 11g Database in full
The unsung heroes of every application are the simple things like buttons, menus, and toolbars. In this article by Shea Frederick, Steve 'Cutter' Blades, and Colin Ramsay, we will cover how to add these items to our applications.
Our example will contain a few different types of buttons, both with and without menus. A button can simply be an icon, or text, or both. Toolbars also have some mechanical elements such as spacers and dividers that can help to organize the buttons on your toolbars items.
We will also cover how to make these elements react to user interaction.Read Buttons, Menus, and Toolbars in Ext JS in full
From the very beginning, it was clear that Sakai needed to exist in universities at enormous scales, supporting hundreds of thousands of students. With requirements changing and evolving, and ever-increasing user expectations, Sakai had to be able to connect with a multitude of external systems. When Sakai was designed, the specifics of the majority of the connected systems were not knowable. To adapt to these tough circumstances, Sakai supplies web services that are easy to hook into or to write. Sakai exposes services for creating and maintaining users, sites, and groups. These services are easily extensible to include any part of the Sakai framework.
In this two-part article by Alan Mark Berg and Michael Korcuska, we will look at the two main types of web service, SOAP (Simple Object Access Protocol) and Representational State Transfer (REST) (http://microformats.org/wiki/rest). We will cover already-existing web services and describe how to hook into them. If you follow the examples, you will be able to write and deploy your first service. Lastly, this article includes a few simple client-side Perl scripts that create new users using both the SOAP and RESTful approaches.Read Sakai Web Services: Connecting to the Enterprise (Part 1) in full