Showing posts with label Frameworks. Show all posts
Showing posts with label Frameworks. Show all posts

Cappuccino is an open source application framework for developing applications that look and feel like the desktop software users are familiar with.

Cappuccino is built on top of standard web technologies like JavaScript, and it implements most of the familiar APIs from GNUstep and Apple's Cocoa frameworks. When you program in Cappuccino, you don't need to concern yourself with the complexities of traditional web technologies like HTML, CSS, or even the DOM. The unpleasantries of building complex cross browser applications are abstracted away for you.

Cappuccino was implemented using a new programming language called Objective-J, which is modelled after Objective-C and built entirely on top of JavaScript. Programs written in Objective-J are interpreted in the client, so no compilation or plugins are required. Objective-J is released alongside Cappuccino in this project and under the LGPL.

Cappuccino is not designed for building web sites, or making existing sites more "dynamic". We think these goals are too far removed from those of application development to be served well by a single framework. Projects like Prototype and jQuery are excellent at those tasks, but they are forced by their nature to make compromises which render them ineffective at application development.

On the other end of the existing frameworks are technologies like SproutCore. While SproutCore set out with similar goals to Cappuccino, it takes a distincly different approach. It still relies on HTML, CSS, JavaScript, Prototype, and an entirely new and unique set of APIs. It also requires special development software and a cumbersome compilation step. We think this is the wrong approach.

With Cappuccino, you don't need to know HTML. You'll never write a line of CSS. You don't ever have interact with DOM. We only ask developers to learn one technology, Objective-J, and one set of APIs. Plus, these technologies are implementations of well known and well understood existing ones. Developers can leverage decades of collective experience to really accelerate the pace of building rich web applications.

If you want to build a rich web application, you need to learn something new. Many people think this will be JavaScript 2, or HTML 5, or some new standard. The problem is, as we've come to realize, standards bodies work too slowly. Cappuccino works right now, not in the theoretical future. Objective-J is essentially JavaScript 2, but available today in every major browser. Because we rely on only the most essential web technologies, improvements are not limited by the pace of browser vendors and standards bodies.

Hibernate is a powerful object relational mapping tool written in Java. Hibernate allows you to develop persistent classes mirroring object oriented paradigm - including association, inheritance, polymorphism, composition, and collections. Hibernate has its own portable SQL based langugage (HQL) or can work with native SQL. Hibernate simplifies persistence programming tasks by providing a higher abstraction.

Hibernate is a suite of tools for ORM, including Hibernate core, Hibernate Tools, Hibernate search etc. Only core is required for basic ORM. Each component is available as a separate download.
Hibernate stores table to class mapping in an external XML file. Following is a sample,
<hibernate-mapping>
    <class name=”tasks.Task” table=”TASKS”>
        <id name=”id” column=”TASK_ID”>
            <generator class=”native”/>
        </id>
        <property name=”date” type=”timestamp” column=”TASK_DATE”/>
        <property name=”title”/>
    </class>
</hibernate-mapping>


POJO deployment is the one way of web service deployment in Axis2. Here we are dropping the .class file or .jar file into the POJO directory in the repository. If it is a web application Axis2 is considering WEB-INF as its repository. The main features of the Axis2 POJO are...
  • Support for primitive types (int, boolean, long, String, and so on)
  • Support for method excludes
  • Support for any kind of "Java Beans"
  • Support for Object Arrays
  • Binary support using byte[] and DataHandlers
  • Support of Axiom
  • Serialization support for List
  • Namespaces handling
  • Inheritances support
  • Support for Bean property excludes
  • Method overloading support using annotations
Technorati Tags: ,

Continuum, Cruise Control and Hudson are some of the famous continuous integration tools which people are using nowadays. Cruise Control is the pioneer one and people are using from a long period of time. Continuum is from the Maven team and very high integration with Maven 1 and 2. Hudson is the new one but it is more popular now.
In our department my PM asked me and to my friend, to do the Cruise Control + SVN +Maven based continuous build mechanism. During this process I had gone through some more R&D on the tools which are available for the continuous build process. In that process I found some of the comments about Hudson. Those were very interesting.. So I thought of comparing this with our Cruise control.
Here in this post I am trying to compare Hudson and Cruise Control. The basic TEN points or features listed below are taken from Hudson's official site and I am just trying to compare these all with the capabilities of cruise Control. I had tried to add my own experience with these. Correct me if there is any features that were wrongly entered or any new features that you know about these.
Versions and platform:
Hudson            : 1.213
Cruise Control : 2.7.1
Plat form         : Windows
images Hudson
banner Cruise Control
1 Open Source     1 Open Source
2 Easy installation: Just java -jar Hudson.war, or deploy it in a servlet container. No additional install, no database.
2.
It also gives us very easy installation. Just unzip the downloaded zip file. That's it. It is actually using an internal Jetty server. No Database, no install here also.
3 Easy configuration: Hudson can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help. There's no need to tweak XML manually anymore, although if you'd like to do so, you can do that, too.
3.
Big difference comes here. The GUI providing by Cruise control for configuration is not at all good. It just displays the config.xml file. :( Its no way near to Hudson for Configuration GUI part. If you want to configure Cruise Control then you must study about the structure of the Config.xml first.
4 Change set support: Hudson can generate a list of changes made into the build from CVS/Subversion. This is also done in a fairly efficient fashion, to reduce the load of the repository.
4.
Cruise control also show the list of files which are changes at this check-in process.
5 Permanent links: Hudson gives you clean readable URLs for most of its pages, including some permanent links link "latest build"/"latest successful build", so that they can be easily linked from elsewhere.
5.
Uhm... Cruise control is not giving this. It gives a link with some log code number attached with it. Its looking horrible and cant be easily likable.
6 RSS/E-mail/IM Integration: Monitor build results by RSS or e-mail to get real-time notifications on failures.
6.
It also gives RSS and email functionality. Don't know about IM support. If we need to change the Email structure then either we have to change XSL or CSS file which we are using  in the email config.
7 After-the-fact tagging: Builds can be tagged long after builds are completed
7.
N.A.
8 Detect new failing tests while build     8 Failing tests will show in the dashboard. But no separation between new and old.
9 Notify when first test in build fails     9 No such type of notification.
10 JUnit/TestNG test reporting: JUnit test reports can be tabulated, summarized, and displayed with history information, such as when it started breaking, etc. History trend is plotted into a graph.
10
It is showing all the unit test results but not as good as Hudson does. There is no detailed information like when it started breaking, History etc. and no graph for unit results too.
11 Distributed builds: Hudson can distribute build/test loads to multiple computers. This lets you get the most out of those idle workstations sitting beneath developers' desks.
11.
The build distribution is done through the maven install goal. Its
12 File fingerprinting: Hudson can keep track of which build produced which jars, and which build is using which version of jars, and so on. This works even for jars that are produced outside Hudson, and is ideal for projects to track dependency.
12.
No idea.
13 Plugin Support: Hudson can be extended via 3rd party plug-ins. You can write plug-ins to make Hudson support tools/processes that your team uses.
13.
Plug-ins are there in Cruise control also.
14 Dash board: Hudson has an attractive dashboard with Colorful as well as meaningful icons. We can separate this building projects into subgroups also. It will also shows building projects. Well designed Ajax pages.
14.
It gives an attractive Dash board. It displays all the necessary information which we need to know. We can directly build from there also. Viewing/ downloading the log file is also allowed from this Interface.
15 Local Copy of projects: Handled by Hudson itself. No need to do by the user.
15.
Maintaining a local copy with the exact SVN data makes us more uncomfortable. The user has to copy the Project into the local folder with SVN data.
16 Auto copy of SVN updates: No need to provide any other code to copy the project from SVN to the local compiling folder.
16.
Its not copying the data from the SVN directly. We need to write (In our case we wrote an ANT build file to download the latest copy of Project from SVN) something separate.
17 Running In background: If the server where we deployed the war is running then its okay for Hudson.
17.
If we want to run it without console then we need to make it a separate 'WINDOWS Service' using any third party tool.
18 We can deploy the war file in any of the server we wanted.
18.
Jetty server is using internally.
19 User authorization schemes. more configurable.
19.
User authentication is there but no schemes at all.
20 Very Active mailing list.
20.
From a long period people are using this. So it gives so many search results. But its mailing list is not that much active when compared with Hudson.

Alternative building tools available.

I got this list from ThoughtWorks. HERE we will get a good comparison of these all.
Conclusion:
In my opinion Hudson much more better than Cruise Control. The time we will take to start to use Cruise control will be high when we compared with Hudson. The GUI which makes all the Configurations very very easy. The Ajax support makes the configuration more "Error Free". Though Cruise control is using by a lot of people, when we looked into the features, mailing list, the fastness and support from Developers I think Hudson will be a good option.
Related links : Continuous Integration with Hudson: A Presentation and an Interview podcast


PostgreSQL is a powerful, open source relational database system. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. It runs on all major operating systems and boasts sophisticated features such as Multi-Version Concurrency Control (MVCC), point in time recovery, tablespaces, asynchronous replication, nested transactions (savepoints), online/hot backups, a sophisticated query planner/optimizer, and write ahead logging for fault tolerance. It is highly scalable both in the sheer quantity of data it can manage and in the number of concurrent users it can accommodate. There are active PostgreSQL systems in production environments that manage in excess of 4 terabytes of data.
Do Visit http://www.postgresql.org

ProcessMaker is the first truly Open Source business process management (BPM) and workflow software designed for small and mid-sized businesses (SMBs) and organizations.
ProcessMaker is a user-friendly application to manage workflow efficiently and effectively.  Business users and process experts with no programming experience can design and run workflows, increase transparency, and radically reduce paperwork.  Automate processes across systems, including human resources, finance, and operations.
ProcessMaker workflow management software is easy to use and easy to implement.  The ProcessMaker toolbox allows you to create forms, design documents, manage roles and users, designate routing rules, link to third-party systems, and map fully-functional workflows.  The software is entirely web-based, making it simple to coordinate workflow across offices.  ProcessMaker connects with your existing IT infrastructure, including DMS, ERP, CRM, and BI systems and databases.
ProcessMaker Enterprise clients enjoy a fully supported, top quality BPM suite with the added benefits of Open Source.  ProcessMaker adapts to meet your IT needs and requires minimal implementation resources.  Flexible and customizable, ProcessMaker has been implemented in a variety of industries including finance, telecommunications, manufacturing, and government.  Learn more about how ProcessMaker's Enterprise solutions can work for your business.
Sugar CRM is the world's leading provider of commercial open source customer relationship management (CRM) software. Founded as an open source project in 2004, SugarCRM applications have been downloaded over five million times and currently serve over 500,000 users in 75 languages. Over 4,000 customers have chosen SugarCRM's On-Site and Cloud Computing services over lock-in based, proprietary alternatives. In the last year, SugarCRM has been recognized for its customer success and product innovation by CRM Magazine, InfoWorld, Customer Interaction Solutions and Intelligent Enterprise.
Do Visit : http://www.sugarforge.org/

 Talend is the first provider of open source data integration software. After three years of intense research and development, and with solid financial backing from leading investment firms, Talend revolutionized the world of data integration when it released the first version of Talend Open Studio in 2006. Talend Open Studio is used primarily for migration and integration between operational systems, as well as for ETL (extract, transform, load) for business intelligence and data warehousing. Unlike proprietary, closed solutions, which can only be afforded by the largest organizations, Talend makes enterprise-class data integration solutions affordable to organizations of all sizes. To download Talend Open Studio free of charge, visit www.talend.com.

Openbravo is a fully functional integrated web-based open source enterprise management system (commonly known as ERP) that is much more at a cost that is far less: be the true owner of your ERP and only pay for the professional support that you really need. The solution is designed for small and mid-sized companies (SMEs) that are looking for an integrated way to manage their operations, optimize processes, increase customer satisfaction and ultimately increase profitability. Since 2001, Openbravo is used by many companies of varying size and across a wide variety of business sectors, from distributors to service and industrial companies
Do Visit : http://www.openbravo.com/
Alfresco is the leading open source alternative for enterprise content management. It is the first company to bring the power of open source to the enterprise content management market, enabling unprecedented scale, ease-of-use and a much lower total cost of ownership than proprietary systems. Alfresco aims to provide an open source offering that surpasses commercial offerings in terms of features, functionality and benefits. Alfresco is founded by a team of content management veterans that includes the co-founder of Documentum, John Newton former COO of Business Objects, John Powell and Dr. Ian Howells former Worldwide VP Marketing SeeBeyond.
Do Visit : http://www.alfrescosoftware.com/

The JFreeChart project was founded eight years ago, in February 2000, by David Gilbert. Today, JFreeChart is used by approximately 40,000 to 50,000 developers (see a list of some of the products and projects that use JFreeChart).
JFreeChart is a free 100% Java chart library that makes it easy for developers to display professional quality charts in their applications. JFreeChart's extensive feature set includes:
  • a consistent and well-documented API, supporting a wide range of chart types;
  • a flexible design that is easy to extend, and targets both server-side and client-side applications;
  • support for many output types, including Swing components, image files (including PNG and JPEG), and vector graphics file formats (including PDF, EPS and SVG);
  • JFreeChart is "open source" or, more specifically, free software. It is distributed under the terms of the GNU Lesser General Public Licence (LGPL), which permits use in proprietary applications.
Download from HERE
API Docs find HERE
Samples find HERE

Spring Web Services is a product of the Spring community focused on creating document-driven Web services. Spring Web Services aims to facilitate contract-first SOAP service development, allowing for the creation of flexible web services using one of the many ways to manipulate XML payloads. images

Key Features

  • Makes the Best Practice an Easy Practice: Spring Web Services makes enforcing best practices easier. This includes practices such as the WS-I basic profile, Contract-First development, and having a loose coupling between contract and implementation.
  • Powerful mappings: You can distribute incoming XML request to any object, depending on message payload, SOAP Action header, or an XPath expression.
  • XML API support: Incoming XML messages can be handled in standard JAXP APIs such as DOM, SAX, and StAX, but also JDOM, dom4j, XOM, or even marshalling technologies.
  • Flexible XML Marshalling: The Object/XML Mapping module in the Spring Web Services distribution supports JAXB 1 and 2, Castor, XMLBeans, JiBX, and XStream. And because it is a separate module, you can use it in non-Web services code as well.
  • Reuses your Spring expertise: Spring-WS uses Spring application contexts for all configuration, which should help Spring developers get up-to-speed nice and quickly. Also, the architecture of Spring-WS resembles that of Spring-MVC.
  • Supports WS-Security: WS-Security allows you to sign SOAP messages, encrypt and decrypt them, or authenticate against them.
  • Integrates with Acegi Security: The WS-Security implementation of Spring Web Services provides integration with Spring Security . This means you can use your existing configuration for your SOAP service as well.
  • Built by Maven: This assists you in effectively reusing the Spring Web Services artifacts in your own Maven-based projects.
  • Apache license. You can confidently use Spring-WS in your project.

Formerly the Acegi Security System for Spring, Spring Security provides powerful and flexible security solutions for enterprise applications developed using the Spring Framework. It is a stable and mature product - Acegi Security 1.0.0 was released in May 2006 after more than two and a half years of use in large production software projects and adopted as an official Spring sub-project on its release.

images

Spring Security 2.0.0 builds on Acegi Security's solid foundations, adding many new features:

  • Simplified namespace-based configuration syntax. Old configurations could require hundreds of lines of XML but our new convention over configuration approach ensures that many deployments will now require less than 10 lines.
  • OpenID integration, which is the web's emerging single sign on standard (supported by Google, IBM, Sun, Yahoo and others)
  • Windows NTLM support, providing easy enterprise-wide single sign on against Windows corporate networks
  • Support for JSR 250 ("EJB 3") security annotations, delivering a standards-based model for authorization metadata
  • AspectJ pointcut expression language support, allowing developers to apply cross-cutting security logic across their Spring managed objects
  • Substantial improvements to the high-performance domain object instance security ("ACL") capabilities
  • Comprehensive support for RESTful web request authorization, which works well with Spring 2.5's @MVC model for building RESTful systems
  • Long-requested support for groups, hierarchical roles and a user management API, which all combine to reduce development time and significantly improve system administration
  • An improved, database-backed "remember me" implementation
  • Support for portlet authentication out-of-the-box
  • Support for additional languages
  • Numerous other general improvements, documentation and new samples
  • New support for web state and flow transition authorization through the Spring Web Flow 2.0 release
  • New support for visualizing secured methods, plus configuration auto-completion support in Spring IDE
  • Enhanced WSS (formerly WS-Security) support through the Spring Web Services 1.5 release
  • Updated support for CAS single sign-on (CAS 3 is now supported).

Symfony provides an architecture, components and tools for developers to build complex web applications faster. Choosing symfony allows you to release your applications earlier, host and scale them without problem, and maintain them over time with no surprise.

images

Symfony is based on experience. It does not reinvent the wheel: it uses most of the best practices of web development and integrates some great third-party libraries.

Symfony is a Model-View-Controller (MVC) framework written in PHP that's aimed at building web applications. If you're already familiar with the MVC paradigm, you won't be surprised by the way symfony organizes scripts. If you aren't familiar with MVC, you just need to understand that separating the code into three parts -- the logic code (called the Model), the presentation code (the View), and the request handling code (the Controller) -- is a good way to ensure the maintainability and reusability of code.

Not only is Symfony an MVC implementation in PHP, it also integrates a lot of objects that facilitate the development of web applications -- and integrates them all with a coherent syntax. Smart URLs, code generation, easy templating, internationalization, caching, automated form validation, and Ajax, are among the most appreciated symfony features. Developing an application with symfony is slightly different than building it with any other framework, or without any framework at all. It's faster, more productive, and just plain fun. But enough talk, let's see some code. [From Francois Zaninotto’s Article]

Home of Symfony Click here

Beginners Tutrorial Click Here

Dojo is the Open Source, portable JavaScript toolkit that lets you build interactive modules quickly, animate transitions, and construct Ajax requests with ease. We think Dojo is the most powerful and easiest to use Ajax and DHTML toolkit on the planet.

Dojo is an Open Source DHTML toolkit written in JavaScript. It builds on several contributed code bases (nWidgets, Burstlib, f(m)), which is why we refer to it sometimes as a "unified" toolkit. Dojo aims to solve some long-standing historical problems with DHTML which prevented mass adoption of dynamic web application development.
Dojo allows you to easily build dynamic capabilities into web pages and any other environment that supports JavaScript sanely. You can use the components that Dojo provides to make your web sites more usable, responsive, and functional. With Dojo you can build degradable user interfaces more easily, prototype interactive widgets quickly, and animate transitions. You can use the lower-level APIs and compatibility layers from Dojo to write portable JavaScript and simplify complex scripts. Dojo's event system, I/O APIs, and generic language enhancement form the basis of a powerful programming environment. You can use the Dojo build tools to write command-line unit-tests for your JavaScript code. The Dojo build process helps you optimize your JavaScript for deployment by grouping sets of files together and reuse those groups through "profiles".
Home of Dojo here
Tutorials, RoseIndia

JUnit is the de facto standard unit testing library for the Java™ language. JUnit 4 is the first significant release of this library in almost three years. It promises to simplify testing by exploiting Java 5's annotation feature to identify tests rather than relying on subclassing, reflection, and naming conventions. In this article, obsessive code tester Elliotte Harold takes JUnit 4 out for a spin and details how to use the new framework in your own work. Note that this article assumes prior experience with JUnit.

Home of JUnit, Articles and Guides: PDF Guide, JavaDoc, Tutorials

AspectJ is a seamless aspect-oriented extension to the Java programming language, Java platform compatible and easy to learn and use. AspectJ enables the clean modularization of crosscutting concerns such as: error checking and handling, synchronization, context-sensitive behavior, performance optimizations, monitoring and logging, debugging support, multi-object protocols.

aspectjbanner2

Home of AspectJ,

Tutorials IBM Developer Works, Programming Guide, InformIT Article

Aspect-oriented programming is a way of modularizing crosscutting concerns much like object-oriented programming is a way of modularizing common concerns. AspectJ is an implementation of aspect-oriented programming for Java.

AspectJ adds to Java just one new concept, a join point -- and that's really just a name for an existing Java concept. It adds to Java only a few new constructs: pointcuts, advice, inter-type declarations and aspects. Pointcuts and advice dynamically affect program flow, inter-type declarations statically affects a program's class hierarchy, and aspects encapsulate these new constructs.

A join point is a well-defined point in the program flow. A pointcut picks out certain join points and values at those points. A piece ofadvice is code that is executed when a join point is reached. These are the dynamic parts of AspectJ.

AspectJ also has different kinds of inter-type declarations that allow the programmer to modify a program's static structure, namely, the members of its classes and the relationship between classes.

AspectJ's aspect are the unit of modularity for crosscutting concerns. They behave somewhat like Java classes, but may also include pointcuts, advice and inter-type declarations.

While working with Hibernate web applications we will face so many problems in its performance due to database traffic. That to when the database traffic is very heavy . Actually hibernate is well used just because of its high performance only. So some techniques are necessary to maintain its performance. Caching is the best technique to solve this problem. In this article we will discuss about, how we can improve the performance of Hibernate web applications using caching.
 Hibernate uses two different caches for objects: first-level cache and second-level cache..
1.1) First-level cache
First-level cache always Associates with the Session object. Hibernate uses this cache by default. Here, it processes one transaction after another one, means wont process one transaction many times. Mainly it reduces then number of SQL queries it needs to generate within a given transaction. That is instead of updating after every modification done in the transaction, it updates the transaction only at the end of the transaction.
1.2) Second-level cache
Second-level cache always associates with the Session Factory object. While running the transactions, in between it loads the objects at the Session Factory level, so that those objects will available to the entire application, don’t bounds to single user. Since the objects are already loaded in the cache, whenever an object is returned by the query, at that time no need to go for a database transaction. In this way the second level cacheworks. Here we can use query level cache also. Later we will discuss about it.

