On Jan 5, 2007, at 11:49 AM, Andrew Zeneski wrote:
I didn't want to change the name, the only reason for this was the
conflict w/ the element 'service' in services.xsd. Do you know a
way to make the element in service-groups.xsd not propagate when
the xsd is included in services.xsd?
Yes
I didn't want to change the name, the only reason for this was the
conflict w/ the element 'service' in services.xsd. Do you know a way
to make the element in service-groups.xsd not propagate when the xsd
is included in services.xsd?
Regardless, the code which parses this also accepts the '
Andrew,
With this change it would be great to follow the pattern used
elsewhere so that the parsing code still accepts the old element
name, which will obviously only work for the group definitions in the
service-group file as the "service" element name would conflict in
the services XML
Service group model is changing. Previous:
new:
All files in apache-ofbiz which reference the old way will be changed
when the implementation is complete. This is a heads up for those
with custom apps, you will need
