Group items tagged

There was a recent outburst in blogs on the topic of Groovy and how it compares to Java. Although I respect the youthfull entusiasim of Groovy and Co. working on this little exercise I'm just perplexed by the "WHY?" in this whole discussion. Let me just say again: W H Y ?!?! 1. Practically no one cares about Groovy (let alone Groovy++ strap-on) beyond Grails community. So this language just as "widely accepted" as Ruby (at least for enterprise software development) 2. If you know Java it's equally "challenging" to pick up either Groovy or Scala. Don't let anyone insult your intelligence by claiming that Scala syntax is somehow more complex than Groovy. In both languages you will need to adapt to functional thinking - and that's where you will have to spend a couple of weekends… 3. If you know Groovy - you already know 90% of Scala (different syntax and few extra features can be picked up in the evening) 4. Scala is designed by people who have proper academic background, experience and talent in the area of language design - Groovy has never been that way (and anyone who dares to look inside of Groovy runtime or history of changes in it will attest to that). NOTE: it did come out rather strong - but that's how I feel about it and after some thinking I'll leave as is. Nothing personal to anyone reading it… 5. Scala as a post-functional language is years ahead of Groovy (static typing with best-in-business type inference, highly tuned mix of imperative and functional styles, powerful and done-right generics, etc.) 6. Groovy will ALWAYS be slower than Scala or Java (latest benchmarks put even Groovy++ about 50 times slower than Java) just by its nature unless someone changes the language and rebuilds the runtime from the ground up. 7. Once we get decent integration with Eclipse, NetBeans and IDEA for Scala, the Groovy will lose its only serious advantage

DdlUtils is a small, easy-to-use component for working with Database Definition (DDL) files. These are XML files that contain the definition of a database schema, e.g. tables and columns. These files can be fed into DdlUtils via its Ant task or programmatically in order to create the corresponding database or alter it so that it corresponds to the DDL. Likewise, DdlUtils can generate a DDL file for an existing database. DdlUtils uses the Turbine XML format, which is shared by Torque and OJB. This format expresses the database schema in a database-independent way by using JDBC datatypes instead of raw SQL datatypes which are inherently database specific. An example of such a file is:

Gaelyk is a lightweight Groovy toolkit for Google App Engine Java. Gaelyk lets you deploy small applications on Google App Engine Java. Gaelyk gives you the choice to use Groovy for developing your applications. Gaelyk builds upon Groovlets. and the Groovy template servlet Gaelyk allows you to cleanly seperate your views with Groovy templates and your actions in Groovlets. Gaelyk simplifies the usage of the Google App Engine SDK by providing more concise and more powerful shortcuts when using the datastore, memcache, the blobstore, the images service, the URL fetch service, when sending and receiving emails or Jabber messages, and much more. Gaelyk lets you define friendly REST-ful URLs thanks to its URL routing system Gaelyk provides a simple plugin system for improving code reuse and code sharing You can: download Gaelyk in the download area, learn how to create Gaelyk applications by reading the extensive tutorial, and participate in the community.

Before you read, please look at this video, showing the core features of ECP. The EMF Client Platform is a framework to build EMF-based client applications. The goal is to provide a one-click application based on a given EMF model. Besides the EMF model no additional components have to be developed or generated. Therefore ECP provides a standard solution including the most common features needed for EMF-based client applications. This application can then be customized step by step. This can be done by extending ECP or replacing single components completly.

ModeShape (formerly "JBoss DNA") is a JCR 2.0 (JSR-283) implementation that provides access to content stored in many different kinds of systems. A ModeShape repository isn't yet another silo of isolated information, but rather it's a JCR view of the information you already have in your environment: files systems, databases, other repositories, services, applications, etc. To your applications, ModeShape looks and behaves like a regular JCR repository. Using the standard JCR API, applications can search, navigate, version, and listen for changes in the content. But under the covers, ModeShape gets its content by federating multiple back-end systems (like databases, services, other repositories, etc.), allowing those systems to continue "owning" the information while ensuring the unified repository stays up-to-date and in sync. ModeShape repositories can be used in a variety of applications. One of the most obvious ones is in provisioning and management, where it's critical to understand and keep track of the metadata for models, database, services, components, applications, clusters, machines, and other systems used in an enterprise. Governance takes that a step farther, by also tracking the policies and expectations against which performance can be verified. In these cases, a repository is an excellent mechanism for managing this complex and highly-varied information. But a ModeShape repository doesn't have to be large and complex: it could just manage configuration information for an application, or it could just provide a JCR interface on top of a couple of non-JCR systems.

"At this point, the only source of useful overview documentation for the Common Navigator are the excellent tutorials at Michael Elder's (the author of the CN) blog. Soon I hope to get some of this transferred into the Eclipse Plugin Developer's Guide. RCP applications can quickly and easily use the CN to show the resources in the workspace. This assumes that your RCP application uses resources (which is another discussion). The CN can also be used for non-resource RCP applications, in that case, these instructions don't apply, as the objects treated by the CN have to be created directly by the RCP application. If you are planning to use the CN in an RCP application that uses resources, there are 3 (2 of which are completely undocumented) things you must do:"

