[
https://issues.apache.org/jira/browse/GERONIMO-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677273#action_12677273
]
David Jencks commented on GERONIMO-4554:
----------------------------------------
branches/2.1 rev 748420 implements the simplest possible (?) solution for this
by naming both the jetty and tomcat web containers "WebContainer". Further
simplification is possible but maybe not for 2.1.4.
For trunk we can think about actually setting up the config.xml overrides and
substitutions.... although I'm not sure it's essential.
> Cant deploy an ejb web service as a plugin using car-maven-plugin
> -----------------------------------------------------------------
>
> Key: GERONIMO-4554
> URL: https://issues.apache.org/jira/browse/GERONIMO-4554
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: car-maven-plugin
> Affects Versions: 2.1.3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.1.4, 2.2
>
>
> I tried to deploy an ejb web service using the car-maven-plugin. The cxf and
> axis2 ejb deployers set up the wslink gbean with a reference to the web
> container. This is set in the plan for the deployers as "WebContainer" but
> the geronimo-plugin.xml overrides this to "${webContainer}". The jetty and
> tomcat plugins use a config-substitutions entry to e.g. set
> webContainer=JettyWebContainer
> So, this all works on a server where all the plugins are installed. However
> it doesn't work when using the car-maven-plugin since the config.xml
> overrides and config-substitutions are not applied.
> We need to either make the config modifications work for the car-maven-plugin
> or make sure none of the deployers the car-maven-plugin might use depend on
> these customizations to work. For instance, we could change all the names to
> WebContainer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
