Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-153

Protocol configuration element should be separate from Container

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 1.0.0.Alpha5
    • 1.0.0.Alpha2
    • Configuration
    • None

    Description

      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.

      <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>

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users ARQ-196 Should support controlling multiple Containers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ARQ-124 Move jndi.properties out as Configuration

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ARQ-171 ServletMethodExecutor should get context path from container

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users ARQ-125 Prototype "ArquillianContext" Hook between test and the ARQ container

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users ARQ-223 Create a EJB test execution protocol

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              aslak@redhat.com Aslak Knutsen
              aslak@redhat.com Aslak Knutsen
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: