Cool, pretty simple code. The defaultmodules.remote.root.url of
does not work, so did you put up
some local web server on top of a modules directory?
On 3/17/11 10:31 AM, Ales Justin wrote:
Ah, you were right Anil. :-)
My "remote" repo had the latest version, while I had old locally.
It takes a while to boot the first time, but it works. :-)
* 1st -- 18:29:34,386 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta2
"(TBD)" started in 228356ms - Started 88 of 112 services (24 services are
passive or on-demand)
* 2nd -- 18:30:03,713 INFO [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta2
"(TBD)" started in 2081ms - Started 88 of 112 services (24 services are passive
or on-demand)
Still dunno why I need logmanager locally to start with ...
> Hmm, it works with default (non RemoteModuleLoader) usage.
> I'll try the rebase, but I doubt it will change anything.
>
> On Mar 17, 2011, at 5:49 PM, Anil Saldhana wrote:
>
>> Yesterday, we replaced "jaas" with "security-domains". Pull
upstream.
>>
>> On 03/17/2011 11:40 AM, Ales Justin wrote:
>>> OK, couldn't resist playing with this last night,
>>> so I hacked a simple "remote" ModuleLoader.
>>>
>>> *
https://github.com/alesj/jboss-modules/blob/f1debb42023bc720708c53dd1801b...
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev