antville / helma

Antville Fork of Helma Object Publisher

About Antville

Antville is an open source project providing a high performance, feature-rich blog hosting software. Antville can host tens of thousands of blogs. Server power is the only limit. Installation and use is easy.

Antville is written in server-side JavaScript and developed with Helma Object Publisher. Antville works with a relational database in the back-end.

Look at the project site for more information.

Status

Antville’s codebase is of stable quality and ready for production deployment. Try out Antville.org for a demonstration.

There still could be bugs hidden in Antville’s source code. If you find one please let us know. The creators of Antville do not take any responsibility for what the software might do.

System Requirements

To run Antville you need Helma Object Publisher and a relational database software. We tested Antville with PostgreSQL and MySQL – MariaDB should work, too.

To enable Antville sending notification e-mails you need access to an SMTP server.

Helma comes with an embedded webserver (Jetty) so you do not need to install one. Yet, you can also use the webserver of your choice.

For details please refer to the installation instructions of Helma Object Publisher and the corresponding software packages.

The INSTALL.md file contains detailed instructions to install Antville.

Documentation and Further Information

For documentation and further information about Antville you can refer to:

• project.antville.org
• about.antville.org
• help.antville.org

Feel free to ask any question about Antville at our support site.

Bug Reporting and Feature Requests

If you think you found a bug please let us know.

A great place for your feature requests or proposals is the project development site.

Antville is open-source, and we want to encourage you to change its code according to your likeness. We are curious about your ideas and suggestions. Feel free to drop us a message to [email protected] or through any channels mentioned before.

About Helma Object Publisher

Helma Object Publisher is an open source project providing a powerful, fast and scriptable web application server written in Java.

Define HopObjects and map them to a relational database table. Create, change and delete HopObjects at your whim using a comfortable object-container model. Manual fiddling around with database code is not necessary.

HopObjects extend the native JavaScript object. They got all the common features you know – and more. One highlight are the special templating features to ease the rendering of objects for the Web.

Combine HopObjects to create a hierarchical structure. A URL in Helma mirrors this structure. Each part of the URL path corresponds to a relational database mapping, similar to the document tree of static websites. Helma’s URL space is an analogy to the Document Object Model implemented in client-side JavaScript.

helma's Issues

Add support for prepared SQL statements to DatabaseObject

Currently, prepared statements are only used in the NodeManager; the DatabaseObject is using java.sql.Statement only.

Adding a method to execute prepared SQL statements should be sufficient for the now.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

---

Warning

Renovate failed to look up the following dependencies: Failed to look up maven package net.sf.javamusictag:jid3lib.

Files affected: modules/jala/build.gradle

---

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency org.eclipse.jetty:jetty-servlet to v9.4.53.v20231009
• Update dependency org.eclipse.jetty:jetty-xml to v9.4.53.v20231009
• Update dependency org.mozilla:rhino to v1.7.14
• Update dependency commons-codec:commons-codec to v1.16.0
• Update dependency commons-net:commons-net to v3.10.0
• Update dependency gradle to v8.4
• Update dependency jaxen:jaxen to v1.2.0
• Update dependency net.sourceforge.jexcelapi:jxl to v2.6.12
• Update dependency org.apache.lucene:lucene-analyzers to v2.9.4
• Update dependency org.apache.lucene:lucene-core to v2.9.4
• Update dependency ch.ethz.ganymed:ganymed-ssh2 to v262
• Update dependency dom4j:dom4j to v20040902
• Update dependency jaxen:jaxen to v2
• Update dependency org.apache.lucene:lucene-analyzers to v3
• Update dependency org.apache.lucene:lucene-core to v9
• Update dependency org.eclipse.jetty:jetty-servlet to v11
• Update dependency org.eclipse.jetty:jetty-xml to v12
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

gradle

gradle.properties

settings.gradle

build.gradle

• com.github.jk1.dependency-license-report 2.5
• com.google.code.gson:gson 2.10.1
• commons-codec:commons-codec 1.15
• commons-fileupload:commons-fileupload 1.5
• commons-logging:commons-logging 1.2
• commons-net:commons-net 3.9.0
• com.sun.mail:javax.mail 1.6.2
• javax.servlet:javax.servlet-api 4.0.1
• org.ccil.cowan.tagsoup:tagsoup 1.2.1
• org.eclipse.jetty:jetty-servlet 9.4.51.v20230217
• org.eclipse.jetty:jetty-xml 9.4.51.v20230217
• org.mozilla:rhino 1.7.13
• xerces:xercesImpl 2.12.2
• xmlrpc:xmlrpc 2.0.1

launcher/build.gradle

modules/helma/build.gradle

• ch.ethz.ganymed:ganymed-ssh2 build209
• net.sourceforge.jexcelapi:jxl 2.5.7
• org.apache.lucene:lucene-analyzers 2.2.0
• org.apache.lucene:lucene-core 2.2.0

modules/jala/build.gradle

• dom4j:dom4j 1.6.1
• jaxen:jaxen 1.1-beta-8
• net.sf.javamusictag:jid3lib 0.5.4

modules/jala/util/HopKit/build.gradle

• bsf:bsf 2.4.0

modules/jala/util/Test/build.gradle

• org.subethamail:subethasmtp-smtp 1.2
• org.subethamail:subethasmtp-wiser 1.2

gradle-wrapper

gradle/wrapper/gradle-wrapper.properties

• gradle 8.3

---

• Check this box to trigger a request for Renovate to run again on this repository

Build fails on macOS

The --info=progress2 option is not supported on macOS 😬

Side-effects in jetty8 branch

With 51b5712 I cherry-picked (hopefully all?) changes for integrating Jetty 8 from @lehni’s fork and noticed that it breaks either the mountpoint setting in apps.properties or the baseUri setting in app.properties (or both).

Attached a test case which should demonstrate the issue.

Using the master branch there should be displayed success under the URL http://localhost:8080/helma/test while with the jetty8 branch a status 500 (“Object not found”) is returned.

(Are there any other side-effects?)

Prerequisites for building Helma

It went rather unnoticed on a rather fully equipped Linux machine that the following prerequisites are needed to build Helma:

• Java 😜
• npx (NodeJS)
• rsync

This should at least be documented (Java is already, afair).

Untangle Helma for an Extended JavaScript Approach

The idea is to extract Java code from Helma and transform it into compatible JavaScript code. Ideally, this JS code would be running with Rhino as well as V8 (NodeJS) or even other engines.

Feasible

• Global Object
• HopObject (as far as no database is involved)
• Skin rendering (i.e. templating; additionally, a popular template framework could be added, e.g. Mustache)
• Java imaging
• Repositories
• Request/response framework (servlet, session?)
• Helma extensions (DatabaseObject, FileObject etc.)
• Command-line runner
• HTTP server
• DOM handling

Laborious

• Code in util (Base64, CacheMap etc.)
• Find and implement replacements for Java libs in userland (e.g. Rome in Antville)
• HacHspConverter

Problematic

• Application framework (i.e. core)
• Database layer / object model (INode et al.)

Add support for jEnv

jEnv is a command line tool to help you forget how to set the JAVA_HOME environment variable

As a first step, simply add the .java-version file. This only contains the version number (e.g. 11.0).

Might come in handy using with Gradle's Java settings…?

Build fails on macOS (rsync)

The --info=progress2 option is not supported on macOS 😬

Evaluate progress in zoesolutions fork

https://github.com/zoesolutions/helma