[arquillian-issues] [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container

[Karel Piwko (JIRA)]

    [ https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12552793#action_12552793 ] 

Karel Piwko commented on ARQ-153:
---------------------------------

ARQ-215 implementation makes support of <xyz:protocol> in the same way as <abc:container> and <def:extension> for arquillian.xml a very small modification.

> Protocol configuration element should be separate from Container
> ----------------------------------------------------------------
>
>                 Key: ARQ-153
>                 URL: https://jira.jboss.org/browse/ARQ-153
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: Configuration
>    Affects Versions: 1.0.0.Alpha2
>            Reporter: Aslak Knutsen
>             Fix For: 1.0.0.Beta1
>
>
> A Contianer should be able to run with any of the support Protocols for communication with TestCase running inside the container. This needs to be configurable in a common way.
> Currently Servlet Protocol configuration is stuck in the specific Containers who use it, this needs to be extracted.
> e.g.
> {code:XML}
> <arquillian xmlns="http://jboss.com/arquillian"
> 		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> 		xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.remote60"
> 		xmlns:servlet="urn:arq:org.jboss.arquillian.protocol.servlet"
> 		xmlns:jmx="urn:arq:org.jboss.arquillian.protocol.jmx"
> 		xmlns:jndi="urn:arq:org.jboss.arquillian.jndi">
> 	<jboss:container id="jbossTest">
> 		<localDeploymentBindAddress>my.domain</localDeploymentBindAddress>
> 		<servlet:protocol>
> 			<remoteServerAddress>remote.server</remoteServerAddress>
> 			<remoteServerHttpPort>8181</remoteServerHttpPort>
> 		</servlet:protocol>
> 		<jndi:protocol> <!-- Is this really a Protocol in the Arquillian sense? -->
> 			<javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl>
> 			<javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial>
> 			<javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs>
> 		</jndi:protocol>
> 	</jboss:container>	
> 	<jboss:container id="jbossStage">
> 		<localDeploymentBindAddress>my.domain</localDeploymentBindAddress>
> 		<jmx:protocol>
> 			<serviceUrl>service:jmx:rmi:///jndi/rmi://localhost:1099/</serviceUrl>
> 		</jmx:protocol>
> 		<jndi:protocol>
> 			<javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl>
> 			<javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial>
> 			<javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs>
> 		</jndi:protocol>
> 	</jboss:container>	
> </arquillian>
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira