[
https://issues.apache.org/jira/browse/JSPF-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved JSPF-61.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.9.7
Assignee: Stefano Bagnara (was: Norman Maurer)
I fixed this by setting the resolver in the Lookup object created instead of
changing the default resolver.
Not sure if this is enough for the user that requested this change or if we
have also to expose the Cache and the SearchPaths property in our object.
jSPF is really modular, so in the worst case an user should be able to
implement it's own extension to DNSServiceXBillImpl and use it, but if we can
accomodate flexibility without adding complexity I'm in favor of doing this.
Let's wait the user feedback, now.
> 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: Stefano Bagnara
> Fix For: 0.9.7
>
>
--
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]
