Marshall Schor wrote: > Marshall Schor wrote: >> Michael Baessler wrote: >>> Thilo Goetz (JIRA) wrote: >>> >>>> CDE is unable to create PEAR descriptor as delegate >>>> --------------------------------------------------- >>>> >>>> Key: UIMA-802 >>>> URL: https://issues.apache.org/jira/browse/UIMA-802 >>>> Project: UIMA >>>> Issue Type: Improvement >>>> Components: Eclipse plugins >>>> Affects Versions: 2.2.1 >>>> Reporter: Thilo Goetz >>>> Fix For: 2.2.2 >>>> >>>> >>>> If you insert the PEAR descriptor into the XML by hand, the CDE >>>> accepts this. It seems there is some custom code in CDE that knows >>>> what kinds of descriptors can be added to a flow. This needs to be >>>> extended to include PEAR specifiers >>>> >>>> >>> Is the CDE able to handle CustomResourceSpecifiers? >>> >> No, I don't think so. But "handle" may mean 2 things. One, covered >> by this Jira, is to only allow a descriptor of this kind to be added >> to the flow. The other, not covered by any Jira, might be for >> extending the CDE so that it could create/edit a >> "CustomResourceSpecifier". > Michael - when I looked into this, I think I found that to add a Pear to > a flow, you import the <pearSpecifier> descriptor. This is different > from the CustomResourceSpecifier. Is this correct? Yes that is correct a pearSpecifier is similar to a CustomResourceSpecifier but it is a separate independent descriptor. > > I had assumed, from your question, that the CustomResourceSpecifier was > used when importing a pear, but I think this is not right. Please > confirm :-). Assuming I got that part right, does the CDE need to do > something about CustomResourceSpecifiers? Is this related to the the > Pear specifier somehow? I think the CDE should be able two handle both specifier types. For a PearSpecifiers you will ever have a specifier like:
<?xml version="1.0" encoding="UTF-8"?> <pearSpecifier xmlns="http://uima.apache.org/resourceSpecifier";> <pearPath>d:\temp\RegExAnnotator</pearPath> </pearSpecifier> containing the path to the installed PEAR. A CustomResourceSpecifier looks like: <?xml version="1.0" encoding="UTF-8" ?> <customResourceSpecifier xmlns="http://uima.apache.org/resourceSpecifier";> <resourceClassName>my.resource.implementation.class</resourceClassName> <parameters> <parameter name="firstParam" value="firstParamValue"/> <parameter name="secondParam" value="secondParamValue"/> <parameter name="classpath" value="/class/path/settings"/> </parameters> </customResourceSpecifier> -- Michael
