Forrest,  Thanks for finding this problem and raising the issue.

IMO this is a critical issue that breaks backward compatibility.

I had validated that our 2.1.2 samples installed and worked in our 2.1.4 server image prior to this change. Since this change has been made this is no longer true. I suspect this will also break other component installations (such as directory) and perhaps user created components.

We need another solution that support backward compatibility.

Joe


Jarek Gawor wrote:
Please see https://issues.apache.org/jira/browse/GERONIMO-4554.

Jarek

On Wed, Mar 4, 2009 at 11:14 AM, Forrest_Xia <[email protected]> wrote:
Recently, when I am building some 2.1 branch samples plugins, I found that
built sample plugins are all not installable.
A message on admin console like this:
"A problem has occured:
org.apache.geronimo.kernel.config.LifecycleException: start of
org.apache.geronimo.samples/calculator-tomcat/2.1.3-SNAPSHOT/car failed"

An exception in stdout/stderr like this:
"Caused by:
org.apache.geronimo.kernel.config.InvalidConfigException: Unable to resolve
reference "Container" in gbean
org.apache.geronimo.samples/calculator-tomcat/2.1.3-SNAPSHOT/car?J2EEApplication=null,j2eeType=WebModule,name=org.apache.geronimo.samples/calculator-tomcat/2.1.3-SNAPSHOT
to a gbean matching the pattern [?name=WebContainer#]
       at
org.apache.geronimo.kernel.config.ConfigurationUtil.preprocessGBeanData(ConfigurationUtil.java:380)
       at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:438)
       at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:188)
       at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562)"

After some research, I found someone changed tomcat6-deployer plugin
deployment plan, changed "TomcatWebBuilder" GBean's attribute
"tomcatContainerName" value from "?name=TomcatWebContainer" to
"?name=WebContainer", why did that?

However, I think that's the reason causing the built plugins uninstallable.

Please help review and see if it is a bug before 2.1.4 release. Thanks!

Forrest

--
View this message in context: 
http://www.nabble.com/Why-change-tomcatContainerName-from-%22-name%3DTomcatWebContainer%22-to-%22-name%3DWebContainer%22-in-tomcat6-deployer-plugin-of-2.1.4-snapshot--tp22333212s134p22333212.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.




Reply via email to