[jboss-dev] Scanning jars for package capabilities

[David M. Lloyd]

But folks, consider this.  By doing this scanning by default, this means 
there's yet another hoop the user must jump through in order to use the 
most performant configuration (in this case, bypassing the scanning).

All that said though, I think this whole issue would become moot if we 
eliminate using the JAR streaming API from VFS.  If we instead used the 
ZipFile API exclusively, "traversing the JAR" would amount to scanning the 
keys of a HashMap, never mind all the other possible issues with streaming 
zipfiles that I've raised elsewhere.

- DML

On 06/19/2009 07:38 AM, Andrew Lee Rubinger wrote:
> These tools would need to be run upon an artifact during the project 
> build/release phase, and not by the AS build.  Else we'll be altering 
> the bits of released components and failing checksums, etc.
> 
> On 06/19/2009 07:10 AM, Ales Justin wrote:
>>>> but i guess instead of saying "EXPORT_ALL" (which triggers the
>>>> scanning of jar for packages) we could probably configure each
>>>> deployer/deployment to have this file with a set of
>>>> "includes"/"capabilities" and explicitly list the packages available?
>>> Probably we could use some MC tool to generate this for a jar file 
>>> input?
>>>
>>> Ales, is this something that could be considered for the MC tools
>>> features that you had in mind?
>>
>> I don't think we should "re-invent" this.
>>
>> This is what OSGi based import/export tools have been doing for a long
>> time now:
>> * BND - http://www.aqute.biz/Code/Bnd
>> * Bundlor - http://www.springsource.org/bundlor
>> * PAX Construct - http://www.ops4j.org/projects/pax/construct/
>>
>> And I guess we could even create a proper Maven plugin to do this for us.
>>
>> I already asked for something like this in
>> https://jira.jboss.org/jira/browse/TTALE-44
>> but I'm more keen on extending/forking previously mentioned tools.
>>
>> There was also an OSGi Tools summit, but I need to check what was
>> actually discussed there.
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>