OK, so the problem has returned and it has something to do with when I import 
the Wonder Sources into my workspace.  So, when I deleted .metadata the tests 
worked again because the Wonder sources were no longer in my workspace.

IDK, if I'm doing something wrong but I just go import -> general -> existing 
projects into workspace

Then I select the wonder directory in my Documents folder.  Eclipse 
successfully detects all the frameworks and I just add them.  Is that the wrong 
process?

Also, I get errors on some of the wonder frameworks, mostly having to do with 
HTML not being properly formatted xml i.e <BR> instead of <BR/>.  Could that be 
the issue?

Thanks again,

Johnny




On Aug 26, 2010, at 3:32 PM, Mike Schrag wrote:

> Looks reasonable ... Not sure what .metadata would impact for this issue.
> 
> Sent from my iPhone
> 
> On Aug 26, 2010, at 9:30 PM, Johnny Miller <[email protected]> wrote:
> 
>> Here is the .classpath file for the project.
>> 
>> I have not changed the classpaths since I moved the .metadata folder.  Maybe 
>> it was written over?  Does the order they are written in matter?
>> 
>> <?xml version="1.0" encoding="UTF-8"?>
>> <classpath>
>>         <classpathentry kind="src" path="Sources"/>
>>         <classpathentry kind="src" path="Tests"/>
>>         <classpathentry kind="con" path="WOFramework/ERExtensions"/>
>>         <classpathentry kind="con" path="WOFramework/ERJars"/>
>>         <classpathentry kind="con" path="WOFramework/ERPrototypes"/>
>>         <classpathentry kind="con" path="WOFramework/JavaWOExtensions"/>
>>         <classpathentry kind="con" path="WOFramework/WOOgnl"/>
>>         <classpathentry kind="con" path="WOFramework/JavaEOAccess"/>
>>         <classpathentry kind="con" path="WOFramework/JavaEOControl"/>
>>         <classpathentry kind="con" path="WOFramework/JavaFoundation"/>
>>         <classpathentry kind="con" path="WOFramework/JavaJDBCAdaptor"/>
>>         <classpathentry kind="con" path="WOFramework/JavaWebObjects"/>
>>         <classpathentry kind="con" path="WOFramework/JavaXML"/>
>>         <classpathentry kind="con" 
>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>>         <classpathentry kind="con" path="WOFramework/KMExtensions"/>
>>         <classpathentry kind="con" path="WOFramework/KMFoundation"/>
>>         <classpathentry kind="con" path="WOFramework/MySQLPlugIn"/>
>>         <classpathentry kind="lib" path="Libraries/lucene-1.4.3.jar"/>
>>         <classpathentry kind="lib" path="Libraries/jdom.jar"/>
>>         <classpathentry kind="lib" 
>> path="Libraries/mysql-connector-java-5.0.4-bin.jar"/>
>>         <classpathentry kind="output" path="bin"/>
>> </classpath>
>> 
>> 
>> 
>> 
>> On Aug 26, 2010, at 3:20 PM, Mike Schrag wrote:
>> 
>>> Not the driver, the mysql plugin. Project metadata is in .classpath and 
>>> .project. My guess is that you weren't linked to the mysqlplugin framework.
>>> 
>>> Sent from my iPhone
>>> 
>>> On Aug 26, 2010, at 9:14 PM, Johnny Miller <[email protected]> wrote:
>>> 
>>>> Thanks for the help Mike.
>>>> 
>>>> I have the mysql driver in the Libraries folder and I had added it to the 
>>>> classpath.
>>>> 
>>>> Prior to receiving your email I decided to go for the scorched Earth 
>>>> policy to fix this as it's been going on for the better part of a day.  So 
>>>> I moved my $workspace/.metadata folder to $workspace/.metadata.old
>>>> 
>>>> Then I restarted Eclipse, re-imported my projects and now it works.  Would 
>>>> you know where I could look to in my old .metadata folder to see where the 
>>>> offending bug may lie?
>>>> 
>>>> Thanks again,
>>>> 
>>>> Johnny
>>>> 
>>>> On Aug 26, 2010, at 2:59 PM, Mike Schrag wrote:
>>>> 
>>>>> It's using the default jdbc adaptor instead of your plugin. Make sure the 
>>>>> plugin for your db is in your classpath.
>>>>> 
>>>>> Sent from my iPhone
>>>>> 
>>>>> On Aug 26, 2010, at 8:01 PM, Johnny Miller <[email protected]> wrote:
>>>>> 
>>>>>> Still stuck.
>>>>>> 
>>>>>> Here is the stack trace:
>>>>>> 
>>>>>> java.lang.IllegalStateException: Adaptor 
>>>>>> com.webobjects.jdbcadaptor.jdbcadap...@35de7497 failed to provide new 
>>>>>> primary keys for entity 'HPPoster'
>>>>>>  at 
>>>>>> com.webobjects.eoaccess.EODatabaseContext.prepareForSaveWithCoordinator(EODatabaseContext.java:5713)
>>>>>>  at 
>>>>>> com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditingContext(EOObjectStoreCoordinator.java:370)
>>>>>>  at 
>>>>>> com.webobjects.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3192)
>>>>>>  at er.extensions.eof.ERXEC._saveChanges(ERXEC.java:1085)
>>>>>>  at er.extensions.eof.ERXEC.saveChanges(ERXEC.java:1007)
>>>>>> 
>>>>>> I'm noticing that 'EO_PK_TABLE' does not seem to get created.  My 
>>>>>> TestSuite class is able to successfully login to the database and call a 
>>>>>> stored function.
>>>>>> 
>>>>>> Not sure what it all means.
>>>>>> 
>>>>>> Any help would be greatly appreciated.
>>>>>> 
>>>>>> Johnny
>>>>>> 
>>>>>> 
>>>>>> Begin forwarded message:
>>>>>> 
>>>>>>> From: Johnny Miller <[email protected]>
>>>>>>> Date: August 25, 2010 5:43:10 PM HST
>>>>>>> To: WebObjects-Dev Mailing List List <[email protected]>
>>>>>>> Subject: Having Troubles with JUnit 
>>>>>>> 
>>>>>>> Out of the blue (or maybe since I updated WOLIPS?) I'm having all kinds 
>>>>>>> of issues with running my test cases on my frameworks.
>>>>>>> 
>>>>>>> I found this tidbit on the Wiki that helped (which I didn't seem to 
>>>>>>> need before): 
>>>>>>> http://wiki.objectstyle.org/confluence/display/WO/Testing-JUnit+and+TestNG
>>>>>>> 
>>>>>>> But now I'm getting an error on one of my frameworks that I'm unable to 
>>>>>>> create a primary key for the entity I'm testing (IllegalStateException 
>>>>>>> - Adaptor com.webobjects.jdbcadaptor.jdbcadap...@50152643 failed to 
>>>>>>> provide new primary keys for entity)?
>>>>>>> 
>>>>>>> The way I test my EOModels is I have a test database that I setup/tear 
>>>>>>> down every time that I run the test.  I'm able to create the tables 
>>>>>>> (using EOUtilities.rawRowsForSQL) but when I try to saveChanges on the 
>>>>>>> EO i'm creating I get the error above.
>>>>>>> 
>>>>>>> I'm using a MySQL database with the MySQL plugin framework.  Did 
>>>>>>> something change recently in WOLips that could have caused my old tests 
>>>>>>> to fail?
>>>>>>> 
>>>>>>> Thanks in advance,
>>>>>>> 
>>>>>>> Johnny Miller
>>>>>>> Kahalawai Media Corp
>>>>>>> http://www.kahalawai.com
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> Johnny Miller
>>>>>> Kahalawai Media Corp
>>>>>> http://www.kahalawai.com
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>> http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40pobox.com
>>>>>> 
>>>>>> This email sent to [email protected]
>>>> 
>>>> Johnny Miller
>>>> Kahalawai Media Corp
>>>> http://www.kahalawai.com
>>>> 
>>>> 
>>>> 
>> 
>> Johnny Miller
>> Kahalawai Media Corp
>> http://www.kahalawai.com
>> 
>> 
>> 

Johnny Miller
Kahalawai Media Corp
http://www.kahalawai.com



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to