Placing web scripts in the classpath lets you package and deploy them with other extensions that comprise your solution. You can install them using standard Content Services tools without having to upload them into the repository. However, it might not be as convenient to edit them while developing them as if they were located in the Alfresco
content repository where you can easily edit them using Alfresco Share. You can also export and import web scripts in
the content repository using the ACP (Alfresco Content Package) mechanism.

Web scripts let you implement your own RESTful API without tooling or Java knowledge, requiring only a text editor. This approach to developing an Content Services API means that web scripts offer many advantages over existing
technologies, including ease and speed of development, and flexibility in API design. By focusing on the RESTful
architectural style, web scripts let you build custom URI-identified and HTTP accessible content management web services
backed by the Content Services server. The following sections discuss how authors may create documents that work
for user agents that don’t support scripting. The type attribute must be specified for each
SCRIPT element instance in a document.

Content Stores

Therefore, the Web Script Framework uses the common practice of allowing text to be placed into resource bundles, where
a resource bundle exists for each supported language. HTTP Basic authentication is a method designed to allow a web browser or other client program to provide credentials in
the form of a user name and password when making an HTTP request. An authenticated web script has access to all the services of the Content Services server and thus can perform
any operation, although it still adheres to the permissions of the authenticated user. The Web Script Framework does not invent its own caching approach but relies on the caching protocol defined by HTTP. Each web script specifies how it is to be cached, which the Web Script Framework translates into appropriate HTTP headers
when it is invoked. A third party HTTP cache that is deployed as part of the application then caches the web script
response.

These resources are manipulated using
HTTP requests where the method (GET, POST, PUT, DELETE) has specific meaning. Webscripts can also be activated on a schedule, providing a simple way to build monitoring or other automation. Webscripts respond to HTTP requests, making them easy to call from web and mobile apps. The embedded music block can be shared using WebScript into various music applications to reach a bigger target audience.

Adding resource bundles for additional languages

Web script developers have access to the value provided for each token in both the controller script and response template. The Web Script Framework dictates where the files are located and how
they are named. This allows the framework to automatically locate and register web scripts without having to tell the
framework where they are. In some cases, a web script can fall back to Java or rely on advanced Web Script Framework
features where scripting alone cannot support the requirements of the web script. You can call existing web scripts or create your own web scripts for new scenarios. For example, you can create your
own web script to expose a RESTful interface onto a custom content repository extension.

If the value of status.redirect is set
to false, the status code is set on the response, but the response template for the requested format is rendered anyway. Server-side scripting is often used to provide a customized interface for the user. These scripts may assemble client characteristics for use in customizing the response based on those characteristics, the user’s requirements, access rights, etc.

Contents

For instance, authors may want to include press buttons in their documents
that do not submit a form but still communicate with a server when they are
activated. This specification includes more detailed
information about scripting in sections on script macros. Following sections will go into more details about how
to write web page scripts. You can do so in any supported
Kawa language, including Scheme, BRL, KRL, or XQuery. There are advantages to both types of language, but we won’t discuss them right now. Programs that run on a user’s local computer without ever sending or receiving data over a network are not considered clients, and so the operations of such programs would not be considered client-side operations.

Compiled languages on the other hand are transformed (compiled) into another form before they are run by the computer. For example, C/C++ are compiled into machine code that is then run by the computer. The program is executed from a binary format, which was generated from the original program source code. This is a good security measure — if this were not the case, then pirates could start writing code to steal information from other websites, and other such bad things. What is even more exciting however is the functionality built on top of the client-side JavaScript language.

Overriding the default message bundle

This is achieved by setting an override header named X-HTTP-Method-Override on the HTTP request whose value is the
method name to invoke. However, the web browser is not the exclusive client from which to invoke a web script. Any client capable of sending
HTTP requests and receiving HTTP responses can be used. A good example is the cURL client that has full support for the
HTTP protocol and is often used for testing the various capabilities of web scripts.

• However, the URL-encoded approach is inefficient for sending large quantities of binary data or text containing non-ASCII characters.
• For instance, authors may want to include press buttons in their documents
  that do not submit a form but still communicate with a server when they are
  activated.
• To support this, the Web Script Framework provides a special root object named cache
  to all controller scripts for allowing cache controls to be set at runtime.
• A simple script might ask the reader’s name, determine the Internet address of the system that the reader uses, and print a greeting.
• Control elements such as INPUT, SELECT, BUTTON,

  TEXTAREA, and LABEL all respond to certain intrinsic events.

• User agents that don’t recognize the SCRIPT element will likely render
  that element’s contents as text.

JSR-168 Authenticator only works if running on the repository tier, and it does not work for web scripts running in the
Share tier. Tunneling HTTP methods is a last resort that should be used only when no other workaround is available. Each HTTP
method has its own characteristics such as how it is cached, which HTTP clients and intermediaries expect. When tunneling
these methods through HTTP POST, those expectations can no longer be met. The host, port, and contextPath are all predefined by where the Content Services server is installed. Web script component files are located in the file system within the Java classpath or in the repository.

This approach to developing
an Content Services API means that web scripts offer many advantages over existing technologies, including ease
and speed of development, and flexibility in API design. This can be convenient if, for example, you are working with a digital marketing partner and they want to run A/B testing with one software and then heat mapping with another software. A website script is a piece of code that is directly embedded into your website. Invisible to users on your website, scripts can add information to your website or pass along information to a third-party.

All other components are
exactly the same as those for scripted web scripts. Once you have created and registered your web script, you can add additional resource bundles for other languages. It is often necessary to cache the retrieval of content streams of documents residing in the repository as these can be
large in size. A typical setup to support this scenario (as shown in the following figure) is to place an HTTP cache proxy
between the client (for example, a web browser) and the Content Services server. In this situation, the Web Script Framework provides a mechanism for tunneling any HTTP method through a POST method.

Web Scripts Reference

APIs are ready-made sets of code building blocks that allow a developer to implement programs that would otherwise be hard or impossible to implement. A good thing about ReST is that we leverage existing HTTP methods to implement significant functionality on just a
single /acmedocs endpoint. There are no method naming uses of a script conventions to follow and the URL structure is clean and clear. When setting the authentication property to be able to read and write to the Repository we need to have these
operations wrapped in a transaction. This is automatically done as soon as we set the authentication element to
anything else than none.