Skip to content

Native Java Interface

Native Classes

Native Java classes can be declared in a WebDSL application in order to interface with existing libraries and code.

The supported elements are properties, (static) methods, and constructors. The supported types are

  • WebDSL type - Java type
  • Int - int or Integer
  • Bool - boolean or Boolean
  • Float - float or Float
  • String - String

Both the primitive type and the object types such as int and Integer can be produced by the WebDSL call (so overloading between these types is a problem here).

Add Java classes to a nativejava/ dir next to your app file and jar files in lib/.


native class nativejava.TestSub as SubClass : SuperClass {
  prop :String

native class nativejava.TestSuper as SuperClass  {
  static getStatic(): String
  returnList(): List<SubClass>

page root() {
  var d : SuperClass := SubClass()  

  var s : SubClass := SubClass()


  for(a: SubClass in d.returnList()){

(Example taken from compiler tests, source


Passing a native java instance as page argument

If you want an instance of your defined native java class to be passed as page (or ajax template) argument, the class should be serializable for WebDSL. From WebDSL version 1.3.0 and on, support is added for doing this by implementing the following 2 methods in your java class. (If you use a class defined in a library, you may need to extend this class with the following methods)

public static YourClass fromParamMap( Map<String,String> paramMap )
public final Map<String,String> toParamMap()

note: The keys in the returned Map may only consist of character classes [A-Z][a-z][0-9], values may hold any value as they get filtered. On deserialization, the static fromParamMap method is invoked and its result is cast to the type as defined in the page/java template definition.

Examples can be found (notice the link ;)) in WebDSL's source code itself.

Back to top