This content has been marked as final.
Show 3 replies
-
1. Re: Is it possible to customize the org.jboss.arquillian.container.was.remote_8.WebSphereRemoteContainer to get ProtocolMetaData(HTTPContext info) without the admin client connecting through the SOAP
kpiwko Dec 17, 2014 3:56 AM (in response to rnarla)1 of 1 people found this helpfulHi,
not really. Unless you want to build your own container/modify current that would use different mechanism to get URL for WAS8.
Karel
-
2. Re: Is it possible to customize the org.jboss.arquillian.container.was.remote_8.WebSphereRemoteContainer to get ProtocolMetaData(HTTPContext info) without the admin client connecting through the SOAP
rnarla Dec 17, 2014 8:46 AM (in response to kpiwko)Thanks for the prompt reply. With current implementation the portocol meadata is got after the Distribution is done and application is started. If I tried to get this information beforehand from app descriptors would it be the right way to do it or is it in inaccurate way of obtaining the metadata since it is not deployed. Can you think of any other means to get this(HTTPContext) information.
thanks
Ravi
-
3. Re: Is it possible to customize the org.jboss.arquillian.container.was.remote_8.WebSphereRemoteContainer to get ProtocolMetaData(HTTPContext info) without the admin client connecting through the SOAP
gpoul Mar 6, 2015 2:31 PM (in response to rnarla)Can you maybe explain what the problem is you're trying to solve? What is your issue with the admin client connecting through the SOAP port?