[ http://issues.apache.org/jira/browse/GERONIMO-2244?page=comments#action_12424427 ] David Jencks commented on GERONIMO-2244: ----------------------------------------
I recently changed "car" to null in the abstractNameQuery you refer to in branches/1.1, which should have fixed this problem. Do you still want to add the additional xml element? > Explicit reference fail when module type is not "car" > ----------------------------------------------------- > > Key: GERONIMO-2244 > URL: http://issues.apache.org/jira/browse/GERONIMO-2244 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment, console > Affects Versions: 1.1 > Reporter: Aaron Mulder > Priority: Critical > Fix For: 1.1.x > > > Currently the <pattern> used in the naming schema includes group, artifact, > and version, but not type. In ENCConfigBuilder.buildAbstractNameQuery, the > type is hardcoded to "car". This means that if you use a naming:pattern with > an artifactId, it only works if the target module's type is actually "car". > This is not true, for example, for several module types created by the admin > console, as well as in general for user-defined modules. > The naming:pattern element should include a "type" element, and > ENCConfigBuilder (and any other necessary code) should respect it. -- 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
