The conditional statement

 

#if($jca-service-selected)

 

is not there in JEMS installer for 4.0.4.GA as CachedConnectionManager was commented out by default in JBoss AS 4.0.4.GA.

http://jira.jboss.com/jira/browse/JBAS-3642

 

Now it has been added for JBoss 4.0.5.GA

 

 

 


From: Scott M Stark
Sent: Sunday, October 15, 2006 9:44 AM
To: Dimitris Andreadis
Cc: Amit Bhayani; jboss-development@lists.jboss.org; Adrian Brock; Gavin King; Alex Pinkin; Remy Maucherat; Anil Saldhana; Scott M Stark
Subject: Re: Tomcat installation of JBoss

 

This really should be set conditionally based on whether or not jca was installed. It would take a notion of template variables that allowed for conditional inclusion of features in a descriptor that depended on whether the feature was installed. In terms of a velocity template, when I went to look at the current templates/jbossweb-tomcat55.sar/META-INF/jboss-service.xml.vm, it already has this notion:

#if($jca-service-selected)
      <depends>jboss.jca:service=CachedConnectionManager</depends>
#else
      <!-- <depends>jboss.jca:service=CachedConnectionManager</depends>       -->
#end

It looks like Amit already added this.

Dimitris Andreadis wrote:

I tried the tomcat config using the 4.0.4.GA installer and the jbossjca-service.xml that contains the CachedConnectionManager is missing.

 

So I think CachedConnectionValve should be commented out in the 'tomcat' configuration.


From: Amit Bhayani
Sent: Wednesday, October 11, 2006 3:41 PM
To: jboss-development@lists.jboss.org; Adrian Brock; Dimitris Andreadis; Gavin King; Alex Pinkin
Subject: Tomcat installation of JBoss

 

This is regarding http://jira.jboss.com/jira/browse/JBAS-3242

 

JEMS Installer has option where user can select “tomcat” installation of JBoss. Since the CachedConnectionValve is enabled by default from JBoss AS 4.0.5 GA I was wondering what should we do in case user selects the “tomcat” installation as there is no connection pooling neither tx manager.

 

Thoughts?

 

Amit.