Yes, Kurt is right and I felt embarrassed... I'm didn't change the dialect in persistence.xml, which is initially for derby.
<property name="openjpa.jdbc.DBDictionary" value="mysql"/> I guess these tables needed in juddi only (not for standard uddi) like j3_publisher and so on, are built by juddi apis. And others are built by uddi apis. So when my juddi is not set properly, tables for standard uddi is also built. And that why I thought I have a good connection to MySQL, which is actually wrong. Thanks to Kurt and all of you guys! 2014-03-21 6:31 GMT+08:00 Alex O'Ree <[email protected]>: > Any updates on this? > > > On Wed, Mar 19, 2014 at 9:58 AM, Kurt Stam <[email protected]> wrote: > >> The dialect is set in the persistence.xml. >> >> On Mar 18, 2014, at 19:22, MIX <[email protected]> wrote: >> >> Thanks for you reply! >> To Alex: >> Yes I mean the MySQL database 'juddiv3', and I have tables like >> j3_address, j3_address_line,..., created automaticly by juddi. >> Here is my 'juddiv3' database in MySQL, and there is lack of >> 'j3_pulisher' table in it: >> +-------------------------------+ >> | Tables_in_juddiv3 | >> +-------------------------------+ >> | j3_address | >> | j3_address_line | >> | j3_auth_token | >> | j3_binding_category_bag | >> | j3_binding_descr | >> | j3_binding_template | >> | j3_business_category_bag | >> | j3_business_descr | >> | j3_business_entity | >> | j3_business_identifier | >> | j3_business_name | >> | j3_business_service | >> | j3_canonicalization_method | >> | j3_category_bag | >> | j3_clerk | >> | j3_client_subscriptioninfo | >> | j3_contact | >> | j3_contact_descr | >> | j3_discovery_url | >> | j3_email | >> | j3_instance_details_descr | >> | j3_instance_details_doc_descr | >> | j3_keyed_reference | >> | j3_keyed_reference_group | >> +-------------------------------+ >> >> >> To Kurt: >> I followed the user guide and change the dialect for MySQL in >> >> *context.xml* . >> I think I have a successful connection to MySQL. It seems like juddi >> didn't build all the tables needed when starting itself. >> >> >> 2014-03-19 9:34 GMT+08:00 Kurt Stam <[email protected]>: >> >>> Did you follow the instructions in chapter 4? >>> >>> >>> >>> http://juddi.apache.org/docs/3.x/userguide/html/ch04.html#_switch_to_mysql_on_tomcat_using_openjpa >>> >>> You may have forgotten to change the dialect. >>> >>> On Mar 18, 2014, at 17:21, "Alex O'Ree" <[email protected]> wrote: >>> >>> I'm assuming you meant the 'database' juddiv3. Were the tables created >>> automatically through jpa or did you create them yourself? >>> >>> >>> On Tue, Mar 18, 2014 at 11:08 AM, MIX <[email protected]> wrote: >>> >>>> Hi all, >>>> I'm trying to run juddi_v3.2 with openJPA & MySQL, I unziped the >>>> juddiv3.war in tomcat's webapps, and configed a datasource in >>>> juddiv3/META-INF/context.xml like this: >>>> >>>> <?xml version="1.0" encoding="UTF-8"?> >>>> <Context> >>>> <WatchedResource>WEB-INF/web.xml</WatchedResource> >>>> <Resource name="jdbc/JuddiDS" auth="Container" >>>> type="javax.sql.DataSource" username="juddi" password="juddi" >>>> driverClassName="com.mysql.jdbc.Driver" >>>> url="jdbc:mysql://localhost:3306/juddiv3" >>>> maxActive="8"/> >>>> </Context> >>>> >>>> juddi is granted with full privilige on a empty juddiv3 table in >>>> MySQl. I had a MySQL connector added into tomcat lib of course. >>>> And when I try to visit localhost:8080/juddiv3 I got this: >>>> >>>> <openjpa-2.2.1-r422266:1396819 fatal general error> >>>> org.apache.openjpa.persistence.PersistenceException: Table >>>> 'juddiv3.j3_publisher' doesn't exist {prepstmnt 6413608 SELECT >>>> t0.email_address, t0.is_admin, t0.is_enabled, >>>> t0.max_bindings_per_service, t0.max_businesses, >>>> t0.max_services_per_business, t0.max_tmodels, t0.publisher_name FROM >>>> j3_publisher t0 WHERE t0.authorized_name = ?} [code=1146, state=42S02] >>>> FailedObject: root [org.apache.openjpa.util.StringId] [java.lang.String] >>>> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4958) >>>> >>>> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4918) >>>> >>>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136) >>>> >>>> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:86) >>>> >>>> I check MySQL and there are tables like j3_address, j3_address_line, >>>> etc. And juddiv3.j3_publisher table wasn't there. JUDDI seems didn't build >>>> all the needed tables when starting. Am I missing something? >>>> >>>> Thanks. >>>> >>> >>> >> >
