Hi Dennis, all:
rather than introducing new description file I like to have
service.xml insider archive file and which root element can either be
<service> or <services> , if the root element is <service> I will
create ServiceGroupDescription by giving archive name as group name
and the group only contain one service. In the other hand if the root
element is <services> ServiceGruopDescription will be created by
giving archive name as Service Group name and all the service in
service.xml will belong to that service group.
+1, but how about a slight variation: s/service.xml/services.xml/.
+1, but I'd suggest a more distinctive name - how about
service-group.xml? I think that would reduce the chance of user errors
from misreading one name as the other.
There would only be one common filename - the differentiation would
happen via the XML inside the file, which would either be <serviceGroup>
or <service>.
I'm +1 for this idea of switching based on the XML, and I like
"services.xml" as the file name.
--Glen
- Re: [Axis2] More about service groups Glen Daniels
-