Generating Java code from XML in Eclipse

Question

I am working on a project that will have several Java classes that are very similar to each other, and that I would like to generate from XML files. What I would like to be able to do is change the Eclipse build process to do something like this:

Compile the code generator
Run the code generator, converting the XML to Java
Compile the rest of the project

I could do this all manually but I would prefer to be able to have Eclipse do it all for me.

Example

I want to be able to take a source XML file that looks like this:

<command-list>
    <command name="DATE" />
    <command name="GROUP">
        <capability "READER" />
        <argument "groupname" />
    </command>
    <command name="ARTICLE">
        <capability "READER" />
        <argument "message-id" optional="true" />
    </command>
</command-list>

and have it give me something similar to the following (in separate files as appropriate):

public class Date extends Command {
    public ResponseCode execute() {
        Server srv = getServer();
        srv.send("DATE");
        return srv.getResponse();
    }
}

public class Group extends Command {
    public ResponseCode execute() {
        Server srv = getServer();
        if (srv.hasCapability(Capabilities.READER) == false) {
            Log.debug("Attempting non-available capability: READER");
        }
        String groupname = getArgument("groupname");
        if (groupname == null) {
             throw new InvalidArgumentException("Require groupname");
        }
        String command = "GROUP";
        if (groupname != null) command += " " + groupname;
        srv.send(command);
        return srv.getResponse();
    }
}

public class Article extends Command {
    public ResponseCode execute() {
        Server srv = getServer();
        if (srv.hasCapability(Capabilities.READER) == false) {
            Log.debug("Attempting non-available capability: READER");
        }
        String messageId = getArgument("messageId");
        String command = "ARTICLE";
        if (messageId != null) command += " " + messageId;
        srv.send(command);
        return srv.getResponse();
    }
}

Why don't you just write a batch file/shell script to do all of this for you? One line two arguments -> Done! I am asking this because I personally do not know how you would (if possible) do this in eclipse, and it seems like you are going for ease of use here. — thatidiotguy, Aug 10 '12 at 15:32
I want it to be part of the build process, so that if I change my template or my XML it will regenerate — Kevin Lacquement, Aug 10 '12 at 18:18
@thatidiotguy you can integrate ant scripts into the build process as part of the project properties, it's under 'Builders'. I do not know if there is batch/shell script support, but I also haven't looked. — Colin D, Aug 15 '12 at 17:07

Chris Gerken · Accepted Answer · 2012-08-15T16:24:50.733

This is exactly what the JET component in the Model to Text (M2T) project was made for. In fact, you can even create the project, .classpath and any other files you need with JET.

Jet templates are as follows. Note that these templates must be named exactly as shown.

/templates/main.jet

<%@taglib prefix="ws" id="org.eclipse.jet.workspaceTags" %>
<%-- Main entry point for com.lacqui.command.xform --%>

<%-- 
  Let c:iterate tags set the XPath context object.
  For 100% compatibility with JET 0.9.x or earlier, remove this statement
 --%>
<c:setVariable var="org.eclipse.jet.taglib.control.iterateSetsContext" select="true()"/>

    <c:setVariable select="/command-list" var="command-list" />

    --- traverse input model, performing calculations and storing 
    --- the results as model annotations via c:set tag 

    <c:set select="$command-list" name="project">com.lacqui.commands</c:set>
    <c:set select="$command-list" name="commandPkg">com.lacqui.commands</c:set>
    <c:set select="$command-list" name="commandDir"><c:get select="translate($command-list/@commandPkg,'.','/')" /></c:set>

    <c:iterate select="$command-list/command" var="command" >

            - Derive the class name from the name of the command

        <c:set select="$command" name="classname"><c:get select="camelCase($command/@name)" />Command</c:set>

        <c:iterate select="$command/argument" var="argument">

            <c:if test="not($argument/@optional)">
                <c:set select="$argument" name="optional">false</c:set>
            </c:if>

        </c:iterate>

    </c:iterate>

   --- traverse annotated model, performing text generation actions 
   --- such as ws:file, ws:folder and ws:project 

   <ws:project name="{$command-list/@project}" />
   <ws:file template="templates/project.jet" path="{$command-list/@project}/.project"  />
   <ws:file template="templates/classpath.jet" path="{$command-list/@project}/.classpath"/>

    <c:iterate select="$command-list/command" var="command" >

        <ws:file template="templates/class.jet" path="{$command-list/@project}/src/{$command-list/@commandDir}/{$command/@classname}.java" replace="true"/>

    </c:iterate>

/templates/classpath.jet

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" path="src"/>
    <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
    <classpathentry kind="output" path="bin"/>
</classpath>

