[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-104?page=comments#action_12430749 ] Oleg Gusakov commented on GERONIMODEVTOOLS-104: -----------------------------------------------
As far as I understand - applications are isolated from each other because their perspective classloaders are siblings, and the parent classloader does not know about them. If this applies to gbean namespace - which by all means it should - this issue becomes a blocker. Because if I define WebContainer in EAR - nobody else can use it but EAR children. And this might be an intended application design. EAR's should be able to - in terms of Tomcat - at least define their own connectors and, probably - engines. Should it be postulated then that WebContainer, if any, is always defined server-wide? But what if somebody wants to make this container invisible for some applications? In short - if "EAR level WebContainer" is a valid structure - it may be plugin's burden - not runtime's. But we need clarification from runtime folks. > When TomcatWebContainer moved default location - plugin cannot publish > projects > ------------------------------------------------------------------------------- > > Key: GERONIMODEVTOOLS-104 > URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-104 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin > Affects Versions: 1.1.0 > Environment: IBM VM 1.5, Win2k SP4, Eclipse 3.2.0, Little-G 1.1 > Reporter: Oleg Gusakov > > I defined Tomcat engine on the application level (in > geronimo-application.xml) because I need to define a lot of virtual hosts. > When I try to deploy a project into the server - I get > org.apache.geronimo.kernel.config.InvalidConfigException: Unable to resolve > reference "Container" in gbean > default/gtest2/1.0/car?J2EEApplication=null,j2eeType=WebModule,name=default/gtest2/1.0/car > to a gbean matching the pattern [?name=TomcatWebContainer#] > caused by "org.apache.geronimo.kernel.GBeanNotFoundException: No matches for > referencePatterns: [?name=TomcatWebContainer#]" > Two problems here (or one as they have the same root cause): > - plugin should be able to present user a choice of available web containers > to deploy to > - what if I rename bean container (can I?) and it becomes > "MyTomcatContainer35" ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
