[jboss-as7-dev] [JBoss AS7 Development] - Beta1 MUST HAVE List

[David M. Lloyd]

On 03/15/2011 06:46 AM, Max Rydahl Andersen wrote:
>
> On Mar 15, 2011, at 12:22, Jason Greene wrote:
>
>> How do you define running? Do you mean what classes are visible to the application when it does a load class call or do you also include what makes up the appserver?
>>
>> The former is all EE Apis plus the vendor Apis we choose to expose. That will have to be documented.
>
> Okey - any way to get the locations of those jars programmatically somehow and not just from a html page  ?
>
>>
>> What do you want to use the module dep info for, other than debugging?
>
> I got three usecases (and they don't all map to same kind of info they need to know):
>
> 1) For debugging - thats where I want to know all the dirty details to understand what is being loaded (and preferably what is being ignored/filtered)
>
> 2) For junit test runs (i.e. not on/nor in server) - being able to have the exact same jars on the classpath would be a big plus - this would work by either having the jar list available or
> by using some simple jboss embedded/arquillian(?) boostrap once available for AS7
>
> 3) For the classpath of projects that doesn't use maven and would rather use the *actual* jars being made available from the runtime - these can just be the API's

If you just want the raw data, use the ModuleLoaderMBeans.  Have a look 
in jconsole for more information.

-- 
- DML