Re: ServiceGroup - service-group.xsd

[Andrew Zeneski]

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?

Andrew

On Jan 5, 2007, at 1:31 PM, David E Jones wrote:

Regardless, the code which parses this also accepts the 'service' tag and write a warning message. It appears that it works even though the XSD doesn't allow it so I think this follows the same pattern you described.

Andrew,



-David


On Jan 5, 2007, at 10:16 AM, Andrew Zeneski wrote:

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 files.

Service group model is changing. Previous:

<service-group>
        <group name="name">
                <service name="serviceToRun"/>
        </group>
</service-group>

new:

<service-group>
        <group name="name">
                <invoke name="serviceToRun"/>
        </group>
</service-group>





<service name="foo" engine="group">
        <group>
                <invoke="service1"/>
                <invoke="service2"/>
        </group>
</service>

Andrew Zeneski
[EMAIL PROTECTED]

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 to replace "service" with "invoke". In addition, the new implementation will allow embedding group definition right inside the service definition. What a pain in the rear is it to have to edit two files just to call a group of services in order. The files will remain (at least for now) with the added support to embed your group defs inside a service.

smime.p7s
Description: S/MIME cryptographic signature