[wildfly-dev] Confusion around deployment runtime-name

[Brian Stansberry]

On 6/18/13 2:37 AM, Carlo de Wolf wrote:
> On 06/14/2013 05:48 PM, Brian Stansberry wrote:
>>>> #1 is essentially a root of BZ. Operation seek service which contain
>>>> ${name} as part of service name, while MSC has service which has the
>>>> ${runtime-name}:
>>>> >>lookup value:
>>>> jboss.deployment.subunit."jboss-as-ejb-in-ear-ear.ear"."jboss-as-ejb-in-ear-ejb.jar".component.GreeterEJB.START
>>>>
>>>> >>actual msc service:
>>>> jboss.deployment.subunit."nnn.ear"."jboss-as-ejb-in-ear-ejb.jar".component.GreeterEJB.START
>>>>
>>>> >>
>> The lookup is incorrect.
>>
> I would reckon the MSC service name is an internal detail and not an
> exposed user key, so it should be ${name} and the lookup must never user
> ${runtime-name}.
> That is how the example looks, and what I think Brian asserts as being
> incorrect. But that contradicts the #1 assertion.
> So can we come to a definitive assertion here?
>

I think I was definitive. These MSC services should be using the 
runtime-name. If some code is trying to find or depend on the MSC 
service, it should be using the runtime-name.

If this seems to somehow prevent fixing a bug, please provide some links 
to the relevant code.


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat