Hi!
I agree with Mike in this point. It is very confusing that a name can be
set for the service but has no effect.
I think this behaviour should be changed. What was the reason to ignore
the name?
Fabian
[EMAIL PROTECTED] wrote, On 16.05.2006 18:06:
I would just like to say, this seems non-intuitive.
If I have a service tag with a name attribute, I expect the name
specified in the tag to determine the name of my service, not the
arbitrary name of my archive file (which may have versioning
information attached to it).
Now, if the name attribute is optional then I could understand using
the name of the archive file in the absence of the name attribute.
My expectation is that the purpose of the services.xml file is
configuration of my services. As such, I would expect any information
in the services.xml to take precedence over arbitrary environment
features like the name of my archive file.
*
Mike McAngus*
Associate Chief Engineer, Enterprise Architecture
Wendy's International, Inc.
One Dave Thomas Boulevard
Dublin, OH 43017
614-764-6776
