Vega is an open source platform to test the security of web applications. Vega helps you find and validate SQL Injections, Cross-Site Scripting (XSS), inadvertently disclosed sensitive information, and other vulnerabilities. It is written in Java, GUI based, uses db4o v8.0 for persistence with a shared data model and runs on Linux, OS X, and Windows.

 

However the software is more than just a scanner and proxy. It's a platform for developing new types of tests for web applications so it should be interesting for developers since it's extensible and open source, licensed under the EPL (Eclipse Public License) 1.0 which can be combined freely with db4o software thanks to the dOCL.

 

• Vega on GitHub
• Vega's db4o use on GitHub

 

I just revisited the "db4o for jRuby" project on GitHub and it looks great. This is a project by Kacper Cieśla and Tymon Tobolski with help from Marcin Mielżyński.

Here's the info on how to get started and code snippets for basic usage...

 DataNucleus AccessPlatform 3.0.0 has been released. AccessPlatform provides JDO/JPA standards-compliant access to the widest range of datastores for Java applications. It currently supports persistence to RDBMS, ODBMS (db4o, NeoDatis), Documents (XML, Excel, ODF, OOXML), Web-based (JSON, Amazon S3, GoogleStorage), Map-based (HBase, BigTable, Cassandra, MongoDB) datastores, as well as some others (LDAP).

A cool blog post on how you can use Castle Windsor inversion of control container with db4o. In this example a networked db4o server is used rather than the embedded version.

This is a generic repository. Thanks to the db4o server when you connect to the Windows Service it returns a db4o container (IObjectContainer) which is then used as a session in the repository. For screenshots, commented code snippets and full source code on GitHub check:

http://www.thebuttonfactory.nl/?p=1156

The Griffon db4o plugin enables lightweight access to database functionality using db4o.  The current version of griffon-db4o is 0.4.

Upon installation the plugin will generate the following artifacts at $appdir/griffon-app/conf:

• Db4oConfig.groovy - contains the datasource definition.
• BootstrapDb4o.groovy - defines init/destroy hooks for data to be manipulated during app startup/shutdown.

A new dynamic method named withDb4o will be injected into all controllers, giving you access to an com.db4o.ObjectContainer instance, with which you'll be able to make calls to the database. Remember to make all calls to the database off the EDT otherwise your application may appear unresponsive when doing long computations inside the EDT.

For more details and a complete example please see:

http://docs.codehaus.org/display/GRIFFON/Db4o+Plugin

 

Based on the jena semantic web framework owl2java is a code generator to work with OWL ontologies from java. Ontologies are accessed natively via java classes, methods and attributes. A native interface for the object orierented database db4o with support for transparent persistence can be generated from the internal meta model. Where possible, the implementation adheres to the OWL DL standard and also offers some support for constructs that normally require a reasoner. Interested? Have a look at this post outlining current developments. The project consists of two different blocks of functionality, namely Owl2Jena - transparent access to a ontology via a jena based java api Owl2Db4o - transformation of ontologies to db4o compliant object models with instance mapping This plugin was developed as part of a PHD-Thesis at the Chair of Naval Architecture at the University of Rostock and is published under the GPL 2.0   (Source: http://w ...

(Reproduced with permission from: http://www.gamlor.info/wordpress/2011/04/linqpad-db4o-driver-feature-overview/) This time I’m giving a small feature overview for my LINQPad driver for db4o. I promise that is the last post about this for a while =). Why now? Because I’ve implemented the core set of features and now it is has reached a usable state. Installation Well, just take a look at my previous post. I just repeat the most important steps here: Download the plugin-file and save it somewhere. Open LINQPad and add a new connection. Click on ‘View more drivers’ and there on ‘Browse’. Now choose the downloaded lpx-file and confirm it. Opening a Database After installing there’s a new ‘db4o Driver’ entry in the ‘Add connection’ dialog. After choosing it   you need to specify the path to your db4o database file. Optionally you can add the assemblies which contain the classes of the domain model. If you do so, you can access the original classes in LINQPad. You can also enabl ...

Try it out! In the files directory you can find a class diagram and a manual (in German). Nice simple project to extend a db4o viewer and adapt it to you specific needs. 

https://github.com/luc4/db4o-view

I was really glad to see that db4o based Jease (a Java CMS) is getting more visibility. It seems that db4o champion Maik Jablonski is making a nice progress with the project (2 years since inception and v 1.8 released in March). Take a look at a recent article about Jease that was published in Application Development Trends:

http://adtmag.com/blogs/watersworks/2011/04/jease-2-cms.aspx

Congrats Maik!!

by Roman Stoffel (reproduced with permission from original post) In this little post series I’m going to show how my db4o LINQPad driver is implemented. Some parts of these posts useful for other drivers, other parts will be db4o specific. Side note: There’s already a new version of the LINQPad driver out which fixes some issues. Overview The LINQPad website explains well how LINQPad works. For each query LINQPad starts an app domain. This ensures that LINQPad can cleanly kill a query or any code running. For each query LINQPad generates the CIL code dynamically and then runs it. As I explained in a earlier post you can provide additional assemblies to the query execution context. These assemblies are also included in these app domains. That allows you run use any library in LINQPad. Drivers LINQPad supports different drivers for different data source. A driver is responsible for creating connections, showing the available entities or tables and executin ...