Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 2 of 5
Compare

APDT: Aspect PHP Developement ToolsThe Aspect PHP Development Tools (APDT) project provides Eclipse platform based tool support for AOSD with PHP. Our goal is to deliver a user experience that is consistent with the PHP Development Tools (PDT) when working with PHPAspect projects and resources. This ... [More] plugin provides an integration layer between the PHPAspect weaver, runtime and Eclipse/PDT extension points. Warning: APDT requires PDT 2.1.0 RC2 at least! PDT 2.1.0 RC2 is available at http://www.eclipse.org/pdt/downloads/! APDT has the following features: Support of phpAspect syntax Wizards for projects, aspects and examples PHPAspect weaver integration PHPAspect and APDT are both Google Summer of Code projects, respectively in 2006 and 2007. [Less]

0
 
  0 reviews  |  0 users  |  13,376 lines of code  |  0 current contributors  |  Analyzed 6 days ago
 
 

The Dash Framework enables Java components to be developed with clear and documentable external dependencies on configuration, component wiring, and runtime context. Dash ObtainDashObtain: Provides lazy, thread-safe acquisition of fields with the @Obtain annotation. Like dependency injection, but ... [More] more declarative. Example @Obtain use (without error handling...): public class Forwarder implements MessageListener { @Obtain MessageProducer forwardTo; public void onMessage(Message message) { forwardTo.send(message); } }Dash ContextDashContext: Provides 'safe' global variables: a public static @Context field can be exposed in a thread-safe, thread-local, and execution scoped manner. An example is authenticated User. Contextual and execution scoped access to the current principal user is easy to show: public class Authentication { @Context static Principal principal; } public class Forwarder implements MessageListener { ... public void onMessage(Message message) { Processor userDefault = getProcessorFor(Authentication.principal); ... } }The reference to Authentication.principal will occur within the scoped execution of a message handler. Within that scope the principal can be setup and reliably removed like this: public class PojoMessageDispatcher { @WithinContext public void dispatchMessage(Message message, MessageListener listener) { Authentication principal = lookupPrincipalFromChannel(); listener.onMessage(message); } }The @WithinContext will ensure that principal, once set, will be null-ed out after the dispatchMessage method returns. Implementation TechnologyThese Dash projects are implemented with Java 5 and AspectJ. They support compile and load-time weaving. [Less]

0
 
  0 reviews  |  0 users  |  2,492 lines of code  |  0 current contributors  |  Analyzed 9 days ago
 
 

Rejuvenate Pointcut is an open source, research prototype Eclipse plugin that limits the problems associated with fragile pointcuts in AspectJ by assisting developers in rejuvenating pointcuts as the base-code evolves. Development of the tool is current in its early stages and we welcome ... [More] interested participants to join in the development effort by contacting the initial author. It is built as an extension to the AspectJ Development Tools (AJDT) and leverages the JayFX fact extractor plugin, the Drools rules engine, and the JDOM XML parser. Please visit the research web site for more details about the internals of the tool. NewsThe plugin now works with the latest AJDT version (version 2.0.2). The plugin was rewritten to incorporate significant architectural changes in this new version of AJDT. DownloadThe latest stable release is Rejuvenate Pointcut 1.2 and has been tested with Eclipse 3.5 SR2 and AJDT 2.0.2. The archive also includes source code used for that particular version. To install, simply unzip the archive into your Eclipse distribution directory. We hope to have an automated update site set up in the near future. Also feel free to check out the latest sources from the SVN repository. Getting startedTake a look at the GettingStarted page. Also, slides from a recent tool demonstration at the International Conference on Aspect-Oriented Software Development (AOSD '09) are available here. A research poster depicting an earlier version of the tool, presented at AOSD '08, is available here. Getting helpPlease feel free to post to the General User Discussion list with any comments, questions, or concerns. [Less]

0
 
  0 reviews  |  0 users  |  8,745 lines of code  |  0 current contributors  |  Analyzed 12 days ago
 
 

IntroductionAspect Oriented is a paradigm of development that grows day by day. Visualize how this aspects affect the whole application is a difficult matter of study. This project helps the software developer and architect to have the vision of how any AOP application is constructed and how each ... [More] component interacts with each other. ProblemWe need to identify and show how aspects interfere within the system model. SolutionAt first we thought of a solution similar to how a compiler parses a portion of code, analyzes it grammatically and then generates a sense of code to be interpreted by a virtual machine or an operating system. In an analog way, in our solution we have to think about a source code program that has to be parsed to build a kind of basic and generic scene and finally this scene be shown in an specific visualizer. The sense of divide it in three components makes the solution more flexible, providing pluggable components in the parser or either in the adapter. That is, you can choose any parser if you give to the model builder what it needs and you can choose any visualizer if you build the adapter to show the scene. ConclusionWe have investigated so far many possibilities to solve the cited problem discovering that in the field of AOP, AspectJ has become the widely-used de-facto standard by emphasizing simplicity and usability for end users. The lack of tools that can clearly show how the aspects crosscut the different model objects makes our approach an amazing challenge to help AOP developers to have a full comprehension of how the system is interacting. How to configure the projectProject configuration and install [Less]

0
 
  0 reviews  |  0 users  |  61,046 lines of code  |  0 current contributors  |  Analyzed 4 days ago
 
 

A Fullstack JSF web Application using MyFaces core 1.2.3 - JSF implementation MyFaces Tomahawk 1.1.7 - JSF component library MyFaces Orchestra 1.1 - extended scopes (conversation, flash) Facelets 1.14 - JSF view technology Spring 2.5 - IOC container Hibernate 3.3.1.ga - JPA persistence layer ... [More] hsqldb 1.8 - database OVal 1.10 - object validation framework To see the application in action: a) download the source archive from http://jsfatwork.googlecode.com/files/jsfatwork1-0.zip b) run it using maven2: mvn tomcat:run [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

