We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace hard-coded list of registered LdapDicomConfigurationExtensions
LdapDicomConfigurationExtension
@ApplicationScoped public class LdapArchiveConfigurationFactory { ... private static final LdapDicomConfigurationExtension[] configExts() { return new LdapDicomConfigurationExtension[]{ new LdapAuditLoggerConfiguration(), new LdapAuditRecordRepositoryConfiguration(), new LdapImageReaderConfiguration(), new LdapImageWriterConfiguration(), new LdapArchiveConfiguration(), new LdapArchiveUIConfiguration(), newLdapHL7Configuration() }; };
by
@ApplicationScoped public class LdapArchiveConfigurationFactory { ... @Inject private Instance<LdapDicomConfigurationExtension> configExts;
So a LdapDicomConfigurationExtension can be added by declaring its implementation class as @ApplicationScoped bean, e.g.:
@ApplicationScoped
@ApplicationScoped public class LdapArchiveUIConfiguration extends LdapDicomConfigurationExtension {
or providing it by a Producer method or field, e.g.
@Produces @ApplicationScoped private static LdapAuditLoggerConfiguration ldapAuditLoggerConfiguration = new LdapAuditLoggerConfiguration();
The text was updated successfully, but these errors were encountered:
1a41580
gunterze
No branches or pull requests
Replace hard-coded list of registered
LdapDicomConfigurationExtension
sby
So a
LdapDicomConfigurationExtension
can be added by declaring its implementation class as@ApplicationScoped
bean, e.g.:or providing it by a Producer method or field, e.g.
The text was updated successfully, but these errors were encountered: