Download as PDF
Celtix Technology FAQ
Table of Contents
For running Celtix-enabled applications all you need to have is a Java 5 JVM.
To develop services using Celtix, you need Sun Microsystem's Java 5 JDK.
No. Celtix does not require either a J2EE container or a Web container.
Celtix implements the following Web service standards:
Celtix implements the JAX-WS 2.0 specification. JAX-WS 2.0 provides a straightforward way to service-enable your applications using the Java 1.5 Annotation mechanism. It also provides a programming model that enables the creation of Web services-ready Java applications.
Yes. Celtix has extended JAX-WS by adding the concept of system handlers. This allows developers to attach handlers at various points within the invocation chain, giving them more power to interact with the data as it flows in and out of Celtix.
Celtix supports a means to deliver messages to a JMS implementation.
Celtix is not based on a particular JMS implementation. It supports any JMS implementation and ships with the open source ActiveMQ JMS implementation.
While Celtix does not require a J2EE application server, Celtix artifacts can be deployed into a J2EE container.
JBI stands for Java Bussines Integration. It is a standardized set of APIs, Service Provider Interfaces (SPIs) and technologies, maintained through the Java Community Process, for integration of business components.
At a quick glance Celtix and a JBI implementation may appear to be addressing the same set of problems. However, Celtix is not a JBI implementation. Unlike JBI, Celtix provides a much more extensible framework for building services. Its focus is to provide a rich framework for linking non-Java, non-Web Service artifacts as well as building feature rich Web services. Celtix is intended to complement JBI. To this end, it is possible to deploy Celtix runtime components and Celtix developed services inside a compliant JBI container.
SCA stands for Service Component Architecture. It is a set of specifications that describe a framework for building applications and systems using SOA concepts. One of the driving concepts behind SCA is that applications and systems are built up by linking services into assemblies.
SCA focuses on assembling service implementations into complex business applications. Celtix focuses on implementing individual services. Celtix services can be consumed by SCA implementations. Currently, the Celtix project is working with the Tuscany project to ensure robust integration between Celtix services and SCA implementations.
All of the internal components of Celtix are instrumented using JMX. In addition, Celtix supports adding custom JMX instrumentation to any services developed using Celtix. Therefore, Celtix artifacts can be managed by any JMX compliant management tool.