6. Creating Java-backed Web Scripts | Learning Alfresco Web Scripts

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Learning Alfresco Web Scripts

By : Ramesh Chauhan

4.5 (4)

Learning Alfresco Web Scripts

4.5 (4)

By: Ramesh Chauhan

Overview of this book

If you are an Alfresco developer who has no experience with web scripts and you want to start developing Alfresco web scripts, then this book is definitely for you.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Getting Familiar with Web Scripts

1. Getting Familiar with Web Scripts

Understanding web scripts

Reasons to use web scripts

Understanding when to use a web script

Understanding where web scripts can be used

Understanding how web scripts work

Types of web scripts

Summary

2. It's Time for the First Web Script

2. It's Time for the First Web Script

Creating your first web script in Alfresco

Understanding the web script URI

Adding arguments to a web script

Extending the first web script to use the controller

Behind the scenes of web script execution

Important things for any web script

Summary

3. Understanding the Web Script Framework

3. Understanding the Web Script Framework

Execution flow of web scripts

Components of the web script framework

Deployment architecture

Summary

4. Building Blocks of Web Scripts

4. Building Blocks of Web Scripts

The description document – it's a must!

Controller implementation – not mandatory!

Response templates – yes, they are required!

I18N for a web script – it's optional

Configuration document – it's optional

Naming conventions – the most important thing

Summary

5. Invoking Web Scripts

5. Invoking Web Scripts

Invoking a web script from a web browser

Executing a web script using web browser plugins

Executing a web script from standalone Java program

Calling web scripts from Spring-based services

Invoking a web script from Alfresco Share

Calling a web script from JSR-168 portals and the JSF page

Dealing with client limitations

Summary

6. Creating Java-backed Web Scripts

6. Creating Java-backed Web Scripts

Use case scenario

Web script functionality at a high level

Getting ready

Creating a description document

Creating a response template

Creating a Java controller

Configuring the controller for the web script

Deploying the web script

Testing the web script

DeclarativeWebScript versus AbstractWebScript

Using controllers smartly

Summary

7. Understanding JavaScript-based Web Scripts in Detail

7. Understanding JavaScript-based Web Scripts in Detail

Understanding what you can do with the JavaScript API

JavaScript APIs in Alfresco

A must-know ScriptNode API

Code examples

Creating your own root object

Summary

8. Deployment, Debugging, and Troubleshooting Web Scripts

8. Deployment, Debugging, and Troubleshooting Web Scripts

Deployment options

Debugging web scripts

Troubleshooting pointers

Web scripts on a production server

Summary

9. Mavenizing Web Scripts

9. Mavenizing Web Scripts

Setting up your environment

Creating the default project structure for AMP

Generating AMP from the default project

Setting up a development environment with Eclipse

Understanding the default project structure

Extending your default project to create web scripts

Applying AMP to the Alfresco WAR for testing

Summary

10. Extending the Web Script Framework

10. Extending the Web Script Framework

Custom implementation of the web script runtime

The custom implementation of a web script container

Custom authenticator implementation

Custom script processor implementation

Custom template processor implementation

Customizing formats

Summary

Index

Index

Customer Reviews

4.5 (4)

5 star

50%

4 star

50%

3 star

0

2 star

0

1 star

0

Creating a response template

As a rule of thumb for a web script, we have to follow the naming convention as expected by the web script framework in Alfresco. As the web script is supposed to return the response in the JSON and XML formats, we need to create two response templates for the web script. Following the naming conventions, there are two files to be created—contentlocation.get.json.ftl and contentlocation.get.xml.ftl as response templates. Return filesystem_location and size in the response as follows:

To create a JSON response template, create a file named contentlocation.get.json.ftl that has the following content:
```
{
  "content" :
  {
    "filesystem_location" : "${contentFSLocation}",
    "size" : ${contentSize}
  }
}
```

To create an XML response template, create a file named contentlocation.get.xml.ftl that has the following content:

<?xml version="1.0" encoding="UTF-8"?>
<content>
  <filesystem_location>${contentFSLocation}
  </filesystem_location>
  <size...

Search

Your notes and bookmarks