[jboss-as7-dev] [Discuss] Making Shrinkwrap more module-classloader friendly

[David Bosschaert]

In what I'm currently working on the actual ShrinkWrap archive is 
created on the client, but Shrinkwrap still gets slightly involved on 
the test run side in that it is used to reconstitute the Archive it 
receives over the wire from the client (via JMX) using a ZipImporter.

Aslak, in what you're planning to do, ShrinkWrap would not be used 
inside the container, so that would work as well.

Aside from the actual use-case with Arquillian and AS7 (which we can 
solve in a number of ways) I am interested should the design of 
Shrinkwrap be adapted to support modular systems?

On a high level I agree with Thomas that Shrinkwrap should be usable as 
a utility class, without any fancy classloading tricks needed by the 
consumer. That would be ideal.
My Service Idea is more glued into the current SW design and would be 
relatively easy to add, but usage as a simple utility class would be 
even better...

Cheers,

David

On 10/12/2010 12:17, Aslak Knutsen wrote:
> Maven repository and dependency resolution is work in progress:
> http://github.com/kpiwko/shrinkwrap/tree/SHRINKWRAP-140
>
> -aslak-
>
> ----- "Thomas Diesler"<thomas.diesler at jboss.com>  wrote:
>
>> I take the test case can also execute this with the help of some
>> Future,
>> so deployment failures can be fed back to the initiating test case.
>>
>> The OSGiContainer interface, which also allows you to deploy archives
>>
>> from the client classpath as well as from the local mvn repository is
>>
>> currently limited to OSGi bundles only. That needs to fixed as well
>> IMHO.
>>
>> https://github.com/jbosgi/arquillian/blob/jbosgi/protocols/osgi/src/main/java/org/jboss/arquillian/osgi/OSGiContainer.java
>>
>>
>>
>> On 12/10/2010 01:05 PM, Aslak Knutsen wrote:
>>> It's the 'new' scenario that will be supported out of the Arquillian
>> box.
>>>
>>> InContainer callback to Client asking it to 'generate/deploy' a
>> Archive to Container X. ShrinkWrap is not used inside the container at
>> all.
>>>
>>> -aslak-
>>>
>>> ----- "Thomas Diesler"<thomas.diesler at jboss.com>   wrote:
>>>
>>>> Yes, this would also work. The concept is different however
>>>>
>>>> now: test case requests an archive from the client and deploys the
>>>> archive itself
>>>> new: test case requests the client to deploy an archive
>>>>
>>>> On 12/10/2010 12:15 PM, Kabir Khan wrote:
>>>>>> So the way to do that would be to register a notification
>> listener
>>>> with the MBeanServerConnection on the client side, for example
>> when
>>>> starting up the server. You could perhaps configure that with a
>> system
>>>> property or a META-INF/services service.
>>>>> And then have the notification listener in the client assemble
>>>> things with shrinkwrap and deploy those to the server
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>> --
>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>> Thomas Diesler
>>>> JBoss OSGi Lead
>>>> JBoss, a division of Red Hat
>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>> --
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thomas Diesler
>> JBoss OSGi Lead
>> JBoss, a division of Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev