Monday, November 14, 2011

Talk for EclipseCon 2012

Since I am back to the world of developing tools for Eclipse developers, I thought it would be interesting to propose a talk for the North America edition of EclipseCon. As for the subject of the talk, I chose to share some of the knowledge I gathered between 2008 and 2011 while using linked data and RDF on a few projects at IBM.

The talk has a catchy name: I cheated on EMF with RDF. And I may do it again!. If you are interested on hearing this confession, vote for it. Moreover, if you are really, really interested, please leave a comment with your expectations and even the topics you'd like to hear about. I won't be able to put 2+ years of hands-on experience with RDF in a 35 mins talk and would hate to leave behind something that a lot of people are interested just because I don't know they are interested ;-)

That said, the greatest thing about EclipseCon is that the technology sharing experience is not limited to the presentation rooms. If I am there, I will be more than happy to discuss this and any other topic, especially while having some drinks at the bar ;-)

Saturday, May 14, 2011

There is a world of statements out there

People that work with me have certainly heard "wow, I was smart" more than once. Typically I use this sentence when I am puzzled trying to understand some beautiful code I've written or designed a while ago. Now I am afraid that one day I will be saying it a lot if I ever need to look back at the technologies that I was focused on during my last years at IBM. Since 2009, I've been head down understanding the main pieces behind linked data:

I have to confess: these technologies are fantastic! Out of them, the one that I like the most is certainly RDF, probably because it's in the realm of models. Honestly though, I had a hard time understanding it at the beginning for I was seeing it with my old, schema-driven eyes. You know, for more than 15 years I trained myself to see the world as instances of rigid schemas, mainly formed by classes, attributes, and references. Alas, this way of thinking doesn't go well with RDF. If one is like I was, I'd suggest repeating "RDF is not just a new way to express a schema" at least every five minutes while trying to make some sense out of it.

My plan is to use the free time that I happen to have now to write down my thoughts about these technologies. Hopefully I will be able to register here what I refer to as my "linked data intuition": the small pieces of knowledge that I've assembled from various sources and that I now use to tackle any new RDF or REST challenge. For a second I've considered writing this on a personal document and store it away for future reference. How dumb is this? Putting the words here may benefit others and even allow people to correct me. Albeit pretentious, I like to believe that I know the stuff I am about to write ;-) But I wouldn't be surprised to be proven wrong. And that would be actually great: that's when one has an opportunity to reset and reflect about a topic again.

Looking forward to spending more time here in the next few days.

A new life ahead

It has been a while since I've written something here. Either by laziness or my notorious capability of ignoring the social media aspects of today's world, I know I have completely abandoned this blog.

What made me take the time to post now, then? To share that after 10+ years I am no longer an IBMer. It was a very hard decision and at the end the I've chosen what made sense for me and my family. At this moment I fell great, anxiously waiting for the start of my life. Honestly though, by the beginning of this week I was almost miserable: not for regretting the path that I was taking but to be taking it. It is hard to explain. IBM has been a second home, one that was opened to me just two weeks after I came to Canada. Oh well... I promised myself I wouldn't get emotional ;-)

So what lies ahead? In a few weeks I will join Oracle, working with the team that is creating the best Eclipse tooling for developers that have adopted Oracle technologies. Man, I am exited! First I will be back to daily interactions with my favourite framework and its related technologies. Second, I will have to learn an entire new world of enterprise-focused technologies! Lots of fun and hard work for the next months.

Sunday, March 29, 2009

What a great EclipseCon!

As anyone on this planet knows, last week was EclipseCon time. As always, it was a great experience. Seriously... How many conferences can one discuss, during lunch, the double-checked locking pattern or how EMF could support facets? (thanks Eike and Kenn)

All talks I've attended were awesome. It's reinvigorating to see all the energy and technology happening behind Eclipse: from known technologies to hot topics like E4 and XText.

And it gets better! The people at the conference are simply fantastic. Just to name a few, it was great to chat with Nick, Chris, and Boris and to finally meet in person Tom, Kevin, Peter, and Paul Webster. There are many others that, although not listed here, have contributed to make last week a memory that will not fade away from my mind.

A bit more personal, I like to think that the EMF tutorial was well received. We chose to go deeper into several subjects instead of mechanically read all the slides. Unfortunately, because of that, we didn't cover all the material. The offer to be available to answer individual questions after the conference is still valid ;-)

I got some positive reviews for the modeled UI in e4 talk, which definitely doesn't seem to agree with the official numbers. I wonder if we were too "slide driven" while the folks attending were expecting to see more action. Or perhaps my delusional-self is correct and people did mistake the '+1' for the '-1' bucket. Oh well... I am sure we'll do better the next time.

Finally, a special thanks to Steve: I was peacefully seated at the closing event when he handed me a winning deck for Thursday's poker game. My son loved the RC boat and will enjoy playing with it on summer time.

