Classes like AbstractSingletonProxyFactoryBean belong in libraries, where they make perfect sense. Client code is a different story though, and I think it's perfectly OK to use different naming scheme within a team.
AbstractSingletonProxyFactoryBean
Classes like that should be in the bin.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Classes like
AbstractSingletonProxyFactoryBeanbelong in libraries, where they make perfect sense. Client code is a different story though, and I think it's perfectly OK to use different naming scheme within a team.Classes like that should be in the bin.