Have you got my mail ?
Hans
Armin Waibel schrieb:
Hans Novak wrote:
Armin Waibel schrieb:
Think this is problem caused by xdoclet itself, because the error
starts with
error: xjavadoc.TokenMgrError:
I suppose you need a Java5/6 compatible xdoclet version (xjavadoc).
hmmm... where can i get it ?
I use under Linux the latest SUN Java SDK with eclipse and the
latest ojb_blank, nothing more ..
The xdoclet modules are included in OJB (see [db-ojb]/lib directory).
The (xdoclet,xjavadoc) issue below seems very similar to yours
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1601
You can try the link below to get a xjavadoc-1.5 snapshot (this may
solve your xjavadoc problem):
http://prdownloads.sourceforge.net/xdoclet/xjavadoc-1.5-snapshot050611.jar?download
This error always pop up when using hsql. Simply ignore it.
i use mysql - not hsql (i have try it too, but the same error)
It looks like, that the sql file will be executed on the command line
with bash interpreter (and not something like "mysql -u whatever -p
...< [sql-file]" )
Running torque/ddlutils can cause some drop-table error logs at the
first time run, when tables do not exist (running hsql with
in-memory mode this always happens).
i understand, but again, i use mysql.
There are some things i cant understand:
If i run the buildfile with target "create-db" it will try to create
the db and creates succsessfull the SQL Files - BUT forgets some XML
Files to create/change (sometimes).
I must every time run first the target "build" and then the
"create-db" - althought create-db depends on build ... !?
In other words:
if i run the target "create-db" some times, with existing xml Files,
these files will not be overwritten, only when i run the "build" target.
Ok, this ist not a big problem, but i dont know why.
hmm, sounds like an override issue. Maybe only the "build" task remove
the old files completely and replace it by new ones.
The other thing (and for me a much more problem)
the ant task forget foreign keys of the classes.
I think, there is somewehre a problem in the java File - NOT in ojb /
builder, but i dont get any error, something like "a field ist not
persistent" or similar.
My Java code is very big - i am desperating to find the error in the
code, if the ant task dont help me....
Hans
p.s. is there a chance to write in german ? (english is very hard to me)
No sweat! Schreib einfach direkt an mich.
regards
Armin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
------------------------------------------------------------------------
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.
------------------------------------------------------------------------
