No. DOMDocument::validateXMLSchema() will do the validation, and it takes care of everything. Agavi doesn't parse the XSD files, and never will, so there is no way of resolving Agavi configuration directives.

I suppose you're bundling Agavi with your app; in that case, a relative filesystem path (../../blah) will work.

Alternatively, you could try using an XML catalog; I'm not sure though whether libxml uses them for XML Schema (it definitely does for DTDs). Some info can be found at http://xmlsoft.org/catalog.html.

Hope that helps,

David



On 31.01.2010, at 16:13, Yossi Ben Haim wrote:

Hello,

Im trying to import some Agavi types to my local custom xsd file by doing:

<xs:import namespace="http://agavi.org/agavi/config/global/types/ 1.0" schemaLocation="%core.agavi_dir%/config/xsd/_types.xsd" />

In my own xsd file.

However it ignores the %core.agavi_dir% directive as far as I can tell, any way to make this work?

Thank You,
Yossi.







_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Reply via email to