geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sachin Patel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMODEVTOOLS-104) When TomcatWebContainer moved default location - plugin cannot publish projects
Date Mon, 28 Aug 2006 16:46:22 GMT
    [ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-104?page=comments#action_12431008
] 
            
Sachin Patel commented on GERONIMODEVTOOLS-104:
-----------------------------------------------

>> Could that be done with a dendency or reference definition in geronimo-web.xml? Then
plugin can use that plan if one exists. 

I'm non sure what you mean, but the geronimo-web schema provides a web container element,
and it seems that all that needs to be done is to expose this element in the UI, in both the
plan editor and in the project creation wizard.  

> 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

        

Mime
View raw message