Difference between revisions of "Single Port-Type"
From GCube System
Manuele.simi (Talk | contribs) (→From configuration to testing with a single Port-Type) |
Manuele.simi (Talk | contribs) (→From configuration to testing with a single Port-Type) |
||
Line 1: | Line 1: | ||
= From configuration to testing with a single Port-Type = | = From configuration to testing with a single Port-Type = | ||
− | Even if not compulsory, we strongly suggest to adopt the Eclipse 3.3 as development platform. In such an IDE, open a new workspace with a Java 1.5 compiler and create a new Java project | + | Even if not compulsory, we strongly suggest to adopt the Eclipse 3.3 as development platform. In such an IDE, open a new workspace with a Java 1.5 compiler and create a new Java project by specifying a source folder (named from now on, SERVICE folder). Then, fill a user-library with all JARs in gCore lib and name it CONTAINERLIB. |
Revision as of 23:03, 21 March 2008
Contents
From configuration to testing with a single Port-Type
Even if not compulsory, we strongly suggest to adopt the Eclipse 3.3 as development platform. In such an IDE, open a new workspace with a Java 1.5 compiler and create a new Java project by specifying a source folder (named from now on, SERVICE folder). Then, fill a user-library with all JARs in gCore lib and name it CONTAINERLIB.
Structuring the service code
Prepare the source folder structure as follows:
- create a etc folder where to place your configuration file
- create a org/acme/sample folder where to place your source code
- create a schema folder where to place the remote interface files
- copy the share/gcube_tools/build.xml file into your SERVICE folder
Profiling for the infrastructure
Create a new XML file and place it in the SERVICE/etc folder