All about Java
Boris Bokowski (IBM)
Abstract:
As the software landscape changes, the Eclipse platform is also evolving in order to remain relevant and vibrant. Eclipse 4.0, the next generation of the Eclipse platform, arrived this summer….
Jonathan Lindo (Replay Solutions)
Abstract:
See a Live Demonstration of an innovative new Eclipse-based automation feature:
Users are resolving defects 60% faster
Reproduce bugs in minutes in Eclipse
No database or appl…
Mik Kersten (Tasktop)
Abstract:
This webinar will demonstrate the most noteworthy features and enhancements for Mylyn in the Helios release, such as enhanced support for Agile development, code reviews, social technologies …
Boris Bokowski (IBM)
Abstract:
As the software landscape changes, the Eclipse platform is also evolving in order to remain relevant and vibrant. Eclipse 4.0, the next generation of the Eclipse platform, arrived this summer….
Mik Kersten (Tasktop)
Abstract:
This webinar will demonstrate the most noteworthy features and enhancements for Mylyn in the Helios release, such as enhanced support for Agile development, code reviews, social technologies …
Reginald Stadlbauer
Abstract:
This video shows how to automate functional GUI tests for Eclipse based user interfaces. froglogic’s Reginald Stadlbauer shows how to set up an fully automated test using the Squish GUI testing…
Eclipse Committers
Abstract:
The Eclipse Foundation is presenting Helios In Action – a virtual conference where you can interact with project leads involved in the release and see demos of the new features. The annual simul…
Chariot TechCast with Boris Bokowski (IBM)
Abstract:
Today we speak with Boris Bokowski, a committer on the Eclipse Platform UI project, and a Senior Software Engineer at IBM. His participation in Ecilpse dates back to Ecl…
Dave Meurer (Skyway Software/Genuitec)
Abstract:
One of the core capabilities in MyEclipse for Spring, scaffolding generates ready-to-run applications from existing artifacts such as database schemas, Java Beans and JPA ent…
Adobe Ajax Android Anwendung Apache API C++ Community Developer Eclipse Eclipse Foundation Embedded English Enterprise Entwickler Equinox Galileo Google Handy IBM IDE Individual Java Member Microsoft Mobile Modeling NetBeans News Open …
Gestern.hat die Systemprüfung einen Virus gefunden ,, Java/Dldr.agent.l,, und in Quarantäne geschoben. Leider habe ich den Bericht aus Versehen gelöscht. :thumbdown: Frage: 1-Wenn ich Malwarebyts und Hijack This Installiere ,kann Avira …
Programmierung interaktiver Homepages für das World Wide Web Kurzbeschreibung Die Java-Fibel ist eine leicht verständliche Einführung in die Konzepte und Syntax der Sprache, die mittels … Java, Dell, Computerbücher.
It looks like I am late to find out this cool feature, but I’ll share it anyway. The reason for that is I never expected such a feature could exist. So there might be others like me who “underestimates” 
how the open source world addresses any problem that “can” exist and before you know, the solution is there.
As some of you know, I am not a committer on any open source project [yet].
However, I do contribute to quite a lot of them. One of the problems when you do not have write access to the original SCM repository, your patches and changes start getting outdated / conflicted / complicated and it becomes hard to keep up with the changes to the original SCM,
git Seems to tackle the issue. I have come across with Taki’s blog on CVS to GIT and back that explains how to address the problem in detail. Although the blog focuses on “CVS” it should be pretty easy apply the same for SVN and GIT (over GIT).
With these introductions you can mirror a cvs / svn repository and provide your own sub committer group to create patches, pass them to the project, get the updates back.
Even this can be very handy to fork a project.
Jakob Freund meldet auf dem BPMGuide-Blog die Veröffentlichung eines Poster zur neuen Business Process Management Notation in Version 2.0 (BPMN 2.0) das gemeinsam mit der BPM-Offensive erstellt wurde. Das Poster kann kostenlos und in mehreren …
Roman Strobl von JetBrains reagiert auf die Kommentare der Community und beantwortet im Rahmen des interaktiven IDE-Vergleichs zwischen Eclipse, NetBeans und IntelliJ IDEA Fragen zur IntelliJ-IDEA-Entwicklungsumgebung. …
As I mentioned a while back, Eclipse Helios M5 was made available for Download. There are number of New and Noteworthy features, but one really big feature was omitted from the N&N. The Eclipse provisioning platform, p2, finally has API! Really, go take a look at the code… all those internal.provisional packages are now gone! This was actually a huge milestone for the p2 team, and Pascal did a great job steering us towards the API.
What does this mean to you? Well, if you are building anything on top of p2 you should grab M5 and see how the new API feels. We are going to be pushing hard to finalize the API for M6, so if there is anything missing, speak up now.
John Arthorne even started a Migration guide: http://wiki.eclipse.org/Equinox/p2/Helios_Migration_Guide
We are in the midst of judging the product categories for the Eclipse Community Awards. It turns out we received only two nominations for the EclipseRT Application category. The judges have decided they would like to see more nominees, so we have re-opened nominations in this category until February 17 at 5pmET.
This is a new category for the Eclipse Awards so some clarification might be in order. If you are building an internal application, commercial product or open source project that uses any of the EclipseRT technology you can send in a nomination. For example, if you have built a killer web application using RAP or a great server application using Equinox, Jetty and EclipseLink or a SOA application using Swordfish or your using SMILA or ….
I know there are a lot of applications and products using EclipseRT technology. The nomination process is pretty easy and this is your opportunity to garner the fame and prestige of an Eclipse Community Award winner. Feel free to contact me if you have any questions.
In a previous assignment we had a project more like an intranet application where you manage document, make applications (which flow through a complex 400+ step BPM), integration with a SOA engine, task, inbox, etc… It was a large government project with 500 daily users.
We chose the RAP [RCP], Databinding, EMF, Teneo, hibernate, JTrecache, Equinox[OSGI] project stack. We also have written a simple editor to manipulate EMF model.
I must admit I enjoyed defining my models in ecore. With the help of teneo my DAO consisted only ~100 lines. Since the application security (this is including down to input element levels with hidden/read/write granularity) was so tight we also kept the security definitions in the ecore model.
We kept the database schema definitions along with the ecore classes, which helped BI developers and DB admins to get updates momentarily (In the early phase of the project there were weekly deployments).
I think one of the problems with java world is it has the J2EE definition. 90% times you make a project, you choose the Application server, JPA, Web model etc for the project. But people believe “If it is a commercial / corporate product it’s gotta be J2EE compliant”, which is a big bold and IMHO unnecessary binding. Most of the time, you do not WORE! Not to mention there is the saying “Write Once Debug Everywhere”.
Lately application server vendors started adopting OSGI and we’ll see where this will go. But to be honest (this might require a correction) without using equinox, you cannot use much of the eclipse technologies where the base plugins require definitions via extension points. e4 with the new dependency injection stuff may make this comment deprecated. But with the more and on-the-target adoption of OSGI, we’ll see more eclipse technologies used outside RCP and IDE domain.
On the project I mentioned, people were like ‘Are you crazy you are taking way more risks, how are you gonna get support’, well, we used the SOA engine and DB of one of the largest provider provider, we have a support ticket still open for 6 months, where I had over 20 interactions with RAP, Teneo, EMF team all resolved within hours to days. Imagine if we were using the application server from that vendor.
In the end, the project was a big success and a breakthrough not in the country but at the global level. So I think developing enterprise application doesn’t mean you gotta go JavaEE. Putting together your own OSGI stack is much better. Plus while developing, you will get the joy of restarting the application in a matter of seconds rather then in minutes in comparison to application servers.
I landed on a few articles about “UML in Colors” lately, I enjoyed reading those as modeling is used here as a design tool and support for efficient communication. It also made me think : that’s a nice use case for our extensible modeling environment !
Also, ich weiss, dass Java Plattformunabhänig ist, aber inwifern unterscheidet sich Javasprache von c++? Ich kann nämlich schon ansatzweise ein wenig.
OK, I use Eclipse for getting some work done. Eclipse is software so we know it contains bugs. Given that Eclipse is open source software, we all can only expect it to run smoothly if we diligently report back all errors we encounter (and provide steps on how to reproduce etc.). I know all that and I really want to be a good bug reporter because I really want a good experience using Eclipse because I really want to get the work done (and I may even want to sustain the impression that I’ve got everything under control and thus working with Eclipse is a delight).
The other day, I was a very bad bug reporter, and only today I find some time to reason about what happened. This was my task: In preparing the initial contribution for the Object Teams Project I had to rename a bunch of things from org.objectteams to org.eclipse.objectteams. Simply, huh? Back in the days of emacs+bash I might have chosen to just use one big
find . -exec /bin/sed -i -e "s/org.objectteams/org.eclipse.objectteams/g" {} \;
and voila, if fortuna was with me, I might have been done at the return of that single command. But things were actually just a little bit more challenging, like, a few occurrences would have to remain unchanged plus while touching about every single file in our software I was going to also do some clean-up: rename some packages to foo.internal.bar, fixing some copyright headers, etc. Also I preferred to change one plug-in at a time which would mean that all references to plug-ins not yet processed should stay unchanged, too. Plus a few more little deviations from the grand search-and-replace-globally.
OK, since I like to see myself an Eclipse-wizard this was a nice challenge for its refactoring support. Plug-in by plug-in I renamed, I renamed packages with / or without subpackages, and after each step I wanted to see that compiler and PDE agree with all changes and signal that everything is still (or again) consistent, ready to be built, actually. Perhaps things started the get wrong when I estimated the effort as one or two hours. So, after a day or so, I wasn’t perfectly relaxed any more. My fault, should’ve known better about that estimate. BTW, one of the reasons it took so long was simply the size of my workspace in comparison to the power of my computer / hard-disk: every time I performed a rename with updates in non-Java files, I was nervously looking at the screen: “should I sit and wait for the preview page, or should I go to the kitchen, get a chocolate, coffee, just something?“. I did some emailing in parallel, but let’s just keep this: due to those response times I wasn’t perfectly relaxed any more.
What I was going to tell here is a story of bug reporting, because as a safe bet doing a real-life stress test to an Eclipse component should give you a good chance to discover and report a few bugs that have not yet been reported by others. And indeed, I was successful in discovering some bugs, in various components actually.
I think one of the first things that occurred was that the svn synchronize view would sometimes fail to open the compare editor, more precisely, I had to explicitly close the compare editor before comparing the next file. At first this really **** me off, because the error dialog was popping up in some kind of infinite loop. Fun!#$ Once I’d figure out how to work around this problem it soon became a habit to just close the compare editor before clicking the next. Next, the svn plugin made a refactoring fail, because it was trying to create a directory which the previous refactoring had already created. The most creative bug having to do with subversive was a chain-reaction of first failing to undo a refactoring and than during reporting this error blocking the UI of Eclipse so I could only kill the Eclipse process, insert a new coin and start a new game.
I don’t intend to blame a particular component. For clean-up of license headers I have a little home-grown plugin that I just wanted to quickly install into the running Eclipse instance, so I went for the cool new feature to export/install into the host. Oops, my plugin depends on another plugin that only exists in the workspace but not in the host, install failed for good reasons. I removed the dependency and tried again. Installation still failed for the same reason: the ghost of this removed dependency prevented installation into the host Eclipse. Oh, I should have incremented the version or let a version qualifier do this automatically, of course. Tried again, still failed. Tried something so slightly different I cannot recall, from there on it worked. Can I reproduce the two or three different levels of failure? I didn’t even take the time to think of it. Well I would’ve been disappointed without a bug from p2 in this list 
.
PDE did its share by reporting overlapping text edits in plugin.xml and therefore disabling its refactoring participant. What the **** caused those overlapping text edits, and how do I re-enable the refactoring participant to give it one more chance to behave well?
The list could go on if only I could remember. Instead I was happy to finish this 1.5 hours task after 2.7 days, ready to submit our initial code contribution, wow!
Looking back, I / we missed a great opportunity: we could have identified plenty of bugs in various components of Eclipse. With only a few more days of debugging I might have been able to present reproducing steps for all those bugs. And, if triaged and fixed by the corresponding devs, this might have contributed to M6 containing fewer of those bugs that just only occur in real world, never during testing. I failed, I managed only to submit two bug reports, with very little information on how to reproduce.
Susan McCourt responded to an earlier bug report of mine in a very descriptive comment:
That is one of those things I’ve been meaning to fix forever, never wrote a
bug, and so keep forgetting to fix. And it seems like if I’m actually
[doing what triggers the bug], it’s because something is wrong, and so I again postpone
writing a bug.
Sure, when we hit a bug (or a bug hits us) we are always in some context of doing something challenging. Something that requires our mind to stay in focus. Something we want to get done.
Well, work isn’t perfectly linear, so we know how to react to interrupts. Bugs are such interrupts. Sometimes I like the challenge of isolating a bug etc. Sometimes I’m sufficiently relaxed when the bug occurs so I actually take the challenge. Sometimes the bug is sufficiently good-natured so making a small note and going back to the bug after the actual work is done is a perfect strategy. Some bugs, however, smell like depending on so many factors from your current context that reproduction an hour later seems extremely unlikely.
I think I have a solution to all this: given we don’t want to be distracted from our actual work, given also that some bugs need immediate care or they will escape our attempts to identify. Given some of the worst moments are when we start to isolate a bug and during that task a second bug stops us from working on the first bug etc. The only way to relentlessly follow all those tasks is to enable branching universes in your working environment. The frequent use of the work “task” may give a hint that I should finally start using Mylyn (I have no excuse for not doing so), but I would need a Mylyn that is able to capture full contexts: the complete state of my machine plus the full state of my brain. As a start I’m dreaming of always working in a virtual machine, and whenever something strange happens, I quickly (!!) create a snapshot of the virtual machine. Then I could first isolate (and fix 
) the bug that just occurred, and then go back to the exact point where I interrupted my work and act as if nothing had happened. Branching universes with the ability of back porting fixes between branches is what I need. Of course the clock needs to be reset when returning from a bug reporting / fixing branch.
Yeah, that’s why I can’t quite live up to my dreams of good participation in open source development: I haven’t figured out how to enable branching universes for my character. If anybody has a hint on how to do this or any other strategy to not get overwhelmed between work and bug reporting, I’d really appreciate.
And if I don’t smile while writing a bug report, please excuse, I might just be terribly stressed because your bug interrupted my work on isolating another bug that stopped me from doing …
”Always look at the bright side of life…”
The Eclipse Foundation and the OSGi Alliance are holding a Cloud workshop during the OSGi DevCon/EclipseCon developer conference in Santa Clara, Thursday March 25.
They key question we want to answer in this workshop: what role can OSGi play in the cloud? Offerings like the ones from Amazon (aws.amazon.com) are agnostic of any application model and OSGi can play in their EC2 offering like anybody else because it is based on generic x86 machines. However, a model like the Google App Engine so severely knee-capped Java that it is doubt full that OSGi can run on it. Many cloud computing providers have free plans to get you started, or at least make the cost trivial. However, the costly part is your own investment in the software you develop for the cloud. On the desktop and on the server we’ve had a lot of advantage of standards that abstracted us from the vendors. This portability allows us to move our code to different app servers (well mostly). Though most of the lessons we learned in the past still apply to the cloud, the current vendors of cloud computing have very specific offerings that easily create portability problems. How to access the storage? How to discover and handle multiple instances of the application in the cloud? How to handle storage? How to share domain specific services? Standardizing interfaces for these aspects of cloud computing could provide a lot of portability. And portability is not only in the interest of the clients, also vendors gain by having a much larger market.
Perusing the different offerings for cloud computing I can clearly see that the OSGi bundle model would work very well in this area. Applications can easily be managed remotely because remote management is inside OSGi’s genes. This always has made OSGi easy to use in clusters and much of those benefits apply equally to cloud computing. However, the advantages of the OSGi service model seems to be even more clear. A cloud computing environment is by definition a dynamic environment. Adding instances, removing instances, and instances that fail will likely influence the other instances. This means that the application will need to handle the dynamicity of the services that these computing instances provide. There will be also be dependencies that must be managed. OSGi services shine in these areas, making it relatively simple to correctly model these dynamic dependencies.
So overall the combination of cloud computing and OSGi is clearly an interesting one. With the workshop we want to bring together cloud people and OSGi people and see where there are areas where OSGi standards could help. This first workshop is by invitation only because for this first time we want to learn; we need people with experience in the area of cloud computing and that see OSGi as a potential standards player in this area; creating a discussion between cloud experts and OSGi experts. So if you’re heavily into cloud computing and you want to attend, send me or Ian Skerret from the Eclipse Foundation a mail. Amazon? Google? Microsoft? You?
Recently, we received some bug about EEF for the library sample of EMF. After some fixes, EEF works for this metamodel. So I took 5 minutes (yes 5 minutes ! ) to make a demo about this sample.
The important thing behind this demo is the entire EEF process. You have all the steps needed to use EEF in the EMF generated treeviewer. Enjoy
