Group items tagged

Besides being able to query and manipulate the underlying data management system with Blueprints, a GraphML reader and writer package is provided with Blueprints for streaming XML graph representations into and out of the underlying graph framework. The GraphML package uses StAX to process a GraphML graph. This section discusses the use of the GraphML library for reading and writing XML-encoded graphs.

Android Tutorial. Android is a software package containing linux based operating system for mobile devices such as tablet computers, smartphones etc, middleware and key mobile applicaitons.

There is no migration system in vanilla grails (although possibly in Grails 2.0 …. ?) but there do exist several plugins that provide  some migration functionality. As of this post I am aware of three: dbMigrate, Liquibase, and Autobase. Of these, I prefer Liquibase and cannot recommend it enough. While it uses XML to describe its changesets it is a mature open-source Java project that works flawlessly (and has some excellent documentation). I did not have much luck using DbMigrate and Autobase when including in an existing project… which is a shame as Autobase (which is built on Liquibase) uses a nice DSL syntax to build the migrations.

A few weeks back, I wrote a blog entry lamenting the attitude toward IDEs in the Scala community. A few people told me that the tooling situation was better than I'd implied, so I thought I'd spend a bit of time looking at using Scala (and Lift specifically) in Eclipse. I think the situation is still a ways away from the tooling situation for Java, but it is actually quite good, and I wanted to post a quick tutorial for those interested in developing Lift in Eclipse. Prerequisites This post assumes that you already have Scala 2.8 final and Eclipse 3.6 on your system. For Eclipse, I recommend upping the Xmx setting if you haven't already - I had issues when I had multiple Lift projects imported with Xmx set to 386. Also, this tutorial is going to use Maven, not SBT. SBT may be a better build tool for Scala projects, but I'm not sure how well it works with m2eclipse - I'm going to play with that more later. I also assume you know how to install plugins into Eclipse - I will create a more in-depth screencast for doing all of this if there is enough interest.

Last week I decided to challenge Scala's downscalability by trying to replace a Groovy script with a Scala pendant. In this article you will read about this little experiment and a comparision of the Scala result with the Groovy predecessor. But first some background about the script: Some time ago my company introduced a new spam notification system.  When it thinks that a mail contains spam, it keeps it in quarantine and once or twice a day sends an email to the recipient (me) reporting all the kept mails, together with an intranet web link for each  to release it. Here you see an example of such a mail (note: I have my mails displayed in plain text format):

"Besides a rich user interaction many applications need to display a big amount of data sets as diagrams or reports as part of their applications. In order to bridge the gap the BIRT project was created as part of the eclipse ecosystem. BIRT is an open source Eclipse-based reporting system that integrates with your Java/J2EE application to produce compelling reports. That BIRT integrates well with classic RCP applications is a well known fact. But the need for rich internet applications is still growing. And here the RAP comes into play. As a platform for developing Web 2.0 applications with the same patterns as for RCP it paves the way for single sourcing applications running on both platforms. In this talk we will show how to integrate diagrams and reports known from BIRT into RAP applications. Topics covered include how to setup the environment to let BIRT and RAP play well together. In addition we will give advices how to use the reports inside RAP applications and which problems may arise. As a final outcome of we will know everything to bring reporting capabilities into RAP applications. "

"Business Intelligence and Reporting Tools BIRT is an open source Eclipse-based reporting system that integrates with your Java/J2EE application to produce compelling reports. Get started with the newest major release, BIRT 2.6.1. Get started with the latest in the BIRT 2.5 series. Need help with BIRT? BIRT provides core reporting features such as report layout, data access and scripting. Please try BIRT and tell us what you think by filling bugs reports & enhancement requests through Bugzilla as explained on the community page. "

"Apache Lenya is an Open Source Java/XML Content Management System and comes with revision control, multi-site management, scheduling, search, WYSIWYG editors, and workflow. Please see some screenshots or try the Demo. "

"The agile dependency manager Apache Ivy™ is a popular dependency manager focusing on flexibility and simplicity. Find out more about its unique enterprise features, what people say about it, and how it can improve your build system!"

Provide mechanisms for integrating Java security providers into Eclipse: Applications that need to implement security related functionality require cryptographic services upon which to build. Java provides the Java Cryptography Architecture (JCA) as a mechanism for installing implementations of several interfaces used for cryptography, including MessageDigest, Signature, KeyStore, Certstore, and more. In a typical Java application, these implementations reside in the extensions directory of the JRE. In a dynamic Eclipse application, the appropriate packaging mechanism is in Eclipse plug-ins. The goal is to allow JCA to be used in an Eclipse environment while maintaining the programming model of the JCA subsystem. A related goal is to expose the configuration of the JCA system via an Eclipse-based user interface, allowing authorized users to inspect and modify the Security object.

"How much can the IDE predict what you will write in the next seconds? "Code Recommenders" is a blog about ongoing research projects developing so called Framework Understanding Tools (FrUiTs for short) - or more general recommender systems that help developers to deal with the complexity of today's software development. It has a strong focus on new Eclipse based tools and discusses/presents ideas how to overcome issues with current IDEs."

Knowledge Discovery Metamodel (KDM) is publicly available specification from the Object Management Group (OMG). KDM is a common intermediate representation for existing software systems and their operating environments, that defines common metadata required for deep semantic integration of Application Lifecycle Management tools. KDM was designed as the OMG's foundation for software modernization, IT portfolio management and software assurance. KDM uses OMG's Meta-Object Facility to define an XMI interchange format between tools that work with existing software as well as an abstract interface (API) for the next-generation assurance and modernization tools. KDM standardizes existing approaches to knowledge discovery in software engineering artifacts, also known as software mining.

