• View
• Edit
• History
• Print

UpgradeFromVertX2ToVertX3

The idea is to update Ptolemy II from Vert.x 2 to 3.

Resources

• Checklist for Migrating from Vert.x 2.1.x to Vert.x 3 - Part One

How to get access to the branch

Check out the branch with:

   svn co https://repo.eecs.berkeley.edu/svn/projects/eal/ptII/branches/vertx-3-0-0 ptIIv3

Current status

25-Sep-2015: imports are fixed. jjs/modules/httpClient/HttpClientHelper.java compiles. Still to go: other files that use vert.x

• 44 ant errors, down from 67.

Notes below here about how the port was done.

Ptolemy Branch

I created a branch with

  svn copy https://repo.eecs.berkeley.edu/svn/projects/eal/ptII/trunk 
     https://repo.eecs.berkeley.edu/svn/projects/eal/ptII/branches/vertx-3-0-0 
     -m "Creating Ptolemy II branch for building with Vert.x 3.0.0.  See https://www.terraswarm.org/testbeds/wiki/Vert/UpgradeFrom2To3."

The above step is already done, you do not need to do it again

To check out the branch, use:

   svn co https://repo.eecs.berkeley.edu/svn/projects/eal/ptII/branches/vertx-3-0-0 ptIIv3

Which version of Vert.x 3.0?

In $PTII/lib, we are using the following Vert.x 2.x jars that have corresponding jars in 3.x:

• hazelcast-*.jar
• jackson-annotations-*.jar
• jackson-core-*.jar
• jackson-databind-*.jar
• vertx-core-*.jar
• vertx-hazelcast-*.jar

These Vert.x 2.x jars do not have direct replacements in 3.x:

• java-xmlhttprequest-*.jar
• netty-all-*.jar

https://github.com/vert-x3/vertx-stack/blob/master/README.md states that the Vert.x min distribution has:

• Vert.x Core
• Groovy, JS and Ruby languages
• Hazelcast clustering
• Service proxy

Let's start with that and see what else is necessary.

Adding the Vert.x 3.0 jars to the ptII branch

These steps have already been done for you and is in the ptII vert-3-0-0 branch

Delete the Vert.x 2.x jars from the branch :

Copy jar files from the Vert.x 3.0 directory:

FIXME: We probably don't need vertx-lang-groovy-3.0.0.jar or vertx-lang-ruby-3.0.0.jar.

FIXME: Update license files for these jar files.

Add the jar files to the branch:

Edit configure.in and change:

Configure the system. We use --enable-verbose to get more information:

You should see something like:

 checking for the Vertx application platform interface. ... ${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/hazelcast-3.5.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/jackson-annotations-2.5.0.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/jackson-core-2.5.3.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/jackson-databind-2.5.3.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/netty-buffer-4.0.28.Final.jar${CLASSPATHSEPARATOR}${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/netty-codec-http-4.0.28.Final.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/netty-common-4.0.28.Final.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/netty-handler-4.0.28.Final.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/vertx-core-3.0.0.jar${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/vertx-hazelcast-3.0.0.jar${CLASSPATHSEPARATOR}${CLASSPATHSEPARATOR}/Users/cxh/src/ptIIv3/lib/vertx-service-proxy-3.0.0.jar

Also, the new jars should be in .classpath and build.xml

Build

Run ant which we expect to fail.

Ptolemy II files that use Vert.x

Place these file names in a file so that we can run scripts on the files:

Vert.x 2.x classes used in Ptolemy II

Package Change

Checklist for Migrating from Vert.x 2.1.x to Vert.x 3 - Part One says:

"Change all the imports for Vertx. from org.vertx to io.vertx."

I used a script for this.

Run ant

Errors are:

Convert io.vertx.java to io.vertx

io.vertx.java.core.Vertx is now io.vertx.core.Vertx as defined in lib/vertx-core-3.0.0.jar, so we change the io.vertx.java to io.vertx using a script.

Run ant

Convert io.vertx.core.VertxFactory to io.vertx.core.spi.VertxFactory

Make the update

Run ant

Replace io.vertx.core.datagram.InternetProtocolFamily with io.vertx.core.datagram.impl.InternetProtocolFamily;

package io.vertx.core.sockjs does not exist

ant says:

• SockJS in Vertx3: See the Vert.x web docs
• io.vertx.ext.web.handler.sockjs docs - looks like we would use io.vertx.ext.web.handler.sockjs.SockJSHandler

SockJSHandler is found in The Vert.x full download in vertx-web-3.0.0.jar, which was added to $PTII/lib in the vertx-3-0 branch. That jar file was also added to $PTII/configure.in, autoconf was run and then $PTII/configure.

Verticle is missing

Checklist for Migrating from Vert.x 2.1.x to Vert.x 3 - Part One says:

"Verticle is now an interface and not a class to extend, so using Groovy as an example you now extend GroovyVerticle. In Java extend AbstractVerticle instead."

So, in actor/lib/vertx/EventBusTestServer.java, import io.vertx.platform.AbstractVerticle; becomes import io.vertx.core.AbstractVerticle; and we extend AbstractVerticle

"Cannot find annotation method 'concrete()' in type 'VertxGen'"

• vertx-3.0.0 and milestone 6 warning when compile my server verticle

Solution: Downloaded vertx-codegen-3.0.0.jar:

  wget http://central.maven.org/maven2/io/vertx/vertx-codegen/3.0.0/vertx-codegen-3.0.0.jar

added it to lib and added it to configure.in, ran autoconf

"Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider org.netbeans.modules.openide.util.NbBundleProcessor not found"

While running make:

Solution: Intially, I thought the solution was to edit the makefile and add $(PTHOMER_JARS), which is set in mk/ptII.mk:

However, it turns out that the problem was that $PTII/META-INF/services/javax.annotation.processing.Processor existed.

The javac docs say:

"Unless annotation processing is disabled with the -proc:none option, the compiler searches for any annotation processors that are available. The search path can be specified with the -processorpath option; if it is not given, the user class path is used. Processors are located by means of service provider-configuration files named META-INF/services/javax.annotation.processing.Processor on the search path. Such files should contain the names of any annotation processors to be used, listed one per line. Alternatively, processors can be specified explicitly, using the -processor option."

Cannot find symbol VertxHelperBase

Solution: "VertxFactory.newVertx()" -> "Vertx.vertx()"

Current Errors

10/29/2015:

No suitable method found for send(String,String,Handler<Message>)

Docs are at io.vertx.core.eventbus.EventBus

The error is:

The fix is:

cannot find registerHandler

• http://vertx.io/docs/vertx-core/java/
• http://vertx.io/docs/apidocs/io/vertx/rxjava/core/eventbus/EventBus.html

The fix:

• Back to Vert.x