[GitHub] [shiro] aesy opened a new pull request #191: [SHIRO-627] Determine missing bean based on name rather than type

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [shiro] aesy opened a new pull request #191: [SHIRO-627] Determine missing bean based on name rather than type

GitBox
aesy opened a new pull request #191: [SHIRO-627] Determine missing bean based on name rather than type
URL: https://github.com/apache/shiro/pull/191
 
 
   Closes [SHIRO-627](https://issues.apache.org/jira/browse/SHIRO-627)

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services
Reply | Threaded
Open this post in threaded view
|

[GitHub] [shiro] bdemers commented on issue #191: [SHIRO-627] Determine missing bean based on name rather than type

GitBox
bdemers commented on issue #191: [SHIRO-627] Determine missing bean based on name rather than type
URL: https://github.com/apache/shiro/pull/191#issuecomment-577272990
 
 
   Hey @aesy!
   Sorry for the delay in getting to this.
   
   I'm not sure I fully understand the problem this is fixing.  Are you seeing issues injecting multiple realms? Or when overriding a given component?
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[hidden email]


With regards,
Apache Git Services