Another finally... The EMF book was the first one to be sold out at EclipseCon! I had the pleasure to autograph a few copies. On the subject, EMF and modeling in general are everywhere. It is good to see something I helped built making others more productive ;-)

Saturday, September 27, 2008

I am lazy!

It is annoying to feel compelled to start every post with "Wow... It has been a long time since I've posted something here". Of course one answer is "So don't". I'd rather think that some people would prefer to say "So post more". I am known for having an occasional delusional moment here and there, though ;-)

I believe one of the reasons that I don't update this blog as often as I wanted to, besides being insanely busy, is that, bottom line, I am a lazy person. Fortunately, a characteristic that would put me out of any work back 50 years ago, is actually something that should be rewarded on the software development world. Let me illustrate this with an example.

When I am heads down, working 15+ hours per day to develop an entire product or a complicated feature, I get extremely paranoid (way more than normal) about introducing regressions by entering a, or better, any new line of code. And testing everything all the time is too tiring (I started by saying that I am lazy, remember? ;-). So I usually choose to automate as many tests I can. Sure I have to invest some time putting together an automation strategy (usually based on JUnit). But after that, I just need to click a button and watch the JUnit progress bar go while I exercise the divine right of not doing anything for a few minutes - OK, I am lying: usually I am working on another portion of the code while the tests are running.

On my last endeavor, for example, testing the code consisted on executing 11 Java examples that invoke an API written to identify security issues on web applications by looking at their code and by interacting with them as a hacker would do. Each one of these Java applications run for about 2 to 10 minutes and produces a long log that has to be verified. After doing this by hand 3 times, my laziness kicked in and forced me to find an easier way to test my code. After one or two hours of JUnit fun, I had a class that, for a test method like the one below, executes the XYZ.class on a separate VM, collects the generated log, and compares it with a baseline I know is correct.

public void codeCoverageExample() throws Exception {

The comparison part was a bit tricky to implement because the logs have things like timestamps and temporary file paths that change from execution to execution. With some creativity and several regular expressions, I managed to circumvent all the issues and, like a famous black-turtle-neck-guy says, "BOOM" : the annoying tests were out of my way ;-)

I will write at least one more post pointing out cases in which being lazy was extremely valuable. I am already thinking about EMF related examples...

Actually, on a minor digression, is my passion for EMF the ultimate proof that I am lazy? After all, it does generate a bunch of the code that I would need to code by hand ;-)

Wednesday, June 18, 2008

"Ch-ch-ch-ch-Changes" and "I am still around!"

I couldn't really decide what would be the best title for this post. So I chose to use both ideas that I had in mind. Fortunately, as this title, there are several opportunities in which we can actually choose all the options that are presented to us. For example, three years ago, I've chosen to be both Brazilian and Canadian. More recently, I've also chosen to change a bit my professional life and do some product work while keeping my duties as an EMF committer.

After four years dedicating myself exclusively to EMF, I am now working on the Rational AppScan Developer Edition team (our beta is available here). A minor digression, the security-related technology behind this product is quite amazing. I really don't want to sound like a salesman, though. I know that it wouldn't go really well given my "amazing" commercial skills ;-)

The good news is that both Ed and my new manager (Jeff Turnham) have been extremely supportive in my decision of work both internally and on open source. Hopefully most of you agree with their attitude. I certainly do ;-)

To me it will be a bliss to employ the technology that I help build. Although the EMF team has always eaten its own dog food caviar ;-), it is quite different to face the problems that consumers of our code have to deal with. On the other hand, I am really expecting that the product experience will make me a better EMF developer. EMF has been part of my life for quite a while and it certainly deserves the best I can be.

Thursday, March 20, 2008

Platform scheme URI

Wow... It has been more than six months since the last time I took a few minutes to write something here. Things have been a bit crazy lately. A lot has kept me occupied, like, for example, writing the 2nd version of the EMF book (which is "already" available as a rough cut), working on a few bugzillas, and supporting the EMF community. On a more personal note, in October we moved to our new house right when our son was entering the "terrible twos" days. Actually, since then, my wife and I have been working as maniacs to finish the basement and prepare the kids' rooms for the arrival of the new member of the Paternostro family, who is supposed to be here by the end of April.

But I am sure you are not reading this to hear about what I've been doing ;-) So, let's move on to the subject of this post. Quite frequently people ask me how to "locate" files in Eclipse. In 80% of the cases, the conversation is about things like IFile and IWorkspace. Sometimes it digresses to files available inside bundles and, rarely, it involves the "state location" of a bundle (see the Plugin.getStateLocation() javadoc for more details). Obviously you can use IResources or to work with files in these places. There is another way, though: platform URI. Although this scheme has been around since the beginning of time, I decided to ramble about it here because I've never seem its uses described in one single place.

