[
https://issues.apache.org/jira/browse/VYSPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119563#comment-13119563
]
Mike Mahoney commented on VYSPER-297:
-------------------------------------
I wanted to point out one change in the patch that isn't obvious. I modified
org.apache.vysper.xmpp.modules.core.TestUser.createForSession(). Previously it
was returning a new TestUser with a stored resource, but the entity that it
stored did not have a bound resource. This would cause problems in testing
when using the new ResourceRegistry API, since the new API requires Entities
with bound resources instead of resource name Strings as parameters.
The change required updates to some other tests as well, but everything seems
to be working now.
> Accept client suggested resource names
> --------------------------------------
>
> Key: VYSPER-297
> URL: https://issues.apache.org/jira/browse/VYSPER-297
> Project: VYSPER
> Issue Type: Task
> Components: connection handshake
> Reporter: Mike Mahoney
> Assignee: Bernd Fondermann
> Attachments: vysper-297.patch
>
>
> Modify Vysper so it will accept a client's suggested resource name at during
> resource binding. This includes performing a ResourcePrep on the suggested
> name and checking it for size (0-1023 characters). It should also limit the
> maximum number of resources that can be bound to a single bare JID.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
