[JBoss JIRA] Created: (ARQ-604) Tomcat containers does not handle multiline javaVmArguments
by Karel Piwko (JIRA)
Tomcat containers does not handle multiline javaVmArguments
-----------------------------------------------------------
Key: ARQ-604
URL: https://issues.jboss.org/browse/ARQ-604
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tomcat Containers
Affects Versions: tomcat_1.0.0.CR1
Reporter: Karel Piwko
Assignee: Juraj Huska
Fix For: tomcat_1.0.0.Final
Suppose user passes:
{code:xml}
<container qualifier="tomcat" default="true">
<configuration>
...
<property name="javaVmArguments">-Xms512m -Xmx512m -XX:MaxPermSize=512m -Dorg.jboss.resolver.warning=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dfile.encoding=UTF-8
-Djavax.servlet.request.encoding=UTF-8 </property>
...
</configuration>
</container>
{code}
Than startup of the container would fail with:
{code}
Exception in thread "main" java.lang.NoClassDefFoundError:
Caused by: java.lang.ClassNotFoundException:
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: . Program will exit.
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (ARQ-433) Add a Tomcat 7 embedded container
by Ian Brandt (JIRA)
Add a Tomcat 7 embedded container
---------------------------------
Key: ARQ-433
URL: https://issues.jboss.org/browse/ARQ-433
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Tomcat Containers
Affects Versions: 1.0.0.Alpha5
Reporter: Ian Brandt
Tomcat 7 has deprecated the {{[org.apache.catalina.startup.Embedded|http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Embedded.html]}} API as used by the {{arquillian-tomcat-embedded-6}} container implementation. The new API is {{[org.apache.catalina.startup.Tomcat|http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html]}}. That said I have no idea if the [new {{Tomcat}} API is mature or suitable|http://www.coderanch.com/t/513623/Tomcat/Tomcat-embedded-web-app...] for Arquillian at this time. Either way with Tomcat 7 implementing [Servlet 3.0's web fragments|http://java.sun.com/developer/technicalArticles/JavaEE/JavaEE6O...], which coincide nicely with Arquillian/ShrinkWrap by allowing one to package isolated parts of their production webapp configuration for select integration tests, I think it would be great if Arquillian declared Tomcat 7 as a supported container. This could be done by implementing the new API in an {{arquillian-tomcat-embedded-7}} container, forking the deprecated API from {{arquillian-tomcat-embedded-6}} to create the same, or just adding documentation that states the {{arquillian-tomcat-embedded-6}} container can and should be used for Tomcat 7 at this time.
Thoughts? I'm going to plow ahead with {{arquillian-tomcat-embedded-6}} for now. If I run into a reason to fork it or create a container around the new API I'll try my hand at a pull request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (ARQ-598) Improve Tomcat codebase
by Karel Piwko (JIRA)
Improve Tomcat codebase
-----------------------
Key: ARQ-598
URL: https://issues.jboss.org/browse/ARQ-598
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Tomcat Containers
Affects Versions: tomcat_1.0.0.CR1
Reporter: Karel Piwko
Assignee: Karel Piwko
Fix For: tomcat_1.0.0.Final
There is a lot of functionality shared between Tomcat containers. At least ProtocalMetadataParser and TomcatManager should be shared between remote and managed containers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (ARQ-438) @DeploymentName and @OperatesOnDeployment could be made typesafe
by Karel Piwko (JIRA)
@DeploymentName and @OperatesOnDeployment could be made typesafe
----------------------------------------------------------------
Key: ARQ-438
URL: https://issues.jboss.org/browse/ARQ-438
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployable Containers SPI
Affects Versions: 1.0.0.Alpha5
Reporter: Karel Piwko
Priority: Minor
Currently, multideployments are controlled by string based name, e.g.
{code}
@Deployment(name = "dep.active-1")
@TargetsContainer("container.active-1")
public static WebArchive createTestDeployment() {
return Deployments.createActiveClient();
}
@Test
@OperateOnDeployment("dep.active-1")
public void callActive1() throws Exception {
int count = incrementCache(cache);
System.out.println("Cache incremented, current count: " + count);
Assert.assertEquals(1, count);
}
{code}
Deployment.name can be switched to a meta annotation and than this functionality can be provided in a type-safe way, e.g.
{code}
@DeploymentTarget
public @interface MyExtraDeployment {}
public Test {
@Deployment
@MyExtraDeployment
@TargetsContainer("container.active-1")
public static WebArchive createTestDeployment() {
return Deployments.createActiveClient();
}
@Test
@MyExtraDeployment
public void callActive1() throws Exception {
int count = incrementCache(cache);
System.out.println("Cache incremented, current count: " + count);
Assert.assertEquals(1, count);
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months