There are a few ways to work with the "platform" scheme:

platform:/resourceIt is used to identify a resource located in the workspace. The next path segment after "resource" should be the name of a project, which can be followed by the folder and/or file we want to locate.
platform:/pluginIt is used to locate a resource available in a plug-in (I know, I know, bundle). One really cool thing about this one is that it doesn't really matter if this resource is available in a directory or in a jar file. It also doesn't matter if the bundle is installed in a link folder or in the default directory.

The path segment after "plugin" should be the identifier of the bundle, which can be followed by the path of the resource in the bundle.
platform:/fragmentThis one is quite similar to "platform:/plugin", being to used to locate fragment resources instead of bundle resources. As you are probably guessing, the segment after "fragment" should be the fragment's identifier.
platform:/metaWe can use this to access a bundle's stage location. The path segment after "meta" should be the bundle's identifier, followed by the path of the resource we want to refer to.
platform:/configThe "config" segment causes the platform URI to refer to the configuration area of the running Eclipse (usually the eclipse/configuration directory). This can be useful to read the config.ini file, for example.
platform:/baseThis always refers to the directory of the Eclipse being executed.

It is interesting to note that, for example, platform:/base/plugins/org.eclipse.emf/plugin.xml and platform:/plugin/org.eclipse.emf/plugin.xml don't necessarily refer to the same resource. The former is a "pointer" to a plugin.xml file located in a directory plugins/org.eclipse.emf under the directory that Eclipse is installed. The latter points to the plugin.xml of the "org.eclipse.emf.ecore" bundle regardless of where it is installed and whether it is jarred or not.

For the URI-savvy people, you should see "resource", "plugin", "fragment", "meta", "config", and "base" as authorities. Perhaps they could become authorities in e4 (yey! Now this is an e4 related post ;-)

Since we all like actual code...
IProject project = 
if (!project.exists())
project.create(new NullProgressMonitor());

System.out.println("\n==== platform:/resource ====");
URI uri = URI.createPlatformResourceURI("myproject", true);

uri = uri.appendSegments(new String[]{"folder", "file.txt"});

System.out.println("\n==== platform:/plugin ====");
// Just for fun, choose a bundle that is not in the default location
URI uri = URI.createPlatformPluginURI("org.eclipse.emf.ecore", true);

uri = uri.appendSegments(new String[]{"model", "Ecore.ecore"});

// Choose a bundle that is in the default location (<eclipse-dir>/plugins)
uri = URI.createPlatformPluginURI("org.eclipse.core.resources", true);

uri = uri.appendSegments(new String[]{"META-INF", "MANIFEST.MF"});

System.out.println("\n==== platform:/fragment ====");
URI uri = URI.createURI("platform:/fragment/org.eclipse.swt");

uri = uri.appendSegments(new String[]{"META-INF", "MANIFEST.MF"});

System.out.println("\n==== platform:/config ====");
URI uri = URI.createURI("platform:/config/");

System.out.println("\n==== platform:/base ====");
URI uri = URI.createURI("platform:/base/");
The call to CommonPlugin.resolve(URI) returns a URI that uses a protocol which is native to the Java class library (file, jar, http, etc).

I will leave it to you to run this code and see the results :-P Don't forget that it must be executed in an Eclipse shell. Probably the simplest way to do so is to paste these lines into a JUnit test located in a bundle and execute it as a "JUnit Plug-in Test".

So what can we do with platform URIs? For one, read the contents of the resources pointed by them. We may also be able to write to such resources or even delete or create them. A tip for EMF 2.4 users: URIConverter.INSTANCE allows easy access to methods that are extremely handy when dealing with URIs (createOutputStream(URI), createInputStream(URI), delete(URI), and exists(URI)).

Personally I consider URIs a good fit for APIs that would normally use "plain" paths. Take as an example the icon attribute of the extension point below. Because its value is handled as a URI, we are allowed to refer to an image located in a different bundle.
<extension point="org.eclipse.ui.editorActions">
<editorContribution ...>
BTW, if I were to implement the code to process such an extension point, I would probably do something like this:
IConfigurationElement configurationElement = ...
URI iconURI = URI.createURI(configurationElement.getAttribute("icon"));
if (iconURI.isRelative())
URI pluginURI =
configurationElement.getContributor().getName() + "/", true);
iconURI = iconURI.resolve(pluginURI);

ImageDescriptor imageDescriptor =
ImageDescriptor.createFromURL(new URL(iconURI.toString()));
catch (Exception e)
This code assumes that when the value of the icon attribute is a relative URI (like icon/me.gif for example), the developer is indicating that the image is contained in the bundle that uses the extension point.

For obvious reasons, I wrote these examples using EMF APIs, including our URI class. It shouldn't be terribly difficult to rewrite the code in this post to use basic Eclipse and Java code (like,