> Where module_name in this would be: deployment.foo.war:main
what's :main a reference to ?
You can leave out that.
That's a "slot", one could place version there, by default it maps to
"main".
> I need to check if this actually works;
> I mean, do I have access to this module outside Grapher app.
>
> -Ales
>
>> On Mar 15, 2011, at 01:36, Ales Justin wrote:
>>
>>> This is done here:
>>> *
https://github.com/alesj/grapher
>>>
>>> "mvn clean install" will build you a grapher-web-2.0.0-SNAPSHOT.war
in dist/target/.
>>>
>>> You can have such "commands":
>>> *
http://localhost:8080/grapher-web-2.0.0-SNAPSHOT/?extension=this-module
>>> *
http://localhost:8080/grapher-web-2.0.0-SNAPSHOT/?extension=single-module...
>>>
>>> Unfortunately the layout sucks, as I'm missing the jgraph-layout lib.
>>> (which doesn't come oss, afaik)
>>> Any Swing UI help welcome -- to impl custom layout (+ algorithm).
>>>
>>> I'm yet to impl AllModules graph creator.
>>>
>>> Another thing to add is Services visualization, which should be easy to add,
>>> since you mostly need to add trivial lookup logic.
>>>
>>> -Ales
>>>
>>> On Mar 12, 2011, at 9:08 PM, Ales Justin wrote:
>>>
>>>> Hey,
>>>>
>>>> not a bad idea, and I would gladly do it.
>>>>
>>>> I'm already hacking on Modules for some other project, so I'm
quite familiar with them.
>>>>
>>>> I'll try to implement something for Beta1,
>>>> to ease user experience with the new modularized cl layer.
>>>>
>>>> It will probably be similar to what I did for MC deps, a simple .war
app,
>>>> and I'll check with HeikoB what can/should be done to integrate it
with the new console.
>>>>
>>>> -Ales
>>>>
>>>> On Mar 12, 2011, at 4:35 PM, Scott Marlow wrote:
>>>>
>>>>> Hi Ales,
>>>>>
>>>>> You weren't on IRC chat in the AS7 room but I volunteered you to
do a visualization tool for AS7 classloaders. :-) I was kidding of course, about
volunteering you but thought I would mention the idea, in case you like it. The awesome
visualization tool that you did for MC dependencies made me think of you for this idea.
I'm not sure if it is even possible or wanted. But, how do our users figure out, what
is going on in classloader land, with regard to what classes/jars are accessible to each
module or deployment (maybe both?).
>>>>>
>>>>> Maybe this is a possible google summer of code idea?
>>>>>
>>>>> ;-)
>>>>>
>>>>> Scott
>>>>
>>>
>>>
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> /max
>>
http://about.me/maxandersen
>>
>>
>>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen