[ http://issues.apache.org/jira/browse/GERONIMO-1945?page=all ]

Aaron Mulder updated GERONIMO-1945:
-----------------------------------

    Fix Version: 1.1
      Assign To: Erin Mulder

I changed the ConfigurationInfo so that it has a property childConfigurations 
that has ConfigurationInfo objects for the child/nested configurations within 
an EAR.  Right now, it only includes WARs not other types of modules, but this 
should be enough to write generic code to populate a list including children, 
and show the URLs for the child web modules.  Later when EJB JARs and RARs are 
added to the childConfigurations they should just show up in their assigned 
areas.

One note is that we don't want people to start/stop/undeploy/etc. child 
configurations -- they should do that to the EAR instead.  So there should be a 
flag set on the data passed to the JSP indicating whether a configuration was a 
child or not, and if so, no actions should be displayed for it.  Maybe if it's 
a child the action space can say "in EAR" or "in foo/bar/1.0/ear" or whatever.

> Console's web application list does not show WARs that are deployed inside 
> EARs
> -------------------------------------------------------------------------------
>
>          Key: GERONIMO-1945
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1945
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console
>     Versions: 1.0
>     Reporter: Erin Mulder
>     Assignee: Erin Mulder
>      Fix For: 1.1

>
> In the console, click on "Applications -> Web App WARs".   The resulting list 
> of web applications does not include any web application that is packaged as 
> part of an EAR.
> (The list is populated inside ConfigManagerPortlet.doView)

-- 
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

Reply via email to