You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Tom Cunningham (JIRA)" <ju...@ws.apache.org> on 2009/04/20 16:33:47 UTC

[jira] Commented: (JUDDI-222) ERROR: save_publisher fail. Embedded SQL error.

    [ https://issues.apache.org/jira/browse/JUDDI-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700805#action_12700805 ] 

Tom Cunningham commented on JUDDI-222:
--------------------------------------

 Could you provide a screenshot and any applicable stack trace?     Which console (URL would help) are we talking about?      What file did you fix by removing the extra parenthesis?


> 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.  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.