"ModelDriven.org is a community of government, commercial and university members who use, develop and integrate open source and commercial capabilities to enable agile business solutions based on model driven methods and technologies. ModelDriven.org is standards based, leveraging Model Driven Architecture® as defined by the OMG and the Semantic Web as defined by W3C. This community has both a user membership and a provider membership. The user community drives the agenda - ..Read More >>"

Data, Context and Interaction (DCI) is a paradigm used in computer software to program systems of communicating objects. Its goals are: To improve the readability of object-oriented code by giving system behavior first-class status; To cleanly separate code for rapidly changing system behavior (what the system does) from code for slowly changing domain knowledge (what the system is), instead of combining both in one class interface; To help software developers reason about system-level state and behavior instead of only object state and behavior; To support an object style of thinking that is close to peoples' mental models, rather than the class style of thinking that overshadowed object thinking early in the history of object-oriented programming languages. The paradigm separates the domain model (Data) from Use cases (Context) and Roles that objects play (Interaction). DCI is complementary to Model-view-controller (MVC). MVC as a pattern language is still used to separate the data and its processing from presentation. DCI was invented by Trygve Reenskaug, also the inventor of MVC. The current formulation of DCI is mostly the work of Reenskaug and James O. Coplien.

"Apache Tuscany simplifies the task of developing SOA solutions by providing a comprehensive infrastructure for SOA development and management that is based on Service Component Architecture (SCA) standard. With SCA as it's foundation, Tuscany offers solution developers the following advantages: Provides a model for creating composite applications by defining the services in the fabric and their relationships with one another. The services can be implemented in any technology. Enables service developers to create reusable services that only contain business logic. Protocols are pushed out of business logic and are handled through pluggable bindings. This lowers development cost. Applications can easily adapt to infrastructure changes without recoding since protocols are handled via pluggable bindings and quality of services (transaction, security) are handled declaratively. Existing applications can work with new SCA compositions. This allows for incremental growth towards a more flexible architecture, outsourcing or providing services to others. In addition, Tuscany is integrated with various technologies and offers: a wide range of bindings (pluggable protocols) various component types including and not limited to Java, C++, BPEL, Spring and scripting an end to end service and data solution which includes support for Jaxb and SDO a lightweight runtime that works standalone or with other application servers a modular architecture that makes it easy to integrate with different technologies and to extend Integration with web20 technologies Apache Tuscany SCA is implemented in Java and C++ (referred to as Native)"

"This chapter introduces the Expression Language (also referred to as the EL), which provides an important mechanism for enabling the presentation layer (web pages) to communicate with the application logic (backing beans). The EL is used by both JavaServer Faces technology and JavaServer Pages (JSP) technology. The EL represents a union of the expression languages offered by JavaServer Faces technology and JSP technology."

Eglobalsystems Offering Core Java Real-time Online Training Classes For Weekend And Regular Batches For Individuals And Professionals. Eglobalsystems Offering Free DEMO/ Seminar On Core Java Access Control By Real Time Expert. Once Experience Our Free Sessions And Decide Further.

Eglobalsystems Offering Core Java Real-time Online Training Classes For Weekend And Regular Batches For Individuals And Professionals. Eglobalsystems Offering Free DEMO/ Seminar On Core Java Access Control By Real Time Expert. Once Experience Our Free Sessions And Decide Further.

This business suite contains Oracle database technologies and a range of product which is acquired or developed by Oracle.

eGlobalSystems Offering pl sql Real-time Online Training Classes For Weekend And Regular Batches For Individuals And Professionals. eGlobalSystems Offering Free DEMO/ Seminar On pl sql Access Control By Real Time Expert. Once Experience Our Free Sessions And Decide Further.

eGlobalSystems is one of the Promote leading IT Services and Core Java Online Training solutions along with IT Training conservatory, with latest Industry offering technology in Eglobalsystems Offering Core Java Real-time Online Training Classes For Weekend And Regular Batches For Individuals And Professionals. Eglobalsystems Offering Free DEMO/ Seminar On Core Java Access Control By Real Time Expert. Once Experience Our Free Sessions And Decide Further.

Eglobalsystems Offering .Net Real-time Online Training Classes For Weekend And Regular Batches For Individuals And Professionals. Eglobalsystems Offering Free DEMO/ Seminar On .Net online training Access Control By Real Time Expert. Once Experience Our Free Sessions And Decide Further.

" Why Object Teams? Team spirit for your objects Building complex systems from isolated objects often yields poor structure which readily decays during system evolution. Objects should team-up in order to co-operate and jointly deliver complex behaviors. Objects play specific roles within a given Team. Context based dispatch Role instances are attached as specializers to existing objects. Object behavior is controlled by the currently active context that determines which roles are active at a given point in time. Contexts are reified into team instances, which may further be used to mediate between roles and maintain state of the collaboration. Modules larger than classes On the road to re-use of modules larger than classes two approaches compete: frameworks and components. For many applications white box frameworks are too fragile and black box components to rigid. Object Teams provide a middle road which balances encapsulation and adaptability. "

" Should you need to compile an OT/J program outside the OTDT, the following steps should enable you to use ANT for this task: download ecotj.jar you'll always find the latest version here in the column "Command Line Compiler" add it to your ANT runtime classpath (either place it in your ant_lib directory or provide the path by a -lib command line option to ant). in your build.xml set the property build.compiler to use the OTDT compiler in tasks, like that: "