You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2022. It is now read-only.
The API I'd like to make available for DynUnit would be a sort of subset of CDI. I don't find it necessary to pull in an entire CDI implementation like Weld considering that Nucleus sort of does most of what CDI provides. Instead, I'd like to use the @Nuke annotation for specifying options for the injected Nucleus, and use @Inject on fields to be injected with components from the Nucleus. Said fields can be optionally annotated with @Named in order to specify which particular component to use if there are more than one with the same class, and that can use either just the component name or its absolute name. Then again, perhaps the @Named bit would work better using @javax.annotation.Resource since Nucleus provides a JNDI context, too.
The text was updated successfully, but these errors were encountered:
The API I'd like to make available for DynUnit would be a sort of subset of CDI. I don't find it necessary to pull in an entire CDI implementation like Weld considering that Nucleus sort of does most of what CDI provides. Instead, I'd like to use the
@Nuke
annotation for specifying options for the injected Nucleus, and use@Inject
on fields to be injected with components from the Nucleus. Said fields can be optionally annotated with@Named
in order to specify which particular component to use if there are more than one with the same class, and that can use either just the component name or its absolute name. Then again, perhaps the@Named
bit would work better using@javax.annotation.Resource
since Nucleus provides a JNDI context, too.The text was updated successfully, but these errors were encountered: