[JBoss JIRA] Created: (ARQ-86) Cannot run TestNG getting started tutorial test from inside m2eclipse
by Pete Muir (JIRA)
Cannot run TestNG getting started tutorial test from inside m2eclipse
---------------------------------------------------------------------
Key: ARQ-86
URL: https://jira.jboss.org/jira/browse/ARQ-86
Project: Arquillian
Issue Type: Bug
Components: Documentation
Reporter: Pete Muir
Priority: Critical
Fix For: 1.0.0.Alpha1
Set up the project as described in the ref guide, and try to run any test
FAILED: testConvertToCelsius
java.lang.ClassCastException: java.lang.String cannot be cast to org.testng.xml.XmlInclude
at org.jboss.arquillian.testng.TestNGTestRunner.execute(TestNGTestRunner.java:70)
at org.jboss.arquillian.protocol.servlet.ServletTestRunner.doGet(ServletTestRunner.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
at java.lang.Thread.run(Thread.java:637)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (ARQ-205) Redesign packaging
by Aslak Knutsen (JIRA)
Redesign packaging
------------------
Key: ARQ-205
URL: https://jira.jboss.org/browse/ARQ-205
Project: Arquillian
Issue Type: Feature Request
Components: Packaging Enricher SPI, Test Protocol SPIs and Implementation
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Alpha3
In the current version the Packager is responsible for creating the final deployment and adding the Protocol as just another AuxiliaryArchive. The problem here is that the Packager has to know about which Protocol is running and pack differently based on it. e.g. when using a Servlet protocol it has to be a WebArchive in the deployment.
Since the protocol has the information on how it needs to package itself and where to place the auxiliary archives in relation to itself the Protocol should do the final packaging.
Remove the Packager SPI and add a new ProtocolPackager SPI on Protocol level.
Each protocol now knows how it needs to modify the Deployment to communicate with it.
--
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
14 years, 5 months
[JBoss JIRA] Created: (ARQ-170) Rename configuration property for Embedded GlassFish HTTP port
by Dan Allen (JIRA)
Rename configuration property for Embedded GlassFish HTTP port
--------------------------------------------------------------
Key: ARQ-170
URL: https://jira.jboss.org/browse/ARQ-170
Project: Arquillian
Issue Type: Bug
Components: GlassFish Containers
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
The configuration property for the Embedded GlassFish HTTP port is currently bindPort.
However, this is an incorrect name. What this value is actually configuring is the port on which the http-listener-1 runs (the HTTP port). In fact, it's the only port that can be configured in Embedded GlassFish. Therefore, the property should be renamed to httpPort to reflect the proper purpose.
change property bindPort to httpPort in GlassFishConfiguration
--
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
14 years, 5 months