Bug 845219 - The properties of tomcat container configuration in arquillian.xml are not parsed properly
Summary: The properties of tomcat container configuration in arquillian.xml are not pa...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Arquillian
Version: 2.0.0.GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: CR1
: 2.1.0
Assignee: Aslak Knutsen
QA Contact: Tomas Repel
URL: http://issues.jboss.org/browse/ARQ-1044
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-02 10:25 UTC by Tomas Repel
Modified: 2012-11-30 15:34 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-30 15:34:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ARQ-1044 0 Major Closed The properties of tomcat container configuration in arquillian.xml are not parsed properly 2013-07-23 11:45:10 UTC

Description Tomas Repel 2012-08-02 10:25:28 UTC
It is impossible to use tabs or newlines in arquillian.xml when defining properties for tomcat configuration. Only space (" ") can be used as delimiter.

For example, this configuration is OK:

<container qualifier="tomcat" default="true">
  <configuration>
    <property name="catalinaHome">/home/tomcat6</property>
    <property name="javaVmArguments">-Xmx1024m -XX:MaxPermSize=512</property>
  </configuration>
</container>

While this one causes failure on startup:

<container qualifier="tomcat" default="true">
  <configuration>
    <property name="catalinaHome">/home/tomcat6</property>
    <property name="javaVmArguments">
-Xmx1024m
-XX:MaxPermSize=512
    </property>
  </configuration>
</container>


Version-Release number of selected component (if applicable):

arquillian-tomcat-managed-5.5, 6, 7; 1.0.0.CR3

Comment 1 JBoss JIRA Server 2012-08-02 12:22:16 UTC
Aslak Knutsen <aslak> updated the status of jira ARQ-1044 to Resolved

Comment 2 JBoss JIRA Server 2012-08-02 12:22:16 UTC
Aslak Knutsen <aslak> made a comment on jira ARQ-1044

pushed upstream, https://github.com/arquillian/arquillian-container-tomcat/commit/710b42bb548ec3f824dc599a8811b7261c571dab

Comment 3 Karel Piwko 2012-08-03 08:40:31 UTC
We need a new Arquillian Tomcat upstream release to incorporate the fix in wfk-arquillian-bom.

Comment 6 JBoss JIRA Server 2012-09-25 12:55:20 UTC
Aslak Knutsen <aslak> updated the status of jira ARQ-1044 to Closed

Comment 7 JBoss JIRA Server 2012-09-25 12:58:24 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Reopened

Comment 8 JBoss JIRA Server 2012-09-25 12:58:24 UTC
Karel Piwko <kpiwko> made a comment on jira ARQ-1044

Reopening to assign Tomas.

Comment 9 JBoss JIRA Server 2012-09-25 12:58:36 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Resolved

Comment 12 JBoss JIRA Server 2012-11-06 17:42:09 UTC
Aslak Knutsen <aslak> made a comment on jira ARQ-1044

[~kpiwko] This should be closed, no?

Comment 13 JBoss JIRA Server 2012-11-07 16:38:57 UTC
Karel Piwko <kpiwko> updated the status of jira ARQ-1044 to Closed

Comment 14 JBoss JIRA Server 2012-11-07 16:38:57 UTC
Karel Piwko <kpiwko> made a comment on jira ARQ-1044

Closing, fixed in 1.0.0.CR4.

Comment 15 Tomas Repel 2012-11-12 13:14:49 UTC
Verified in WFK 2.1.0.CR1.

Comment 16 Karel Piwko 2012-11-30 15:34:30 UTC
Distributed as a part of WFK 2.1.0.GA release.


Note You need to log in before you can comment on or make changes to this bug.