Mavenize SOA Templates

Ein primärer Fokus von Version 12c der Oracle SOA Suite war die Steigerung der Entwicklungsproduktivität. Zwei prominente Neuerungen sind die Einführung von diversen SOA Templates sowie die Unterstützung von Maven als Build-Tool. Die nun existierenden SOA Templates können in vielen Ebenen der SOA Suite Entwicklung genutzt werden. Sie unterstützen die Entwicklung sinnvoll, haben teilweise jedoch Limitierungen hinsichtlich ihrer Flexibilität.t An dieser Stelle wird die Möglichkeit Maven als alternatives Build-Tool in der SCA Entwicklung zu nutzen interessant.

Der Artikel Mavenize SOA Templates erschien auf esentri AG - Oracle Gold Partner.

Activate “Open folder in Terminal” for Finder in Mac OS X

From Linux distributions I was used to have a context menu entry within file browsers which opened a terminal at the current folder. In standard configuration Mac OS X’s Finder does not provide this functionality. However, the service exists and it just has to be activated.

In order to activate this service open the following screen in System Preferences:

System Preferences > Keyboard > Shortcuts > Services

Two options can be activated:

  • New Terminal at Folder
  • New Terminal Tab at Folder

Afterwards the service is available within folder context menus.

"Open terminal at folder" option
“Open terminal at folder” option

Eclipse not starting (no error message)

Recently, I had a strange behaviour with my Eclipse installation. I think the error occurred after I had to kill Eclipse due to some issue during a build. Afterwards Eclipse was unable to restore the workspace.

If you run into the same issue try these three things:

  1. Try to delete the following folder:
    <Workspace DIR>/.metadata/.plugins/org.eclipse.core.resources/.snap
  2. If error still persists and using Eclipse 4 delete following file aswell:
    <Workspace DIR>/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
  3. Create a new workspace and import projects. If you did set the broken workspace as default open the following file:
    <Eclipse Home>\configuration\.settings\org.eclipse.ui.ide.prefs

    In this file search for preference SHOW_WORKSPACE_SELECTION_DIALOG and set it to true.

Forwarding emails using filters in Google Mail

Automatic email forwarding for certain emails can be quite handy. Here is a quick guide how you create forwarding filters in Google Mail.

To start off with we need to add a new forwarding email address and verify that we are allowed to forward emails to this address. In order to do this open up Google Mail settings and click the Forwarding and POP/IMAP tab.

Open forwarding settings
Open forwarding settings

Within the upcoming tab click on the Add forwarding address button and enter an email address in the new dialogue.

Enter forwarding email
Enter forwarding email

As soon as the new forwarding email address is added the owner should get an email containing a verification code. With this code one can verify that one is allowed to forward emails to this address. The code can be entered within the Forwarding and POP/IMAP tab.

Enter verification code
Enter verification code

After verification emails can be forwarded to this address. Google Mail provides two options for forwarding emails. First option is to forward all emails to a certain address. The second option is to define filters which identify certain emails and forward these to a specific email address. The later option is of interest for us.

In order to create a new filter navigate to the settings Filters tab. Here one can see existing and create new filters.

Create new filter
Create new filter

Creating a filter is very simple. First of all one has to define the filter criteria, which can also be done by simply typing search terms into Google Mail’s email search field.

Define filter criteria
Define filter criteria

Secondly, one has to define which actions should be applied to emails matching the defined filter criteria. In order to forward emails one has to check the Forward it to action and select the desired destination email address.

Define actions
Define actions

After creating the filter all actions, including Forward it to, should be applied to emails matching the filter criteria.

 

git svn – Subversion repository moved, what should I do?

As I prefer Git as version control system I often end up working with it as client for Subversion (SVN) repositories. Recently, I had to interact with a SVN repository which was moved to another location after my initial cloning.

As Git stores the SVN URL and includes it into the SHA-1 hash calculation you can end up having the following problem as soon as you change the repository URL and try to push your changes to the remote repository:

Unable to determine upstream SVN information from HEAD history.
Perhaps the repository is empty. at /usr/libexec/git-core/git-svn line 519.

The problem is that by changing the SVN repository URL calculated SHA-1 hashes differ and Git cannot determine the proper commit to push to. In order to overcome these problems you can add the rewriteRoot option to your configuration file and afterwards change the URL:

git config --replace-all svn-remote.svn.rewriteRoot http://old.repository.com/url
git config --replace-all svn-remote.svn.url http://new.repository.com/url

Next time you try to push your changes they will be pushed to the new repository destination (newURL) but Git pretends it to be the old repository destination (oldURL).

Simple SVN to Git repository migration

Recently I wanted to migrate an existing Subversion (SVN) repository trunk to a new Git repository. Here is a short description how you can do it in four simple steps.

First of all, create a new bare repository:

$ mkdir NewGitRepo
$ cd NewGitRepo/
$ git init --bare

Secondly, checkout the old SVN repository using Git and enter the repository folder. For this post I created a sample SVN repository on my local hard drive:

$ git svn clone file:///some/file/path/OldSVNRepo/trunk ./OldSVNRepoGit
$ cd OldSVNRepoGit

Thirdly, add your new Git repository as additional remote branch to the checked out SVN repository:

 $ git remote add origin /some/file/path/NewGitRepo/

Finally, push SVN contents to new Git bare repository:

$ git push -u origin master
Counting objects: 12, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (12/12), 1016 bytes, done.
Total 12 (delta 3), reused 0 (delta 0)
Unpacking objects: 100% (12/12), done.
To /some/file/path/NewGitRepo/
 * [new branch]      master -> master
Branch master set up to track remote branch master from origin.

As stated in the heading, this is just a simple way. Additional information regarding this topic can be found in the Pro Git book by Scott Chacon:

http://git-scm.com/book/en/Git-and-Other-Systems-Migrating-to-Git

Deactivating automatic updates in Mac OS X 10.9.4

Recently I had some problems staying under my monthly mobile bandwidth cap. One reason being an increased travel and tethering time. Although working on an up to date system is preferable most of the time, I started to turn off automatic updates on my Mac while working using my mobile connection.

The automatic update settings can be found under System Preferences -> App Store.

App Store Settings
App Store Settings

When traveling you can uncheck all but the “Automatically check for updates” check box. That way you get notified if new updates are available and can set yourself a reminder to update your system when a landline connection is available.

Automatic update settings
Automatic update settings