[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-104?page=comments#action_12430971 ] Sachin Patel commented on GERONIMODEVTOOLS-104: -----------------------------------------------
Ok, so from my understanding the Eclipse plugin simply needs to provide support in the deployment plan editor as well as the new web project creation wizard for the WebContainer element. - What I don't understand is since there is a TomcatWebContainer defined, why isn't Geronimo defaulting to the first one found? Alternatively, the Eclipse WTP Server Framework allows extensiblility to the publishing processes. So you could actually extend the Geronimo publish processes by providing a publish task, that sets the appropriate WebContainer. > 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
