--- Yves Trudeau <[EMAIL PROTECTED]>
schrieb: > Hi,
> a few months ago, I got exactly the same problem
> and Alexander
> Schroeder, from Sap Labs, find the solution. Just
> use the following
> mapping:
>
> <mapping>
> <java-type>java.lang.Object</java-type>
> <jdbc-type>VARBINARY</jdbc-type>
> <sql-type>LONG BINARY</sql-type>
> </mapping>
>
>
> And in the code, using Xdoclet
>
> * @ejb.persistence
> * column-name="Objet"
> * sql-type LONG BINARY
> * jdbc-type VARBINARY
>
> This works perfectly for me.
>
> Good Luck!
>
> Yves
>
Hi,
I did that and it worked, thanx! I did change the
mapping in the standardjbosscmp-jdbc.xml file. Do I
have to change it in the standardjaws.xml too or is
that file deprecated?
Is that a mapping that is correct for SapDB in any
case, that means should someone inform the JBoss guys
so that they change the default mapping for SapDB?
The downside of your solution is that I now have two
different code versions for the different dbs (because
of the XDoclet tags). So instead of just having
different config files, the differences are now in the
source code :-((
I think that is the ugly side of XDoclet or is there a
clean way to do this.
Mit sch�nen Gr��en von Yahoo! Mail - http://mail.yahoo.de
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
