Cisco CVP VoiceXML software has been designed to be easy to use but highly extendable. While the software provides enough to produce high quality voice applications out of the box, many users will want to extend the functionality of the software by building custom components that perform very specific tasks. This document describes the processes and application programming interfaces (APIs) provided for a developer to construct and deploy these components.
Read the rest of this entry »

• 0 Comments

O MNI B ROKER is an Object Request Broker (ORB) that is compliant to the Common Object Request Broker Architecture (CORBA) specification, revision 2.0, as defined in [1] and [2] by the Object Management Group (OMG).
Some highlights of O MNI B ROKER
are:
Full CORBA IDL support
Complete CORBA IDL–to–C++ mapping
Complete CORBA IDL–to–Java mapping
Uses IIOP as native protocol
Dynamic Invocation Interface
Dynamic Skeleton Interface
Interface Repository
Peer–to–Peer communication with nested method invocations
Read the rest of this entry »

• 0 Comments

When I quit my day job in the summer of 2006 to bring an idea of mine to life as an Internet startup, I was faced with a huge number of questions and not a lot of clear answers. The excitement of starting a new project was soon tempered by the difficulty of choosing among the dizzying array of possible technical platforms and solutions. While the shelves were full of books focusing on each of the components of a web application, what I really wanted was a look at how all the pieces fit together.
Read the rest of this entry »

• 0 Comments

This document describes the rationale behind the Web Service Integration Gateway (WSIG) and how to install, configure and use it. The WSIG (version 0.4) is a JADE add-on that provides support for bidirectional invocation of Web services from JADE agents, and JADE agent services from Web service clients. This is the first public release of this add-on and as such it should be treated as a beta that is subject to change at any time.
Read the rest of this entry »

• 0 Comments

Simple template to introduce XDoclet First template: XDoclet architecture Case study: Create Web Service Deployment Descriptor 1st try Case study: Create Web Service Deployment Descriptor 2nd try Summary and resources Use XDoclet to generate Web service support files ibm.com/developerWorks Presented by developerWorks, your source for great tutorials Section 1. About this tutorial What is XDoclet? You can skip this page if you already use XDoclet or already read the first XDoclet tutorial. XDoclet facilitates automated deployment descriptor generation.
Read the rest of this entry »

• 0 Comments

Apply XDoclet to a J2EE project What is XDoclet? • Javadoc metadata templating engine • Attribute-oriented programming • Outgrown its EJBDoclet roots Why XDoclet? • Avoid code metadata duplication • Pragmatic Programming: • DRY - Don’t Repeat Yourself • Program close to the problem domain • Write code that writes code • JSR’s 175 & 181 JSR 175 A metadata facility for the Java Programming Language would allow classes, interfaces, ?elds, and methods to be marked as having particular attributes. JSR 181
Read the rest of this entry »

• 0 Comments

XDoclet is basically just a code generation tool. Many applications have redundant code and/or interfaces and this is where XDoclet comes into play. You can update one source file and use XDoclet to regenerate the affected files. The incredible improvements to content management are clearly obvious. XDoclet parses source code like JavaDoc. By reading JavaDoc tags embedded in source code, XDoclet uses predefined templates to generate code based on those tags. A common use of XDoclet is to embed tags in EJB’s and automatically generate all of the interfaces, beans, and XML descriptors.
Read the rest of this entry »

• 0 Comments

This tutorial shows J2EE developers how to use XDoclet to speed development. XDoclet simplifies continuous integration between components using attribute-oriented programming. It allows you to radically reduce development time by generating deployment descriptors and support code, allowing you to focus on application logic code. If you are a J2EE development veteran, then you realize keeping code in sync with deployment descriptors can be a drag. Often you may need to reuse components with other applications or in other environments like other application servers or with other database systems. You need to keep separate deployment descriptor for each application/environment combination, even if only one or two lines of the large deployment descriptor changes, you need to have a deployment descriptor for every possible configuration.
Read the rest of this entry »

• 0 Comments