juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-256) We need a test for CustodyTransfer
Date Wed, 22 May 2013 02:56:21 GMT

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

Alex O'Ree commented on JUDDI-256:

I've added 6 unit tests for transfers within the same node. One issue was uncovered in the
current trunk.

[WARNING] [talledLocalContainer] Caused by: java.lang.IndexOutOfBoundsException: Index: 1,
Size: 1
[WARNING] [talledLocalContainer]        at java.util.ArrayList.RangeCheck(ArrayList.java:547)
[WARNING] [talledLocalContainer]        at java.util.ArrayList.get(ArrayList.java:322)
[WARNING] [talledLocalContainer]        at org.apache.juddi.validation.ValidateCustodyTransfer.validateTransferEntities(
[WARNING] [talledLocalContainer]        at org.apache.juddi.api.impl.UDDICustodyTransferImpl.transferEntities(UDDICustod
[WARNING] [talledLocalContainer]        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
[WARNING] [talledLocalContainer]        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Basically, I modified the key bag after the token was issued and then attempted to transfer.
> We need a test for CustodyTransfer
> ----------------------------------
>                 Key: JUDDI-256
>                 URL: https://issues.apache.org/jira/browse/JUDDI-256
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.0beta
>            Reporter: Kurt T Stam
>            Assignee: Alex O'Ree
>             Fix For: 3.2
> We have no test that exercises this API. We need one to make sure it works.
> This relies on some form of replication to work to do the actual transfer, as described
in the spec.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message