[ http://issues.apache.org/jira/browse/GERONIMO-1981?page=all ]
David Jencks reassigned GERONIMO-1981:
--
Assign To: Dain Sundstrom (was: Aaron Mulder)
The problem here is to get a sibling name from an abstract name. We have the
web container name, and want to create a sibling name for a new web connector.
We don't know what kind of module these are in, so I don't see how to get the
parent name for the web container. If we added a method
public abstract AbstractName createSiblingName(AbstractName
siblingAbstractName, String name, String type);
that replaced the name and type in the source name, that would be ideal. What
do you think of adding this method to Naming?
> Web Connector has GBean=(container name) in AbstractName
>
>
> Key: GERONIMO-1981
> URL: http://issues.apache.org/jira/browse/GERONIMO-1981
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: kernel
> Versions: 1.1
> Reporter: Aaron Mulder
> Assignee: Dain Sundstrom
> Priority: Blocker
> Fix For: 1.1
>
> The GBean name for the default Jetty AJP connector appears to be (forgive the
> URL encoding but this came from the console):
> geronimo%2Fjetty%2F1.1-SNAPSHOT%2Fcar%3FGBean%3DJettyWebContainer%2CServiceModule%3Dgeronimo%2Fjetty%2F1.1-SNAPSHOT%2Fcar%2Cj2eeType%3DGBean%2Cname%3DJettyAJP13Connector
> The problem is the part of the connector name that appears to say
> "GBean=JettyWebContainer"
> I believe that was introduced in an attempt to have a standard JSR-77
> component list its parent module with its parent module type, but that
> doesn't seem to make sense for parents of type "GBean". Can we remove the
> "ParentType=ParentName" block for parents of type GBean?
> If not, then we have a bug that when creating a new web connector we don't
> add the "ParentType=ParentName" block. e.g., see
> JettyManagerImpl.addConnector, which runs this:
> AbstractName name = kernel.getNaming().createChildName(containerName,
> uniqueName, NameFactory.GERONIMO_SERVICE);
> And that gets a name without the GBean=JettyWebConnector, which means even if
> the name= component is the same as an existing connector, it comes out with a
> distinct AbstractName.
--
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
