struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musachy Barroso" <musa...@gmail.com>
Subject Re: [VOTE] Bring Convention plugin into trunk and deprecate Zero Config
Date Tue, 15 Jul 2008 01:53:26 GMT
>
> I opened WW-2576 some time ago.
>
> After looking at the source I came to the conclusion that the convention
> plugin is designed to exclude a whole bunch of packages from classpath
> scanning. For my feeling that is not the best way to go because you can never
> be sure what is on your classpath. Worst case the application stops working
> because the admin adds some jars to the classpath of the appserver, the ear
> is exte`nded with some lib or whatever. In an enterprise environment this
> behaviour is IMHO a no-no.
>
> Anyway, I do understand that there are usecases where this approach is needed.
>
> To solve this, I thought about an option like "scanningRoot" that defaults
> to "**" (or "^(.*)$")  In my case, I would set it to something
> like "com.project.**" or "^com\.myproject\.(.*)$"
>

The jars excluded from the scan will never have actions, like
freemarker, velocity, jdk jars, etc. You can completely disable the
scanning of jar files, and the plugin will scan only the specified
packages, wouldn't that cover the use case that you described above?


>
> BTW, I added the flatLayout parameter to the table on plugin page.

nice, thanks.
musachy

-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message