Indeed schemas cannot be loaded from other archives than NXCore because
the TypeService use the NXCore context to locate schema files.
I fixed this today. You should be able now to define schemas outside NXCore
Bogdan
Jean-Marc Orliaguet wrote:
Hi,
I'm not 100% how this is supposed to work, if this is a bug or not,
but how can a component register an extension if the extension refers
to a resource located outside the component's jar?
for instance:
- package-a.jar declares a service component "ResourceService" with an
extension point called "resources":
- package-b.ear registers an extension in the "resources" extension
point of the "ResourceService" by refering to a resource
("META-INF/myresource.xml") packaged in the package-b.ear file (and
not in package-a.jar).
which would be:
<extension target="package.a.ResourceService"
point="resources">
<resource>
<src>META-INF/myresource.xml</src>
</resource>
</extension>
now how can "ResourceService" get access to the resource located in
the .ear file or in any other .jar deployed? which is invisible for
the component's classloader?
for instance does the registration of xsd schemas really work when the
schema file is located in an external package (i.e. outside NXCore.jar)?
can someone register a type based on an xsd schema in nuxeo.ear for
instance and confirm that the schema really gets registered?
thanks
/JM
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