The CDO (Connected Data Objects) Model Repository is a distributed shared model framework for EMF models and meta models. CDO is also a model runtime environment with a focus on orthogonal aspects like model scalability, transactionality, persistence, distribution, queries and more. CDO has a 3-tier architecture supporting EMF-based client applications, featuring a central model repository server and leveraging different types of pluggable data storage back-ends like relational databases, object databases and file systems. The default client/server communication protocol is implemented with the Net4j Signalling Platform.

Apache CouchDB is a document-oriented database that can be queried and indexed in a MapReduce fashion using JavaScript. CouchDB also offers incremental replication with bi-directional conflict detection and resolution. CouchDB provides a RESTful JSON API than can be accessed from any environment that allows HTTP requests. There are myriad third-party client libraries that make this even easier from your programming language of choice. CouchDB's built in Web administration console speaks directly to the database using HTTP requests issued from your browser. CouchDB is written in Erlang, a robust functional programming language ideal for building concurrent distributed systems. Erlang allows for a flexible design that is easily scalable and readily extensible. See the introduction and the technical overview for more information.

Couchbase: The End of the Trade-off Game Before Couchbase, ops teams managing web applications faced tough compromises when it came to databases. Screaming speed or durable, safe data storage. Super scale out virtually overnight or scaling up with lots of hardware upgrades. Bleeding-edge NoSQL or safe, but inflexible relational solutions. Couchbase eliminates those trade-offs. We supply extraordinary speed with complete safety and incorruptibility.  A growth path that will never force you to rethink your application infrastructure from datacenter deployments to mobile devices - one continuous, synchronized flow. Solutions that complement your other systems - including your RDBMS.  Technology that meets the needs of developers and conforms to the mission-critical demands of ops teams. This really is the beginning of a new era of NoSQL solutions. Couchbase: database solutions for a post-relational world. Learn more.

Akka is the platform for the next generation event-driven, scalable and fault-tolerant architectures on the JVM We believe that writing correct concurrent, fault-tolerant and scalable applications is too hard. Most of the time it's because we are using the wrong tools and the wrong level of abstraction. Akka is here to change that. Using the Actor Model together with Software Transactional Memory we raise the abstraction level and provide a better platform to build correct concurrent and scalable applications. For fault-tolerance we adopt the "Let it crash" / "Embrace failure" model which have been used with great success in the telecom industry to build applications that self-heal, systems that never stop. Actors also provides the abstraction for transparent distribution and the basis for truly scalable and fault-tolerant applications. Akka is Open Source and available under the Apache 2 License.

"The Open Services for Lifecycle Collaboration (OSLC) is an open (creative commons) REST based service specification aimed at improving/simplifying Application Lifecycle Management (ALM) system integration. A number of aspects of ALM integration are covered by OSLC ranging from Requirements Management to Automation(Build/Deploy). The OSLC Change Management (CM) spec outlines a standard for creating, modifying, and querying for change requests (tasks) from OSLC based service providers. A goal of the Mylyn project is to implement a client for OSLC-CM (see [1]). Additionally, support for both OSLC Automation and OSLC SCM are part of the Mylyn restructuring proposal: http://www.eclipse.org/project-slides/mylyn-restructuring-review.html Once these plans have solidified, we can begin to fill out the roadmaps for each specification. "

"An "executable" UML model is one with a behavioral specification detailed enough that it can effectively be "run" as a program. This can be extremely valuable in order to test and validate the model, independently of the one or more implementation platforms to which the system being modeled will ultimately be deployed. Or, in some cases, the model itself can actually be run as the production implementation, given an appropriate execution environment. There have been model execution tools and environments for years, even before UML. However, each tool defined its own semantics for model execution, often including a proprietary action language, and models developed in one tool could not be interchanged with or interoperate with models developed in another tool. A previous post described Stephen Mellor's quest of more than a decade to change this through OMG standards for precise UML model execution semantics and a UML action language. In 2008, this led to the adoption of the Foundational UML (fUML) specification, providing the first precise operational and base semantics for a subset of UML encompassing most object-oriented and activity modeling. The fUML specification still did not provide any new concrete surface syntax, however, tying the precise semantics solely to the existing abstract syntax model of UML. This meant that, in order to fully specify a detailed behavior in a UML model - say the effect behavior of a transition on a state machine or the method of an operation of a class - one still had to draw a very detailed, graphical activity diagram. "

This page contains the latest compiled builds of Pentaho Data Integration (Kettle) community edition.  The builds are based on source code downloaded daily from SVN. Why download these snapshot builds? You want the latest version - to get the latest features in PDI. You want a more stable version - PDI point releases (e.g. 4.0.1) can include important bug fixes - see the PDI JIRA system for a full list of known issues. You need a bug fixed - You're struggling with a critical bug which has been fixed in a more recent version. To save time - You haven't got the time and/or inclination to learn about how to download PDI from SVN and build your own version.

"NTail is a log file 'tail' plugin for Eclipse that enables multiple, independent view instances to be open at the same time. Each view instance is, in turn, capable of hosting its own independent set of log tail viewers. Developed to enable watching host platform and plugin-in runtime platform log files at the same time. Useful to simultaneously watch the log files of a mutli-tier system. Also enables watching the same log file in separate views subject to different line filters."