Arise Quickstart

This quickstart talks about two files that you can get from the download page, namely arise-run.jar and ariseservice.war.

Starting the GUI

The dist contains a runnable archive which contains all classes necessary to run Arise:

    java -jar arise-run.jar

This should bring up the starting window. In order to do something, you must connect to, or in this case create, an Engine. Try CTRL-N or File -> New ... to do so.

This brings up the workarea dialog, where you will create an Engine and set up a workarea for it. An Engine is a named interpreter for a given language. It lives in a VM until it is closed.

To get one running, you must state name and language. In the runnable archive, you can type in "beanshell" or "piji" (default) as possible languages. Give it a nice name, too, if you want to.

When your workarea is up, type in an expression. Then press CTRL-B to evaluate the entire buffer, or mark the sub-expression you want and press CTRL-E.

If the result (display in the console below) was OK and not a primitive type, you might want to inspect it. Type CTRL-I to bring up the inspector.

Enable Remote Operation

You might have noticed the Remote checkbox in the workarea dialog. To work against a remote Engine, you need to have a Servlet or EJB container nearby. If you have a JBoss server, you are in luck, because that is the only one we have tested on. Otherwise, a Servlet 2.3 container such as Tomcat 4.x will work.

The simplest Remote protocol we support is HTTP, which means you have to deploy ariseservice.war in your favorite web container.

On JBoss and/or Tomcat or Jetty, the URL of the servlet will be:

    http://<host>:8080/ariseservice/ServiceInvoker

Try it out in a browser. It will respond to GET with a short summary of its well-being, such as:

   I am net.sf.arise.delegate.ServiceInvokerServlet@a732a4
    Number of requests received : 0
    Number of responses sent    : 0

After that, bring up the new workarea dialog again, and check the Remote checkbox. The URL field will be enabled, so type in (or verify) the same URL as we tried above. The Engine you create this time will be instantiated on the server. Now go!

If you are on JBoss, the variable "mbeanserver" will be bound to its MBean server, regardless of language. So try evaluating the expression mbeanserver, and bring up the inspector on it afterwards.

Piji manual