Saturday, September 02, 2006

BlogDay 2006









Wish All Blogger A Very Happy BlogDay 2006.

I am feeling really lazy today to write.

See you all soon

Do visit my blog.

Happy Blogging!

Wednesday, March 08, 2006

Design Pattern Definition

i found this definition on internet. Really good definition. simple and explanatery.

"A design pattern is a general solution to a common problem in software design. The idea is that the solution gets translated into code, and that the code can be applied in different situations where the problem occurs."

----x----x----X----x----x----
Technorati Tags:

Wednesday, January 25, 2006

Apache Struts to release Struts 1.3.0 as the "Action Framework"

14 Dec 2005

The Apache Struts flagship product, the leading web application framework for Java, is now known as the "Struts Action Framework".

To make the framework easier to maintain, Apache Struts subdivided the original monolithic distribution into several subprojects. Each subproject has its own website, documentation, and release cycle, and may be downloaded separately. For consistency, the original core framework component also has its own name now: "Struts Action Framework". The JARs and external dependencies for the extensions to Struts Action Framework are being bundled into a convenient distribution known as the "Struts Action Framework Library".

The Struts Action Framework 1.3.0 release will include several exciting new features, including:

* Composable Request Processor
* ActionDynaForm interfaces
* Arbitrary configuration properties
* Catalog and Command Elements
* Enhanced Global Exception Handlers
* Extends attribute for XML configurations
* "isCommitted" Exception Handling
* Postback Actions
* Wildcard ActionConfig properties

The key change in this release is the "composable request processor". The request processor is the framework's "kernal". The request processor methods are now command objects in a flexible chain of commands. Rather than subclassing a monolithic object, developers can now just replace commands with their own implementations. Commands can also be inserted or removed, if needed, to extend or streamline the request processing gauntlet, to better meet the needs of different kinds of applications.

The Struts Action Framework 1.3.0 release, and other milestones on the Apache Struts roadmap, were discussed at ApacheCon on Tuesday, December 13, 2005, in a talk, entitled "Struts 2006: An Embarrassment of Riches". Slides from the talk are available online

Source: Jakarta Apache

----x----x----X----x----x----
Technorati Tags:

Tuesday, December 20, 2005

JRuby for Java. A Java API

Ruby is a reflective, object-oriented programming language. It combines syntax inspired by Ada and Perl with Smalltalk-like object-oriented features, and also shares some features with Python, Lisp, Dylan and CLU. Ruby is a single-pass interpreted language. A fast growing language.

The language was created by Yukihiro "Matz" Matsumoto, who started working on Ruby on February 24, 1993 and released it to the public in 1995.

A new API is arrived as a Open-source from SourceForge.. JRuby.
  • A 1.8.2 compatible Ruby interpreter written in 100% pure Java
  • Most builtin Ruby classes provided
  • Support for interacting with and defining java classes from within ruby
  • Bean Scripting Framework (BSF) support
  • Distributed under a tri-license (CPL/GPL/LGPL)
You can fine more information in following website.
Ruby
JRuby

----x----x----X----x----x----
Technorati Tags:

Monday, December 19, 2005

Marshalling and UnMarshalling of XML files

Marshaling is process of encoding object to put them on the network (on one end) (and then Unmarshal the object to decode the object and place it in the address space on the other end).

In distibuted environment, while sending the object from client to server side, the object is marshelled on stun side , sent across the network and on skeleton side its unmarshelled (given to server for necessory processing).

Once the processing is done by server the response object is marshelled by the skeleton , sent across the network to the client and hece to stub and again unmarshelled and given to client.

So basically marshelling is encrypting phenomenon while transeferring the object on network.


Serialization is process of breaking the object(to be sent across network) into form that can be sent across the network (that is converting it into to a sequence of bytes).

Necessarily, before sending the object across network , it must be serialized.

And Marshelling is next step of sending the encrypted object(which is serialized) across the network.

