Re: ojb_blank problem

Is there nobody, who can help me ?
If there is no solution for this (in my view - ojb Bug) i must cancel 
ojb and migrate to hibernate... (what i dont like)

Hans

Hans Novak schrieb:
> Hi,
>
> i need help to run the ojb_blank projekt (i try with mysql & hsql, 
> same errors)
> If i configure it like the tutorial says, i get in eclipse some errors:
> first, i get a lot of errors like this:
>
>
> [ojbdoclet] 2007-08-29 13:35:28,017 [main] INFO  
> xdoclet.XDocletMain.start - Running <ojbrepository/>
> [ojbdoclet] Error parsing File 
> /home/hnovak/eclipse-workspace/osfaktura/src/java/AfterBuyImport.java:Lexical 
> error: xjavadoc.TokenMgrError: Lexical error at line 11, column 1.  
> Encountered: "@" (64), after : ""
> [ojbdoclet] Error parsing File 
> /home/hnovak/eclipse-workspace/osfaktura/src/java/de/repcom/osfaktura/core/partner/Partner.java:Encountered 
> "<" at line 255, column 22.
> [ojbdoclet] Was expecting one of:
> [ojbdoclet]     <IDENTIFIER> ...
> [ojbdoclet]     "[" ...
> [ojbdoclet]     "." ...
> [ojbdoclet]     "(" ...
>
>
> at the line 255 in Partner.java is Collection<Task> col ...
> It sounds like, that it can recognize the Java 5/6 notation.
> The  "project-schema.xml/sql" is not written correctly. On some 
> classes it miss the foreign-key statements. If i cut the java 5/6 
> notation out from Collection in the java classes, then it writes it 
> correctly with foreign-key statements.
>
> Then i get these errors:
>
>
> shutdown-check:
> append-shutdown-sql:
>    [echo]
>    [echo]       Executing the create-db.sql script ...
>    [echo]         [sql] Executing resource: 
> /home/hnovak/eclipse-workspace/osfaktura/build/database/create-db.sql
>     [sql] Failed to execute:  ECHO Not implemented      [sql] 
> java.sql.SQLException: Unexpected token: ECHO in statement [ ECHO]
>     [sql] 1 of 2 SQL statements executed successfully
> insert-sql:
> shutdown-check:
> add-shutdown-sql-file:
> [torque-sql-exec] Our new url -> jdbc:hsqldb:build/database/ojb_blank
> [torque-sql-exec] Executing file: 
> /home/hnovak/eclipse-workspace/osfaktura/build/database/project-schema.sql 
>
> [torque-sql-exec] Failed to execute: drop table PARTNER if exists;  
> ... (SNIP REST OUT) ...
> [torque-sql-exec] Executing file: 
> /home/hnovak/eclipse-workspace/osfaktura/build/database/ojbcore-schema.sql 
>
> [torque-sql-exec] Executing file: 
> /home/hnovak/eclipse-workspace/osfaktura/build/database/shutdown.sql
> [torque-sql-exec] 2 of 3 SQL statements executed successfully
> BUILD SUCCESSFUL
> Total time: 6 seconds
>
>
> If i do a:  "mysql db <./project-schema.sql" (and the other two sql 
> scripts) it works fine (except for the "foreign key" statements, i 
> wrote above)
>
>
> Hans
>
>

-- 


	
------------------------------------------------------------------------

	
Repcom Datentechnik GmbH <http://www.repcom.de/>
Hauptstr. 103 - 63110 Rodgau
Tel. 06106-638081
Fax 06106-638083
Steuernummer 03524225030 
Ust-IdNr.: DE151061445 	Bankverbindung:
Deutsche Bank Dietzenbach,
Kto. 1516400 BLZ 50570024 , Inhaber  Repcom Datentechnik

Internationale  Zahlungen
Kto. 1510304 BLZ 50570024, Inhaber  J. Novak
de54505700240151030400 BIC deutdedb538
Öffnungszeiten: 
Mo.-Fr. 14.00-18.30 Uhr 
Tel. Hotline Mo.-Fr. 10.00-18.30 Uhr
Sie finden uns hier: Anfahrtsbeschreibung 
<http://www.repcom.de/images/repcom/anfahrt.jpg> 	
Messenger
Yahoo
ICQ
	: bforpc
: 174290900
	MSN
Skype
	: [email protected]
: bforpc

Unsere primÀren Web Adressen  www.repcom.de <http://www.repcom.de/> 
  und   www.dataportal.de <http://www.dataportal.de/> 	

Unsere AGB's finden Sie hier 
<http://www.repcom.de/index.php?main_page=conditions>. 

Vertraulichkeitshinweis
Der Inhalt dieser E-Mail, einschliesslich etwaiger AnhÀge, ist 
vertraulich und nur fÃŒr den oben bezeichneten Adressaten bestimmt. Wenn 
Sie nicht dieser Adressat oder dessen Empfangsvertreter sein sollten, so 
beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, 
VervielfÀltigung, Weitergabe oder eines anderen Gebrauchs des Inhalts 
nicht gestattet ist und gesetzeswidrig sein kann. Bitte informieren Sie 
in diesem Fall unverzglich den Absender und vernichten Sie dieses E-Mail 
nebst AnhÀngen und aller Kopien.

	
------------------------------------------------------------------------