[jboss-as7-dev] No validation of deployment descriptors

[Max Rydahl Andersen]

I can just put in my 5 cents:

we don't prevent deployment in tools if there are validation errors since the server or frameworks are normally more lenient.

We warn/error where we can, but does not prevent deployment.

If there are errors that prevents deployment we expect the server to report them.

i.e. example where too strict validation before deployment is if your war is saying it is 3.0 in the web.xml - if we had validated that against JBoss 5  which is reported to only support 2.5 it would not have been possible to deploy them even though it supported most web.xml v 3.0.

Its always a balance.

I would thus say the validation should be possible on both sides but the JSR88 shouldn't force validation errors to prevent deployment.

/max

On Nov 30, 2011, at 16:59, Thomas Diesler wrote:

> Folks, 
> 
> this is related to 
> 
>     [AS7-2854] JSR88 does not validate deployment descriptors
> 
> I wonder whether it is the correct approach to validate the DDs in the JSR88 layer. It seems more natural/correct to validate the DDs in the subsystem that consumes the deployment. The behaviour I would expect is that the (invalid) deployment reaches the server, fails during deploy and that the deployment failure is       communicated back to the jsr88 layer.
> 
> Thoughts?
> 
> cheers
> -thomas 
> -- 
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx 
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

/max
http://about.me/maxandersen