Change By: Pedro Igor (19/Feb/14 5:36 PM)
Description: Considering the following configuration, where we have a custom Partition type defined:

{code}
        IdentityConfigurationBuilder builder = new IdentityConfigurationBuilder();

        builder
            .named("default")
                .stores()
                    .file()
                        .supportType(CustomPartition.class)
                        .supportType(IdentityType.class)
                        .supportType(Relationship.class);

        DefaultPartitionManager partitionManager = new DefaultPartitionManager(builder.buildAll());

        partitionManager.add(new CustomPartition("Custom Partition"));

        assertNotNull(partitionManager.getPartition(CustomPartition.class, "Custom Partition"));
{code}

When adding a CustomPartition instance, it always fails because PicketLink does not identify a store to support the CustomPartition type. 

This only works if we provide a configuration using the base Partition type instead:

{code}
        IdentityConfigurationBuilder builder = new IdentityConfigurationBuilder();

        builder
            .named("default")
                .stores()
                    .file()
                        .supportType(Partition.class)
                        .supportType(IdentityType.class)
                        .supportType(Relationship.class);
{code}
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