juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Closed: (JUDDI-309) truncation error for endPoint field
Date Sat, 14 Nov 2009 15:39:39 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kurt T Stam closed JUDDI-309.

    Resolution: Fixed

> truncation error  for endPoint field
> ------------------------------------
>                 Key: JUDDI-309
>                 URL: https://issues.apache.org/jira/browse/JUDDI-309
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>            Priority: Minor
>             Fix For: 3.0.1
> When I try to do a save_binding, I get an error returned, and the following
> message is printed on the juddi console:
> "A truncation error was encountered trying to shrink VARCHAR 'http://schemas.xmlsoap.org/soap/http'
to length 20."
> I looked at my data, and part of my binding template data is the following
> accessPoint information:
> <nspfx:accessPoint
>         useType="http://schemas.xmlsoap.org/soap/http"
>         xmlns:nspfx="urn:uddi-org:api_v3"
> >http://localhost:30080/juddiv3/services/inquiry</nspfx:accessPoint>
> I looked in the underlying Derby database, and I see that column
> 'ACCESS_POINT_TYPE' in table 'J2_BINDING_TEMPLATE' is defined as VARCHAR(20),
> so I suspect this is the column length limit that I am hitting.
> I see in http://www.uddi.org/pubs/uddi_v3.htm#_Toc85908385 that UDDI v3 seems
> to expect that the useType field will be a value like 'endPoint' or
> 'wsdlDeployment' or 'bindingTemplate' or 'hostingRedirector', so I assume
> that is why the column's length is defined to be 20?
> But I see, later in the UDDI spec (http://www.uddi.org/pubs/uddi_v3.htm#_Toc85908400)
> that there is an example with
>   useType="uddi:tempuri.org:tmodel:newprotocol"
> so it seems like it would be better if the column in the database did not
> have such a short limit by default.
> Is this something that can be configured?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message