From: Kieran K. <kie...@ma...> - 2008-08-25 20:28:58
|
Oh, almost forgot .... also had to add a studio record that was missing from Apple's create.sql for Studio with PK #32 Just connect using derby ij and do this (or add this to the studios SQL) INSERT INTO studio VALUES (0.00,'Wonder Movies',32); Connecting using derby ij goes something like this (all one line): java -Dderby.system.home=/Users/kieran/Library/Databases/ derby-10.3.3.0/data -jar /Users/kieran/Developer/Examples/ JavaWebObjects/Databases/db-derby-10.3.3.0-bin/lib/derbyrun.jar ij > CONNECT 'jdbc:derby:movies'; > usual SQL statements .... blah blah On Aug 25, 2008, at 4:05 PM, Kieran Kelleher wrote: > Well the final thing I did after sending that email for help was to > use Wonder's DerbyPlugin upgraded to 10.3.3.0 derby jars (because > 10.3.2.1 which DerbyPlugin seems to have according to its JDBC info > plist is apparently bad buggy version and the download was not readily > available at the derby site), and then changed a copy in my home dir > of /Developer/Examples/JavaWebObjects to work with the 10.3.3.0 derby > jars and install the examples using that version ....... however there > was a few other things I did along the way before that too ........ in > brief, here is the final list of what I did to get it launching ...... > > - Copied the WO5.4 /Developer/Examples/JavaWebObjects to my home dir > - Linked the example frameworks into my workspce and fixed all the > build path garbage > - Fixed the 2 compile errors in JavaBusinessLogic so it used old WO > 5.3.3 NSMutableDictionary instead of NSMutableDictionary<Object> > - Upgraded Wonder's derby.jar and derbytools.jar to derby 10.3.3.0 > - Upgraded my local dir copy of Apple WO examples to use derby > 10.3.3.0 and installed the example databases > - I added this to Properties file > derby.system.home=/Users/kieran/Library/Databases/derby-10.3.3.0/data > - Any classpath links to any derby jar in Apple's examples were > replaced with just linking to Wonder's DerbyPlugin framework > > > Gotchas: > Apparently the derby databases are tied to the version of the derby > installation and a newer version of derby cannot connect to databases > created with older version of derby. Apparently there is an > "upgrade=true" option that can be put in the jdbc connection URL to > address this > > Regards, Kieran > > > > On Aug 25, 2008, at 3:23 PM, Mike Schrag wrote: > >>> Never mind ...... got it working :-) >> For the sake of our descendants, what did you do? >> >> ms >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |