THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Yoko consists of several modules, currently
- api This module runs the
xsdtojavatask contained in the celtix codegen plugin which is run with corba-binding schema and generates the java classes for this schema. These classes will then be used by both the tools and runtime modules. - bindings: This module contains bindings that can be used with Celtix which will allow a Celtix application to communicate over a specific protocol. Currently, this module contains the CORBA Runtime Binding (click for more details), which is described by the JIRA issue YOKO-40 - http://issues.apache.org/jira/browse/YOKO-40. In the future, it is hoped that other bindings will also be included.
- tools This module contains the command line tools used for wsdl to idl and idl to wsdl. Functionality will be added on a continous basis once the initial baselines for the tools are done.
- WSDLToIDL The JIRA Issue for this tool is 42 - http://issues.apache.org/jira/browse/YOKO-42. This tool should now support primitive types for the generation of a corba binding and the generation of idl for this corba binding. Support for simple, fault and complex types will be added in the near future.
- IDLToWSDL The JIRA issue for this tool is - JIRA Issue 41 - http://issues.apache.org/jira/browse/YOKO-41
- core: This module contains the ORB and IIOP transport that will be used by the bindings for sending and receiving requests. The ORB will be used in a binding in place of a normal Celtix transport.
The modules bindings and orb should be combined into a coremodule which will represent the core functionality of the Yoko project, as described in the "Initial Tasks" email on the yoko-dev mailing list, March 3rd and 6th, 2006.
TBD: Describe the purpose of each module. What does it contain now, what are the plans? Related Jira issues or components? Are more modules expected in the future, e.g. Naming or Notification Service implementation, IDL to Java compiler, etc.?