Use the quickstart archetype to create a basic Maven project. Maven provides archetypes, which serve as templates for creating new projects. The Maven quickstart archetype is a basic archetype, providing the bare outline of a new Maven project.

To create a new project for the Derby datasource bundle, invoke the Maven archetype plug-in as follows. Open a new command prompt, change directory to a convenient location (that is, to the directory where you will store your Maven projects), and enter the following command:

 mvn archetype:create
-DarchetypeArtifactId=maven-archetype-quickstart
-DgroupId=org.fusesource.example
-DartifactId=derby-ds

	Note
	The preceding command parameters are shown on separate lines for ease of reading. You must enter the entire command on a single line, however.

After downloading the requisite dependencies to run the quickstart archetype, the command creates a new Maven project for the org.fusesource.example/derby-ds artifact under the derby-ds directory.

Change the project packaging type to bundle. Under the derby-ds directory, open the pom.xml file with a text editor and change the contents of the packaging element from jar to bundle, as shown in the following highlighted line:

<project ...>
  ...
  <groupId>org.fusesource.example</groupId>
  <artifactId>derby-ds</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>bundle</packaging>
  ...
</project>

Add the bundle configuration to the POM. In the pom.xml file, add the following build element as a child of the project element:

<project ...>
  ...
  <build>
    <defaultGoal>install</defaultGoal>

    <plugins>

      <plugin>
        <groupId>org.apache.felix</groupId>
        <artifactId>maven-bundle-plugin</artifactId>
        <extensions>true</extensions>
        <configuration>
          <instructions>
            <Bundle-SymbolicName>${project.groupId}.${project.artifactId}</Bundle-SymbolicName>
          </instructions>
        </configuration>
      </plugin>
      
    </plugins>
  </build>

</project>

Customize the Maven compiler plug-in to enforce JDK 1.6 coding syntax. In the pom.xml file, add the following plugin element as a child of the plugins element, to configure the Maven compiler plug-in:

<project ...>
  ...
  <build>
    <defaultGoal>install</defaultGoal>

    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <configuration>
          <source>1.6</source>
          <target>1.6</target>
        </configuration>
      </plugin>
      ...
    </plugins>
  </build>

</project>

Add the Derby dependency to the POM (this is the only Maven dependency that is needed in this project). In the pom.xml file, add the following elements as children of the project element:

<project ...>
  ...
  <properties>
    <derby-version>10.8.2.2</derby-version>
  </properties>

  <dependencies>
    <!-- Database dependencies -->
    <dependency>
      <groupId>org.apache.derby</groupId>
      <artifactId>derby</artifactId>
      <version>${derby-version}</version>
    </dependency>
    
  </dependencies>
  ...
</project>

Customize the derby-version property to the version of Derby you are using.

Instantiate the Derby database instance and export the datasource as an OSGi service. In fact, this example exports two datasources: an XA datasource and a non-transactional datasource. The Derby datasources are exported using a blueprint XML file, which must be stored in the standard location, OSGI-INF/blueprint/. Under the derby-ds project directory, create the dataSource.xml blueprint file in the following location:

src/main/resources/OSGI-INF/blueprint/dataSource.xml

Using your favorite text editor, add the following contents to the dataSource.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0"
            default-activation="lazy">
  
  <bean id="derbyXADataSource" class="org.apache.derby.jdbc.EmbeddedXADataSource">
    <property name="databaseName" value="txXaTutorial"/>
  </bean>

  <service ref="derbyXADataSource" interface="javax.sql.XADataSource">
   <service-properties>
     <entry key="datasource.name" value="derbyXADB"/>
   </service-properties>
  </service>
  
  <bean id="derbyDataSource" class="org.apache.derby.jdbc.EmbeddedDataSource">
    <property name="databaseName" value="txXaTutorial"/>
  </bean>
  
  <service ref="derbyDataSource" interface="javax.sql.DataSource">
   <service-properties>
     <entry key="datasource.name" value="derbyDB"/>
   </service-properties>
  </service>
</blueprint>

In the definition of the derbyXADataSource bean, the databaseName property identifies the database instance that is created (in this case, txXaTutorial). The service element then exports the XA datasource as an OSGi service with the interface, javax.sql.XADataSource. The datasource.name service property makes it possible to identify this datasource unambiguously, when it is referenced from other bundles.

To build the derby-ds bundle and install it in the local Maven repository, enter the following Maven command from the derby-ds directory:

mvn install