Based the project Akku http://akkasource.org/ - my interest is in the pluggable persistence layer
Transactors http://doc.akkasource.org/transactors ... "Scala Actors are poor for managing shared state"
Tutorial http://debasishg.blogspot.com/2009/10/pluggable-persistent-transactors-with.html
See MongoDB - document centric DB, compare to couchdb. Includes mapreduce
http://gavingrover.blogspot.com/2007/06/using-prolog-with-groovy.html
*IPLResources
Groovy http://groovy.codehaus.org/
tuProlog - its both flexible and convenient to build inference
engines using JVM based languages - not too much info on performance.
http://www.alice.unibo.it/xwiki/bin/view/Tuprolog/
We have many potential community members and a core team of developers. Additionally, some developers tend not to commit code immedicately to the core trunk, but might like to maintain separate branches until ready. How do we manage it all (committers) without stifling the community process? A restrictive model for inviting committers to the core team is not necessary if we use hybrid SCM approach that allows a central repository for a team plus associated personal branches from both team and non-team members. The latter approach is supported by Bazaar - a distributed SCM that provides for a central repository like subversion. See below for more explanation on the flavors of the central repository.
Distributed SCM:
Mercurial & Subversion SCM googlecode
Bazaar SCM Launchpad https://launchpad.net/
Centralised with local commits: similar to centralised, except that when developers are making a series of changes they use "commit --local", or unbind their checkout, then commit their work to the shared main line when it is complete.
Decentralised with shared main line: each developer has their own branch or branches, plus commit rights to the main branch. They do their work in their personal branch, then merge it into the main line when it is read
Lauchpad hosts Ubuntu and does has more specific tools for Ubuntu sources.
Kenai is great if using the Netbeans IDE
subversion, Mercurial
CMIS is "Content Management Interoperability Services"
CMIS Specification documentApache Chemistry
http://incubator.apache.org/chemistry/
Is Apache Chemistry the followup of Jackrabbit CMIS sandbox? A requirement is that the CMS be JCR compliant (version?)
JCR loves CMIS presentation (Day Software) See Jackrabbit CMIS sandbox!
JCR Jackrabbit CMIS sandbox (images are similar to above slide presentation)
http://wiki.apache.org/jackrabbit/SandboxCMIS
http://www.day.com/o.file/cmis-impl-jrsandbox.pdf?get=b445d210537cf544123a6f6...
CMIS/JCR Server Architecture
Proposed CMIS Client Architecture
QUESTION: can we see SDO (Service Domain Objects) in this architecture? What are pro/cons of option 1 and 2?
CMIS Implementations (JCR + CMIS, CMIS and ?)
Open question: where does SDO (Service Description Objects) fit? SDO + CMIS?
SDO (Service Data Objects)
SOA and SDO: What is SDO?
* SDO - is based on disconnected graph architecture
Supporting data READ/WRITE - change history/tracking
The MOF and OMG's Model Driven Architecture (MDA)
http://en.wikipedia.org/wiki/Meta-Object_Facility/2004/EclipseCon_2004_TechnicalTrackPresentations/40_Frankel.pdf
The use of OCL Object contraint language is used to annotate the ecore based domain model to associate business logic (methods described in the model for example) during the automated generation of code.
* OCL http://de.wikipedia.org/wiki/Object_Constraint_Language
* Discover the Eclipse Modeling Framework (EMF) and Its Dynamic Capabilities http://www.devx.com/Java/Article/29093
Apache Tuscany - A framework to help build SOA based applications
SCA concepts.
Quoted from site: "SCA is a standard programming model for abstracting business functions as components and using them as building blocks to assemble business solutions. An SCA component offers services and depends on functions that are called references. It also has an implementation associated it with it which is the business logic that can be implemented in any technology.
SCA provides a declarative way to describe how the services in an assembly interact with one another and what quality of services (security, transaction, etc) is applied to the interaction. Since service interaction and quality of service is declarative, solution developers remain focus on business logic and therefore development cycle is simplified and shortened. This also promotes the development of reusable services that can be used in different contexts. For example, a shopping cart service can be used in a retail application or a travel application without changing. Services can interact with one another synchronously or asynchronously and can be implemented in any technology.
SCA also brings flexibility to deployment. A solution assembled with SCA is deployed as a unit and can be distributed over one or more nodes in the network and can be reconfigured without programming changes
Applications that adopt SCA programming model can interact with non-SCA applications. Meaning non-SCA application can call into SCA enabled applications and SCA enabled applications can call out into non-SCA enabled application
he basic building block for SCA is a component. It is the abstraction of a given business function. A component is described with the following attributes:
This is demonstrated below.
The implementation of a component can be in any language that is suitable for the user, for example BPEL for business processes or XSL-T for transformations or Ruby for scripting or pure Java. How the services, references, properties and intents are defined for an implementation is specific to that particular implementation type."
