[jboss-as7-dev] module usability issue? or intended?

[Jason T. Greene]

Bah this is all wrong (and inconsistent)! All Bill should have to do is 
either a) deploy security plugin deployment or b) add a new security 
extension module and reference it from the domain configuration. He 
shouldn't have to muck with the picketlink module descriptors. I'll 
create an issue for this.

On 7/6/11 9:17 AM, Brian Stansberry wrote:
> Just a guess, but a module does not export its dependencies by default.
> You have to add attribute export="true" to export the entire dependent
> module, or use child "exports" elements to export particular classes.
>
> On 7/6/11 8:53 AM, Bill Burke wrote:
>> I wanted to add a custom LoginModule.  To have the class visible, I had
>> to add my jars to the picketbox module.
>>
>> Originally, I tried the intuitive approach (well, intuitive to me), of
>> creating a new module for my custom jars, and adding a dependency to
>> these jars within the picketbox module.  This did not work.  Is it
>> supposed to?  If not, why?
>>
>> I'm just trying to understand the logic here.
>>
>>
>
>


-- 
Jason T. Greene
JBoss, a division of Red Hat