These packages always generate weld warnings.  Currently none of these
packages contain classes that need to be injected so they are ignored.
Also the app developer can call
CdiConfiguration.get().add("ignore.me.package")  or
CdiConfiguration.get().remove(...).

In my next pull request 0.2-SNAPSHOT, I am refactoring the List Storage of
the ignorePackages to a Set and making the add,remove support varargs.
Going try to add some unit testing in that as well.

John


On Thu, Jun 27, 2013 at 3:42 AM, Martin Grigorov
<notifications@github.com>wrote:

> In
> wicket-experimental/wicket-cdi-1.1/wicket-cdi-1.1-core/src/main/java/org/apache/wicket/cdi/CdiConfiguration.java:
>
> > +import javax.enterprise.inject.spi.CDI;
> > +import javax.inject.Inject;
> > +
> > +import org.apache.wicket.Application;
> > +import org.apache.wicket.request.cycle.RequestCycleListenerCollection;
> > +
> > +/**
> > + * Configures CDI integration
> > + *
> > + * @author igor
> > + *
> > + */
> > +@ApplicationScoped
> > +public class CdiConfiguration
> > +{
> > +	private static final String[] defaultIgnoredPackages = new String[]
>
> What is the reason to ignore these packages ? Or why *just* these
> packages ?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/apache/wicket/pull/48/files#r4910342>
> .
>