after org.lappsgrid.all-2.3.0 is deployed on Maven central

following these points:

1. experimental for this step is now all included in org.lappsgrid.all
2. need to specify what classes need to be imported for here

Step 1:

• mentions ANC's Nexus repository, but this is not mentioned further during step 1 or any later step
• the properties table gives groupID=org.lappsgrid.tutorial, which is different from the pom

Step 4:

• The archive with manifest files has a syntax error in the embedded bean tag (missing closing tag)

Step 5:

• Error loading WSDL: WSDLException (at /html): faultCode=INVALID_WSDL: Expected element '{http://schemas.xmlsoap.org/wsdl/}definitions'. (Update: tried this with SoapUI 5.3.0 and had no problems)

References to the parent pom and org.lappsgrid.all should be updated to the latest versions:

• parent-pom:2.0.5
• org.lappsgrid.all:2.3.1

Hello

I'm going through the tutorial and I'm having an issue in step 5 with mvn jetty:run. I get the following stacktrace:

[ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) on project lappsgrid_example: Failure: NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) on project lappsgrid_example: Failure
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failure
    at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:479)
    at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:396)
    at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210)
    at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
    ... 20 more
Caused by: java.lang.NullPointerException
    at org.mortbay.jetty.plugin.AbstractJettyRunMojo.checkWebXml(AbstractJettyRunMojo.java:358)
    at org.mortbay.jetty.plugin.AbstractJettyRunMojo.configureWebApplication(AbstractJettyRunMojo.java:383)
    at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:438)
    ... 25 more

I checked the effective POM and I am importing the jetty plugin, and I am using a carbon copy of the web.xml and pom.xml defined in the source.

• LIF is LAPPS Interchange Format
• when reading I know a lot, but what do I actually do?
• add new Java class
• call it something
• remove content and cut and paste parts of the step2 code
• add what packages need to be imported
• package need not be added

• expand on parent adding a bit
• spell out that 'packaging', 'name' and 'description' need to be added
• mention that repositories needs to be added if not done by global setting

All the unit tests in step 5 are failing. For example, testMetadata checks that the produces/required encoding is UTF-8, but the encoding is never set in the metadata.

• remove test code (testing is now step5)
• replace main source code and POM from fix #26
• minor fix in REAMDE

subtask of #2

For instance, the serialization module has both javadoc and groovydoc.
Should we worry about putting them together for later references, or at least an URL-aggregating web page?

pay special attention to the part about setting up POM with depnedencies

• helloworld
• whitespace tokenizer
• Stanford tagger
• NLTK tagger

• make clear up front that there are two alternatives
• option 1, mention that code needs to be pasted in under class definition
• there are errors after the previous step
• there is a mistake in what is pasted
• Returning Metadata, spell out that the code snippet replaces curent getMetadata method
• metadata vbl needs to be declared

This should be trivial. Replace pom.xml from the fix of #20.

subtask of #2

• spell out when unit test can be skipped
• say where to put the test
• use skeleton, then add in the two methods
• need to import LAPPS classes (easiest way: copy all from main class)
• issue with ProcessingService and WebService
• import java.util.*
• add link to file with all asserts (currently only path to it is given)
• some asserts are fixed, some service specific
• service.execute
• add link to full example code
• incompatible types (service.execute() returns String and container needs a Map)
• integration test only possible after step5 (need to re-arrange)

1. many lapps APIs now using java 8
2. apply changes in schema 1.1.0
   1. lif - added $schema, dropped label, type
   2. metadata - added licenseDesc

Due to the fact that current step 4 (testing) includes details on WAR integration test, which only can be proceeded after WAR packaging covered in step 5, two steps need to be switched.

    for (String word : words) {
        start = text.indexOf(word, start);
        if (start < 0) {
            return new Data<String>(Uri.ERROR, "Unable to match word: " + word).asJson();
        }
        int end = start + word.length();
        Annotation a = view.newAnnotation("tok" + (++id), Uri.TOKEN, start, end);
        a.addFeature(Features.Token.WORD, word);
    }

This loop is from WhitespaceTokenize.java and the bug of this code is that it forgets to add begin=end; at the end of the loop.

For example, this bug code will fail with input text "a a".
It will obtain two annotations which are token a and have the same begin and end.

Question: do we need to provide a hands-on tutorial for setting up service grid locally, and/or registering a new service to an existing service grid?

• Maven setup
• Project setup
• Lapp interfaces and base classes
• Implementation
• Service Metadata
• web.xml and generating a war file.
  • Deployment.

Taken from whitespace_tokenizer tutorial

Then go further with more examples

• wrapping external java program into a service (using stanfordnlp tagger)
• wrapping non-java program into a service (using nltk tagger)
  • call python from java (using pycaller module)
  • wrap results from python into LAPPS grid API

• breif description of the tutorial and the steps involved
• a link to advance to step one

add more details later