2 Replies Latest reply on Mar 25, 2014 5:49 AM by ghetolay

Separate client and server/container dependency

ghetolay Jan 17, 2014 10:33 AM

So on arquillian you can run test on both side server and client (using @RunAsClient).

I'm testing websocket implementations and I'm wondering if it's possible to differentiate client and server maven dependency.

Because if I add both client and server dependency I got conflict error.

I'm wondering if arquillian as 2 different classloading or if it's possible to run test inside 2 different process.

1. Re: Separate client and server/container dependency

vjuranek Jan 23, 2014 5:25 PM (in response to ghetolay)

Hi,
I currently try to solve similar problem. It seems that Arquillian doesn't support it, however, item 1/ in Karel's reply could work for you - i.e. keep only client dependency in project and server dependency add into server deployment (or put them directly to server).
HTH
Vojta
Actions
2. Re: Separate client and server/container dependency

ghetolay Mar 25, 2014 5:49 AM (in response to ghetolay)

Thks I've tried it but I can't do it cause conflict are operating directly with server container.

I'm testing websocket connection and adding a client implementation conflicts with the one include inside server container.
I would need to do the other way, add specific dependency to client side but not possible at the moment.
Actions