2) Cache Implementations

Hibernate supports four open-source cache implementations named EHCache (Easy Hibernate Cache), OSCache (Open Symphony Cache), Swarm Cache, and JBoss Tree Cache. Each cache has differentperformance, memory use, and configuration possibilities.
2.1)2.1EHCache(EasyHibernateCache) (org.hibernate.cache.EhCacheProvider)
  • It is fast.
  • lightweight.
  • Easy-to-use.
  • Supports read-only and read/write caching.
  • Supports memory-based and disk-based caching.
  • Does not support clustering.
2.2)OSCache(OpenSymphonyCache) (org.hibernate.cache.OSCacheProvider)
  • It is a powerful .
  • flexible package
  • supports read-only and read/write caching.
  • Supports memory- based and disk-based caching.
  • Provides basic support for clustering via either JavaGroups or JMS.
2.3)SwarmCache (org.hibernate.cache.SwarmCacheProvider)
  • is a cluster-based caching.
  • supports read-only or nonstrict read/write caching .
  • appropriate for applications those have more read operations than write operations.
2.4)JBoss TreeCache (org.hibernate.cache.TreeCacheProvider)
  • is a powerful replicated and transactional cache.
  • useful when we need a true transaction-capable caching architecture .
LiveJournal Tags: ,
Technorati Tags: ,

