Hia all,
I just started using jBoss and I must say - it's great!
I only missed the possibility to use Cloudscape as my database of choice
since no type mappings were included in the final version. So I created a
type-mapping which corresponds to the Cloudscape documentation and which
proofed to work in my environment. The integration process works for the
Cloudscape RmiJdbcServer (of Cloudscape 3.5, that's what I tested) - I did
not yet have the time to integrate Cloudconnector.
So I'd like to submit the information I harvested when attempting to
integrate Cloudscape with jBoss [have a good look at point 5.]. Here we go:
0. Copy Cloudscpae.jar into the lib/ext directory of jBoss.
1. As described in the preliminary jBoss manual in the "Installing JDBC
drivers" section, add the following driver to jboss.properties:
jdbc.drivers=COM.cloudscape.core.RmiJdbcDriver,[...]
2. Edit jboss.conf and add:
<MLET CODE="org.jboss.jdbc.XADataSourceLoader" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="Cloudscape">
<ARG TYPE="java.lang.String" VALUE="org.jboss.minerva.xa.XADataSourceImpl">
</MLET>
3. Edit jboss.jcml and add:
<mbean name="DefaultDomain:service=XADataSource,name=Cloudscape">
<attribute
name="URL">jdbc:cloudscape:rmi://localhost:1099/DATABASE</attribute>
<attribute name="JDBCUser">your_name</attribute>
<attribute name="Password">your_password</attribute>
</mbean>
4. Add the following type-mapping to your standardjaws.xml:
<type-mapping>
<name>Cloudscape</name>
<mapping>
<java-type>java.lang.Boolean</java-type>
<jdbc-type>BIT</jdbc-type>
<sql-type>BOOLEAN</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Byte</java-type>
<jdbc-type>TINYINT</jdbc-type>
<sql-type>TINYINT</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Short</java-type>
<jdbc-type>SMALLINT</jdbc-type>
<sql-type>SMALLINT</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Integer</java-type>
<jdbc-type>INTEGER</jdbc-type>
<sql-type>INTEGER</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Long</java-type>
<jdbc-type>BIGINT</jdbc-type>
<sql-type>LONGINT</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Float</java-type>
<jdbc-type>REAL</jdbc-type>
<sql-type>REAL</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Double</java-type>
<jdbc-type>DOUBLE</jdbc-type>
<sql-type>DOUBLE PRECISION</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Character</java-type>
<jdbc-type>CHAR</jdbc-type>
<sql-type>CHAR</sql-type>
</mapping>
<mapping>
<java-type>java.lang.String</java-type>
<jdbc-type>LONGVARCHAR</jdbc-type>
<sql-type>LONG VARCHAR</sql-type>
</mapping>
<mapping>
<java-type>java.sql.Date</java-type>
<jdbc-type>DATE</jdbc-type>
<sql-type>DATE</sql-type>
</mapping>
<mapping>
<java-type>java.sql.Time</java-type>
<jdbc-type>TIME</jdbc-type>
<sql-type>TIME</sql-type>
</mapping>
<mapping>
<java-type>java.sql.Timestamp</java-type>
<jdbc-type>TIMESTAMP</jdbc-type>
<sql-type>TIMESTAMP</sql-type>
</mapping>
<mapping>
<java-type>java.lang.Object</java-type>
<jdbc-type>LONGVARBINARY</jdbc-type>
<sql-type>LONG VARBINARY</sql-type>
</mapping>
</type-mapping>
5. Note: you have to change either the port of JNP (in jnp.properties) or
Cloudscape's port because both use 1099 by default. Without changing one of
the settings you will not be able to lookup a bean from a client!
Well, that's it ... easy, hm? :)
Sorry if I posted to the wrong mailing list. The manual just said, contact
the mailing list ...
Have fun,
Hope this helps,
BENJAMIN BROLL
M A S S P | NEWMEDIA GMBH FRIELINGSDORFWEG | 12 45239 | ESSEN
TELEFON | 49 201 6159141 TELEFAX | 49 201 45139284
[EMAIL PROTECTED] MASSPNEWMEDIA.COM
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