/templates/project.jet

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
    <name><c:get select="$command-list/@project" /></name>
    <comment></comment>
    <projects>
    </projects>
    <buildSpec>
        <buildCommand>
            <name>org.eclipse.jdt.core.javabuilder</name>
            <arguments>
            </arguments>
        </buildCommand>
    </buildSpec>
    <natures>
        <nature>org.eclipse.jdt.core.javanature</nature>
    </natures>
</projectDescription>

/templates/class.jet

package <c:get select="$command-list/@commandPkg" />;

public class <c:get select="$command/@classname" /> extends Command {
    public ResponseCode execute() {
        Server srv = getServer();
<c:iterate select="$command/capability" var="capability">

        if (srv.hasCapability(Capabilities.<c:get select="$capability/@name"/>) == false) {
            Log.debug("Attempting non-available capability: <c:get select="$capability/@name"/>");
        }
</c:iterate>        
<c:iterate select="$command/argument" var="argument">

        String <c:get select="$argument/@name"/> = getArgument("<c:get select="$argument/@name"/>");
<c:if test="$argument/@optional = 'false'" >
        if (<c:get select="$argument/@name"/> == null) {
             throw new InvalidArgumentException("Require <c:get select="$argument/@name"/>");
        }
</c:if>
</c:iterate>        

        String command = "GROUP";
<c:iterate select="$command/argument" var="argument">
        if (<c:get select="$argument/@name"/> != null) command += " -<c:get select="$argument/@name"/> " + <c:get select="$argument/@name"/>;
</c:iterate>       

        srv.send(command);
        return srv.getResponse();
    }
}

and using this model:

<command-list>
    <command name="DATE" />
    <command name="GROUP">
        <capability name="LOGGER" />
        <capability name="AUTHENTICATOR" />
        <argument name="groupname" />
    </command>
    <command name="ARTICLE">
        <capability name="READER" />
        <argument name="article-id" optional="false" />
        <argument name="message-id" optional="true" />
    </command>
</command-list>

gives a complete java project named com.lacqui.commands containing three java files:

package com.lacqui.commands;

public class ArticleCommand extends Command {
    public ResponseCode execute() {
        Server srv = getServer();

        if (srv.hasCapability(Capabilities.READER) == false) {
            Log.debug("Attempting non-available capability: READER");
        }

        String article-id = getArgument("article-id");
        if (article-id == null) {
             throw new InvalidArgumentException("Require article-id");
        }

        String message-id = getArgument("message-id");

        String command = "GROUP";
        if (article-id != null) command += " -article-id " + article-id;
        if (message-id != null) command += " -message-id " + message-id;

        srv.send(command);
        return srv.getResponse();
    }
}

and this:

package com.lacqui.commands;

public class GroupCommand extends Command {
    public ResponseCode execute() {
        Server srv = getServer();

        if (srv.hasCapability(Capabilities.LOGGER) == false) {
            Log.debug("Attempting non-available capability: LOGGER");
        }

        if (srv.hasCapability(Capabilities.AUTHENTICATOR) == false) {
            Log.debug("Attempting non-available capability: AUTHENTICATOR");
        }

        String groupname = getArgument("groupname");
        if (groupname == null) {
             throw new InvalidArgumentException("Require groupname");
        }

        String command = "GROUP";
        if (groupname != null) command += " -groupname " + groupname;

        srv.send(command);
        return srv.getResponse();
    }
}

I'm not trying to use XML as a runtime data format - I'm using it to simplify my source file generation. — Kevin Lacquement, Aug 14 '12 at 13:02
JET is a development time tool that generates code, JSP's, HTML, property files, Eclipse "dot resources", etc etc into Eclipse projects (possibly after creating and configuring those projects). That resource generation is driven by a model, usually XML but could be any format, and that model is not used at all at runtime. So JET really is a good approach for you here. Post a sample class in your question and I can post a template you might use to generate that class. — Chris Gerken, Aug 14 '12 at 15:38
How to get this working in Eclipse? I tried pasting couple of files as recommended in this answer. Created a project and enabled JET on it, and dumped the .jet files in 'template' folder. But its giving errors. I am trying to learn this and not sure how to get it working. — AnilJ, Feb 14 '17 at 19:34

score 1 · Answer 2 · answered Aug 10 '12 at 15:46

1

You might want to take a look at JaxB.

Lars Vogel did a simple tutorial if you want to take a quick look at it.
JAXB Tutorial

Also here is a benchmark test of xml unmarshaling.
XML unmarshalling benchmark in Java: JAXB vs STax vs Woodstox

answered Aug 10 '12 at 15:46

Dan

1,179
2
10
18

I'm not trying to use XML as a runtime data format - I'm using it to simplify my source file generation. – Kevin Lacquement Aug 14 '12 at 12:59

Generating Java code from XML in Eclipse

2 Answers2

Linked