Re: one last Eclipse mystery... can't connect to any database.
Re: one last Eclipse mystery... can't connect to any database.
- Subject: Re: one last Eclipse mystery... can't connect to any database.
- From: Chuck Hill <email@hidden>
- Date: Mon, 16 Jul 2012 13:11:28 -0700
Which version of WO is this? I don't see 600 lines in JDBCContext.
On 2012-07-16, at 1:08 PM, Pascal Robert wrote:
> When you run the app, are you seeing the properties for the database connection? That exception looks a lot like a problem with missing JDBC properties.
>
>> Ok -
>>
>> I added a model db connection than ran generate sql and get the following dump:
>>
>> java.lang.RuntimeException: Failed to generate SQL.
>> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGeneratorFactory$ReflectionSQLGenerator.generateSchemaCreationScript(EOFSQLGeneratorFactory.java:67)
>> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog.generateSql(GenerateSQLDialog.java:298)
>> at org.objectstyle.wolips.eomodeler.actions.GenerateSQLDialog$1.run(GenerateSQLDialog.java:279)
>> at java.lang.Thread.run(Thread.java:680)
>> Caused by: java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGeneratorFactory$ReflectionSQLGenerator.generateSchemaCreationScript(EOFSQLGeneratorFactory.java:65)
>> ... 3 more
>> Caused by: java.lang.NullPointerException
>> at com.webobjects.jdbcadaptor.JDBCContext._fetchJDBCInfo(JDBCContext.java:600)
>> at com.webobjects.jdbcadaptor.JDBCPlugIn.jdbcInfo(JDBCPlugIn.java:1046)
>> at com.webobjects.jdbcadaptor._MySQLPlugIn.jdbcInfo(_MySQLPlugIn.java:715)
>> at com.webobjects.jdbcadaptor.JDBCAdaptor.jdbcInfo(JDBCAdaptor.java:233)
>> at com.webobjects.jdbcadaptor.JDBCExpressionFactory.createExpression(JDBCExpressionFactory.java:26)
>> at com.webobjects.eoaccess.EOSQLExpressionFactory.expressionForString(EOSQLExpressionFactory.java:79)
>> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory._expressionForString(EOSchemaSynchronizationFactory.java:1003)
>> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.dropTableStatementsForEntityGroup(EOSchemaSynchronizationFactory.java:394)
>> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.dropTableStatementsForEntityGroups(EOSchemaSynchronizationFactory.java:525)
>> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.schemaCreationStatementsForEntities(EOSchemaSynchronizationFactory.java:882)
>> at com.webobjects.eoaccess.synchronization.EOSchemaSynchronizationFactory.schemaCreationScriptForEntities(EOSchemaSynchronizationFactory.java:685)
>> at com.webobjects.eoaccess.EOSynchronizationFactory.schemaCreationScriptForEntities(EOSynchronizationFactory.java:233)
>> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGenerator53.fixDuplicateSingleTableInheritanceDropStatements(EOFSQLGenerator53.java:430)
>> at org.objectstyle.wolips.eomodeler.core.sql.EOFSQLGenerator53.generateSchemaCreationScript(EOFSQLGenerator53.java:480)
>> ... 8 more
>>
>>
>> ?
>>
>> James
>>
>> On Mon, Jul 16, 2012 at 2:56 PM, Tim Worman <email@hidden> wrote:
>> Let's keep the discussion on list. Yes, I am using integration.
>>
>> 1. A Wonder app logs all of its model db connection properties at launch. If you still can't connect, post the logged properties to the list for your problem connection.
>> 2. Open your model in Entity Modeler, fill in your connection dictionary, and run some tests writing schema changes to the database. If it can't connect, it will tell you why.
>>
>> Good luck.
>>
>> Tim
>> UCLA GSE&IS
>>
>> On Jul 16, 2012, at 11:27 AM, James Cicenia <email@hidden> wrote:
>>
>>> Well, I used localhost and 127.0.0.1 plus remote database connections.
>>>
>>> While removing the JavaERJDBCAdaptor gets me most of the way there it does choke on finding some tables. Very strange indeed.
>>>
>>> I am using the integration branch of wonder... are you?
>>>
>>> Curious
>>> James
>>>
>>>
>>> On Mon, Jul 16, 2012 at 2:18 PM, Tim Worman <email@hidden> wrote:
>>> I also did a fresh install yesterday and haven't had any problems connecting to mysql. This doesn't sound like an eclipse or wolips problem since those aren't involved in your actual database connection.
>>>
>>> Most likely you have a overridden db connection property that is not correct in your development environment. FWIW, when I connect to local MySQL databases, I use 127.0.0.1.
>>>
>>> Tim
>>> UCLA GSE&IS
>>>
>>> On Jul 16, 2012, at 10:18 AM, George Domurot <email@hidden> wrote:
>>>
>>>> We've done several fresh installs recently, without issue. However, we did create fresh workspaces. Not sure if that matters, but it might be worth a try to create a new workspace, import, run and test.
>>>>
>>>> Also, we are using Eclipse Indigo Service Release 2 with latest WOLips.
>>>>
>>>> -G
>>>>
>>>> On Jul 16, 2012, at 9:57 AM, Pascal Robert wrote:
>>>>
>>>>>
>>>>> Le 2012-07-16 à 12:47, James Cicenia a écrit :
>>>>>
>>>>>> I can access my mysql database from command line and Navicat. My built app works on the server. I have changed workspaces. Still Eclipse won't let me connect to any mysql database be it local or remote.
>>>>>>
>>>>>> I am using the latest wolips and eclipse 3.7.2.
>>>>>>
>>>>>> I guess I will try another Golips install.
>>>>>
>>>>> I don't think it's going to change your problem. Do you have the JDBC driver in the class path?
>>>>>
>>>>>> Meanwhile, is there something to see if Eclipse is allowed to access the 3306 port?
>>>>>
>>>>> Beside having the JDBC driver is your class path, no. If port 3306 was blocked, you wouldn't be able to access it by the command line client and Navicat.
>>>>>
>>>>>> Thanks
>>>>>> James
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jul 16, 2012 at 9:38 AM, G Brown <email@hidden> wrote:
>>>>>> One thing I discovered: You should discard eclipse workspaces when things don't work. I had an eclipse workspace since the Flood (Noah's) , and in that old one some things don't work. If I create a new workspace, and add projects to the new workspace, then things work. I think it will be standard best practice for me to change workspaces with each version of eclipse, or when things don't work.
>>>>>>
>>>>>>
>>>>>> On Jul 14, 2012, at 1:43 PM, James Cicenia wrote:
>>>>>>
>>>>>>> Hello -
>>>>>>>
>>>>>>> I am having another head scratching mystery. No matter what I do, no matter the database, no matter the credentials entered and no matter whether the database is local or remote, WO won't connect to the database. I can connect to all databases using Navicat just fine. This only effects my Eclipse and not my deployed apps. Is there another obscure switch in Eclipse?
>>>>>>>
>>>>>>> Thanks
>>>>>>> James
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Webobjects-dev mailing list (email@hidden)
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>
>>>>>> This email sent to email@hidden
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list (email@hidden)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>
>>>>> This email sent to email@hidden
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list (email@hidden)
>>>> Help/Unsubscribe/Update your Subscription:
>>>>
>>>> This email sent to email@hidden
>>>
>>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/gvc/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden