[
https://issues.apache.org/jira/browse/JSPF-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613889#action_12613889
]
Stefano Bagnara commented on JSPF-61:
-------------------------------------
I don't like the patch you propose... in that case we can leave the code as is
and tell the user to run a Lookup.setDefaultResolver(resolver) in its own code
and jspf will use that static resolver.
Otherwise if we want to avoid static/singleton stuff then we have to avoid the
static usage of Lookup object similarly to what we do in james server
DNSServer, e.g:
Lookup l = new Lookup(namestr, type);
l.setResolver(resolver);
> Allow use of costum Resolver
> ----------------------------
>
> Key: JSPF-61
> URL: https://issues.apache.org/jira/browse/JSPF-61
> Project: jSPF
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.9b1, 0.9b2, 0.9b3, 0.9b4, 0.9.5, 0.9.6
> Reporter: Norman Maurer
> Assignee: Norman Maurer
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
