Building bedework for jboss

Jboss supports ear files and war files.

Bedework can be built as a single ear file deployment package. This has the advantage that there is only one copy of all the libraries. Each war file within the ear is essentially configuration files only, defining the context.

An example configuration is found in

<quickstart>/bedework/config/bwbuild/jboss

The entire bwbuild directory can be copied into your home directory and the properties and options files modified to suit.

The bw script (which is in the trunk and will make it's way in 3.4.1.1) can be used to build this...

cd <quickstart>
./bw -bwchome /home/me/bwbuild -bwc jboss deploy.debug

Create user login files

To login you need to link jboss up to ldap etc or create two property files in the jboss <config>/conf/props

Create a bedework.users.properties file with

# users file for demo bedework calendar
douglm=bedework

and a bedework.roles.properties file with

# roles file for demo bedework calendar

Define database resource

In the deploy directory there should be a file containing something like:

<datasources>
  <no-tx-datasource>
    <jndi-name>CalendarDS</jndi-name>
    <connection-url>jdbc:mysql://127.0.0.1:3306/cal3p3</connection-url>
    <driver-class>com.mysql.jdbc.Driver</driver-class>
    <user-name>db-user</user-name>
    <password>db-password</password>
    <idle-timeout-minutes>15</idle-timeout-minutes>
    <metadata>
      <type-mapping>mySQL</type-mapping>
    </metadata>
  </no-tx-datasource>
</datasources>

This MUST be a no-tx-datasource otherwise auto-commit is enabled adn rollbacks will not work.