RMI uses a standard mechanism (employed in RPC systems) for communicating with remote objects: stubs and skeletons. A stub for a remote object acts as a client's local representative or proxy for the remote object. The caller invokes a method on the local stub which is responsible for carrying out the method call on the remote object. In RMI, a stub for a remote object implements the same set of remote interfaces that a remote object implements.
When a stub's method is invoked, it does the following:

* initiates a connection with the remote JVM containing the remote object,
* marshals (writes and transmits) the parameters to the remote JVM,
* waits for the result of the method invocation,
* unmarshals (reads) the return value or exception returned, and
* returns the value to the caller.

The stub hides the serialization of parameters and the network-level communication in order to present a simple invocation mechanism to the caller.
In the remote JVM, each remote object may have a corresponding skeleton (in Java 2 platform-only environments, skeletons are not required). The skeleton is responsible for dispatching the call to the actual remote object implementation. When a skeleton receives an incoming method invocation it does the following:

* unmarshals (reads) the parameters for the remote method,
* invokes the method on the actual remote object implementation, and
* marshals (writes and transmits) the result (return value or exception) to the caller.

In the Java 2 SDK, Standard Edition, v1.2 an additional stub protocol was introduced that eliminates the need for skeletons in Java 2 platform-only environments. Instead, generic code is used to carry out the duties performed by skeletons in JDK1.1. Stubs and skeletons are generated by the rmic compiler.
----x----x----X----x----x----
Technorati Tags:

Thursday, December 15, 2005

Join Crack the Verifier

Every new product needs testing and review done by more than one person to ensure the different view point of technical bottlenecks,bugs, enhancements and improvement on the newly implemented features.Java is not a exception in that.

After the release of Tiger (Jsdk1.5), Sun focusing on its next release of Java Standard Edition 6 Mustang. The one of the main feature of this release is newly improved Type Checking Verifier, a part of Java’s class verifier.

Sun asks Java Developer Community to join to do a strenuous review and analysis on this new produce before it been shipped.

For more details on this topic, please visit suns article Crack the Verifier!

----x----x----X----x----x----
Technorati Tags:

Monday, December 12, 2005

What is service-oriented architecture?

Recently I read a wonderful article about SOA from JavaWorld.

Articles some paragraph are given below.

Service-oriented architecture (SOA) is an evolution of distributed computing based on the request/reply design paradigm for synchronous and asynchronous applications. An application's business logic or individual functions are modularized and presented as services for consumer/client applications. What's key to these services is their loosely coupled nature; i.e., the service interface is independent of the implementation. Application developers or system integrators can build applications by composing one or more services without knowing the services' underlying implementations. For example, a service can be implemented either in .Net or J2EE, and the application consuming the service can be on a different platform or language.

Service-oriented architectures have the following key characteristics:

* SOA services have self-describing interfaces in platform-independent XML documents. Web Services Description Language (WSDL) is the standard used to describe the services.

* SOA services communicate with messages formally defined via XML Schema (also called XSD). Communication among consumers and providers or services typically happens in heterogeneous environments, with little or no knowledge about the provider. Messages between services can be viewed as key business documents processed in an enterprise.

* SOA services are maintained in the enterprise by a registry that acts as a directory listing. Applications can look up the services in the registry and invoke the service. Universal Description, Definition, and Integration (UDDI) is the standard used for service registry.

* Each SOA service has a quality of service (QoS) associated with it. Some of the key QoS elements are security requirements, such as authentication and authorization, reliable messaging, and policies regarding who can invoke services.


Its worth to read the article

Read the article What is service-oriented architecture?

----x----x----X----x----x----

Technorati Tags:
Google

Java Tech Talk
If you like to add Headline Animator to your web site.

Copy the below HTML code to your site.






Who links to me?

Blogroll Me!

Best Blogs in Asia

Directory of Computers/Tech Blogs



Java Get Powered

Powered by Blogger