steinarb commented on issue #1500:
URL: https://github.com/apache/shiro/issues/1500#issuecomment-2151558867

   Offhand I see two ways that would work:
   
   1. Import all the packages that the INI parser might want to instantiate 
classes from into
   2. Make it possible for the class using the INI parser to send its own 
classloader to the INI parser
   
   Downside of alternative1 is potentially introducing some undesirable 
dependencies to shiro-lang (mostly theoretical when using resolution=optional)
   
   Upside of alternative 1 is that no API changes have to be made.
   
   Upside of alternative 2 is that I'm pretty sure it will work (or at least: 
can be made to work, always, by the API user, by adjusting the imports of the 
bundle of the class calling the parser)
   
   Downside of alternative 2 is that the user of the API have to be aware of 
all packages that need to be imported


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to