> IMHO we should have an "EJBValidator" that, upon deploy, can get the Jar
> and apply all sorts of rules to test if it's ok.
well we need it on ejb-jar.xml the simple one (not the extensions for now)
will see
marc
>
> Something like this (in ContainerFactory.deploy):
> EJBValidator val = new EJBValidator();
> val.addValidationListener(this);
> val.validate(ejbJar);
> // This will produce a set of ValidationEvent's. The CF should track
> these, and if any harmful ones are found, then we barf
> if (validationFailed) throw new DeploymentException("Invalid EJB-jar or
> XML");
>
> The events should be printed to the log, *or*, we might want to change
> DeploymentException so that it can include a list of problems.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