The features of WhiteDog System are: Framework for the object sharing applications. i.e. shared paint board or chat application. Annotation based design. Put @Share annotation to the method you want to share its execution. Put @Share annotation to the field you want to synchronize its state at ... [More] session start. Pluggable protocol. Currently, UDP multicasting(JGroups) and in-VM(ClassLoader) are supported. WhiteDog System runs on Java5 and depends on AspectJ1.6. Now Ivy repository is available: http://whitedog.googlecode.com/svn/trunk/ivyrepository/ You can use Ivy repository from your ivy by adding following settings to your ivysettings.xml NewsJan.20 Ivy repository available. Aug.4 WhiteDog now supports state synchronization at starting session. Jun.26 Custom peer factory (PeerFactory) and current message sender (peer) identification (Session.getCurrentPeer()) are supported (in trunk). See chat sample for details Jun.24 Basic peer management (iterate/add event/remove event) is now supported in JGroupsSession implementation (in trunk) Now working forAdditional work relating ivy (publishing each module. source or javadoc artifacts) Projects whitedog WhiteDog core classes which doesn't include any session implementation. whitedog-jgroups JGroups session implementation. whitedog-local Local session implementation. whitedog-sample-paint Sample shared paint application. whitedog-sample-autosessionpaint Sample shared paint application that uses automatic session management aspect(jp.whitedog.AutoSessionAspect). whitedog-sample-localdoublepaint Sample locally shared paint application that has two shared paint area. That uses IN-VM(ClassLoader) session. whitedog-sample-chat Sample chat application. This application explains how to use peer management (and state synchronization) [Less]

0
 
  0 reviews  |  0 users  |  1,885 lines of code  |  0 current contributors  |  Analyzed 2 days ago
 
 

This project is in the process of being moved to tll

0
 
  0 reviews  |  0 users  |  38,940 lines of code  |  0 current contributors  |  Analyzed 6 days ago
 
 

Designed with theatrical lighting design in mind, Cameo provides lighting controls common to Cue based light boards. Cameo is designed to provide young designers and smaller venues an alternative to expensive lighting consoles without sacrificing artistic freedom. Cameo requires the ENTTEC Open ... [More] DMX USB Interface to connect to lighting hardware, but can run in a simulation mode without any hardware. [Less]

0
 
  0 reviews  |  0 users  |  8,034 lines of code  |  0 current contributors  |  Analyzed 4 days ago
 
 

Arid POJOs is a framework for simplifying POJO application development. Automatic Spring Bean GenerationArid POJOs provides a custom Spring/XML namespace that scans a package hierarchy and generate bean definitions for the classes or interfaces that it finds. The classes and interfaces can be ... [More] filtered by an AspectJ type pattern, which supports various criteria including name matching, annotations, and subtypes. The generated beans use autowiring. Here is a simple example. ... ... The generated bean definitions can also instantiate an entirely different class. The original interface/class is passed as a constructor argument. This is used, for example, with the dynamic Generic DAO feature. Dynamic Generic DAOsArid POJOs can also generate DAO implementations from an interface using a Grails GORM/Rails Active Record like mechanism. Here is an example interface: public interface CustomerRepository extends GenericDao { Customer findByCustomerId(String customerId); Customer findUsingSomeStrangeNamedQuery(String firstName, String lastName); }Arid POJOs will generate a proxy, which implements this interface. The findByCustomerId() method is turned into Criteria Query, which searches on the customerId property, and the findUsingSomeStrangeNamedQuery() method ends up calling a named query. This is accomplished using the following bean definitions: ... ... [Less]

0
 
  0 reviews  |  0 users  |  2,624 lines of code  |  0 current contributors  |  Analyzed 3 days ago
 
 

Well still v. indefinate software suite. Non compilable java se ee mix stuff can't really tell where it's going :)

0
 
  0 reviews  |  0 users  |  2,116 lines of code  |  0 current contributors  |  Analyzed about 2 years ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.