11:43 a.m.
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
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
11:54 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen updated ARQ-153:
------------------------------
Fix Version/s: 1.0.0.Beta1
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
8:51 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-153:
-------------------------------
When this feature is implemented, it would be nice to push these settings up into common
configuration interfaces. This way, it would give the developer the ability to inject the
container configuration so that the test knows how to communicate with the test archive
deployed to the container.
For instance, consider we are testing a REST service.
@RunWith(Arquillian.class)
public class RESTEndpointTest {
@Deployment
public static Archive<?> createDeployment() { ... }
@Arquillian ContainerContext containerContext;
@Test
public void shouldRespondToRequest() {
ClientRequest request = new ClientRequest(containerContext.getApplicationUri() +
"/resource/customer/1");
ClientResponse<String> responseObj = request.get(String.class);
Assert.assertEquals(200, responseObj.getStatus());
}
}
getApplicationUri() is a convenience method which puts together:
- remoteServerAddress (from servlet protocol)
- remoteServerHttpPort (from servlet protocol)
- deploymentContextPath (from container)
to get something like http://localhost:8080/test
It's nearly impossible to write HTTP client tests (JAX-RS, Selenium, etc) in a
portable way w/o this feature.
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
12:59 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-153:
-----------------------------------
The basis for ARQ-125 should provide that. With a option to open up for Enrichers of
style:
e.g.
@ArquillianResource(MySerlvet.class)
URL myServlet;
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
6:37 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
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
7:24 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
Aslak Knutsen commented on ARQ-153:
-----------------------------------
true. one little extra detail to it..
A Protocol should be associated with Container.
So we have:
<jboss:container>
<http:protocol />
</jboss:container>
The ProtocolConfiguration is not a field on the ContainerConfiguration, but some higher
level(Configuration?) should know how to match them..
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
7:31 p.m.
New subject: [JBoss JIRA] Commented: (ARQ-153) Protocol configuration element should be separate from Container
[
https://jira.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-153:
-------------------------------
I should mention for those following this issue that this will resolve the problem of
Arquillian getting 404s when it deploys a WebArchive that isn't named test.war.
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
12:48 a.m.
New subject: [JBoss JIRA] Assigned: (ARQ-153) Protocol configuration element should be separate from Container
[
https://issues.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen reassigned ARQ-153:
---------------------------------
Assignee: Aslak Knutsen
Protocol configuration element should be separate from Container
----------------------------------------------------------------
Key: ARQ-153
URL: https://issues.jboss.org/browse/ARQ-153
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Aslak Knutsen
Assignee: 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
New subject: [JBoss JIRA] Resolved: (ARQ-153) Protocol configuration element should be separate from Container
[
https://issues.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen resolved ARQ-153.
-------------------------------
Resolution: Done
https://github.com/aslakknutsen/arquillian/tree/the_bigger_picture
Protocol configuration element should be separate from Container
----------------------------------------------------------------
Key: ARQ-153
URL: https://issues.jboss.org/browse/ARQ-153
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Aslak Knutsen
Assignee: 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:41 p.m.
New subject: [JBoss JIRA] Updated: (ARQ-153) Protocol configuration element should be separate from Container
[
https://issues.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-153:
------------------------------
Fix Version/s: 1.0.0.Alpha5
(was: 1.0.0.Beta1)
Protocol configuration element should be separate from Container
----------------------------------------------------------------
Key: ARQ-153
URL: https://issues.jboss.org/browse/ARQ-153
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha5
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 a.m.
New subject: [JBoss JIRA] Closed: (ARQ-153) Protocol configuration element should be separate from Container
[
https://issues.jboss.org/browse/ARQ-153?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-153.
-----------------------------
Protocol configuration element should be separate from Container
----------------------------------------------------------------
Key: ARQ-153
URL: https://issues.jboss.org/browse/ARQ-153
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha5
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4852
days inactive
5151
days old
arquillian-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)
-
Karel Piwko (JIRA)