[
https://issues.apache.org/jira/browse/JUDDI-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Qualis updated JUDDI-222:
---------------------------------
Description:
Go to Consol(Beta)
Click on get_authToken. Execute process which will return the authInfo. Copy
authInfo returned
Click on save_publisher
Past the authInfo:#### in SOAP msg and complete other required attribues.
Click submit
RESULT:
Fault response returned.
SERVER LOG:
In the log there is a report of SQL error in the INSERT INTO statement
org.apache.juddi.datastore.jdbc.PublisherTable. There were extra Removed the
extra parenthesis ) in the SQL
SOLUTION:
Removed the extra parenthesis found in the INSERT statement found in class
org.apache.juddi.datastore.jdbc.PublisherTable. This to be exact
// build insertSQL
sql = new StringBuffer(150);
sql.append("INSERT INTO ").append(tablePrefix).append("PUBLISHER (");
sql.append("PUBLISHER_ID,");
sql.append("PUBLISHER_NAME,");
sql.append("EMAIL_ADDRESS,");
sql.append("IS_ADMIN, ");
sql.append("IS_ENABLED, ");
sql.append("MAX_BUSINESSES, ");
sql.append("MAX_SERVICES_PER_BUSINESS, ");
sql.append("MAX_BINDINGS_PER_SERVICE, ");
sql.append("MAX_TMODELS) ");
sql.append("VALUES (?,?,?,?,?,?,?,?,?)");
insertSQL = sql.toString();
There were about 4. Rebuilt the juddi-2-1.0rc6.jar and redeployed to server.
Restart the AS.
TEST:
I tried to save a publisher and no error returned. I checked the PUBLISHER
table and the new publisher was entered.
COMMENT:
Can this be fixed in the next release. Not sure why I was never able to get
3.0 working on Linux; so maybe this was fixed in 3.0. Thanks
was:
Go to Consol(Beta)
Click on get_authToken. Execute process which will return the authInfo. Copy
authInfo returned
Click on save_publisher
Past the authInfo:#### in SOAP msg and complete other required attribues.
Click submit
RESULT:
Fault response returned.
SERVER LOG:
In the log there is a report of SQL error in the INSERT INTO statement
org.apache.juddi.datastore.jdbc.PublisherTable. There were extra Removed the
extra parenthesis ) in the SQL
SOLUTION:
Removed the extra parenthesis found. There were about 4. Rebuilt the
juddi-2-1.0rc6.jar and redeployed to server. Restart the AS.
TEST:
I tried to save a publisher and no error returned. I checked the PUBLISHER
table and the new publisher was entered.
COMMENT:
Can this be fixed in the next release. Not sure why I was never able to get
3.0 working on Linux; so maybe this was fixed in 3.0. Thanks
> ERROR: save_publisher fail. Embedded SQL error.
> -----------------------------------------------
>
> Key: JUDDI-222
> URL: https://issues.apache.org/jira/browse/JUDDI-222
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0rc6
> Environment: Linux
> Reporter: Richard Qualis
> Assignee: Kurt T Stam
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Go to Consol(Beta)
> Click on get_authToken. Execute process which will return the authInfo. Copy
> authInfo returned
> Click on save_publisher
> Past the authInfo:#### in SOAP msg and complete other required attribues.
> Click submit
> RESULT:
> Fault response returned.
> SERVER LOG:
> In the log there is a report of SQL error in the INSERT INTO statement
> org.apache.juddi.datastore.jdbc.PublisherTable. There were extra Removed the
> extra parenthesis ) in the SQL
> SOLUTION:
> Removed the extra parenthesis found in the INSERT statement found in class
> org.apache.juddi.datastore.jdbc.PublisherTable. This to be exact
> // build insertSQL
> sql = new StringBuffer(150);
> sql.append("INSERT INTO ").append(tablePrefix).append("PUBLISHER (");
> sql.append("PUBLISHER_ID,");
> sql.append("PUBLISHER_NAME,");
> sql.append("EMAIL_ADDRESS,");
> sql.append("IS_ADMIN, ");
> sql.append("IS_ENABLED, ");
> sql.append("MAX_BUSINESSES, ");
> sql.append("MAX_SERVICES_PER_BUSINESS, ");
> sql.append("MAX_BINDINGS_PER_SERVICE, ");
> sql.append("MAX_TMODELS) ");
> sql.append("VALUES (?,?,?,?,?,?,?,?,?)");
> insertSQL = sql.toString();
> There were about 4. Rebuilt the juddi-2-1.0rc6.jar and redeployed to
> server. Restart the AS.
> TEST:
> I tried to save a publisher and no error returned. I checked the PUBLISHER
> table and the new publisher was entered.
> COMMENT:
> Can this be fixed in the next release. Not sure why I was never able to get
> 3.0 working on Linux; so maybe this was fixed in 3.0. Thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