JDOM is an open source Java-based document object model for XML that was designed specifically for the Java platform so that it can take advantage of its language features. JDOM integrates with Document Object Model (DOM) and Simple API for XML (SAX), supports XPath and XSLT. It uses external parsers to build documents.

JDom Java Doc Find here

  • JDOM is Java platform specific. The API uses the Java language's built-in String support wherever possible, so that text values are always available as Strings. It also makes use of the Java 2 platform collection classes, like List andIterator, providing a rich environment for programmers familiar with the Java language.
  • No hierarchies. In JDOM, an XML element is an instance of Element, an XML attribute is an instance of Attribute, and an XML document itself is an instance of Document. Because all of these represent different concepts in XML, they are always referenced as their own types, never as an amorphous "node."
  • Class driven. Because JDOM objects are direct instances of classes like Document, Element, and Attribute, creating one is as easy as using the new operator in the Java language. It also means that there are no factory interfaces to configure -- JDOM is ready to use straight out of the jar.
LiveJournal Tags: ,
Castor XML is an XML databinding framework. Unlike the two main XML APIs, DOM (Document Object Model) and SAX (Simple API for XML) which deal with the structure of an XML document, Castor enables one to deal with the data defined in an XML document through an object model which represents that data.

Castor XML can marshal almost any "bean-like" Java Object to and from XML. In most cases the marshalling framework uses a set of ClassDescriptors and FieldDescriptors to describe how an Object should be marshalled and unmarshalled from XML.
For those not familiar with the terms "marshal" and "unmarshal", it's simply the act of converting a stream (sequence of bytes) of data to and from an Object. The act of "marshalling" consists of converting an Object to a stream, and "unmarshalling" from a stream to an Object.

del.icio.us Tags: ,,,
LiveJournal Tags: ,,,
+