Re: suggestion for default pipelines

2014-04-28 Thread Chen, Pei
Yes. I was thinking of the use case for example- the ytex component need SentenceDectectorA but dictionary lookup component expects SentenceDectectorB. It's probably not too common but something to consider with the cool dynamic/plugin n play pipelines idea. Sent from my iPhone > On Apr 28, 2

Re: suggestion for default pipelines

2014-04-28 Thread Richard Eckart de Castilho
At the time a factory method becomes callable, the Maven/Ivy-magic should already have taken place, no? -- Richard On 27.04.2014, at 17:52, Chen, Pei wrote: > My vote would be for the latter. Have the "Factory" create pipelines instead. > It could just be a naming thing though... > > +1 for

Re: suggestion for default pipelines

2014-04-27 Thread Chen, Pei
My vote would be for the latter. Have the "Factory" create pipelines instead. It could just be a naming thing though... +1 for building dynamic pipelines. I think this idea has been thrown around for sometime, but it hasn't been really worked on so it would be cool to see it in action. I think

Re: suggestion for default pipelines

2014-04-27 Thread Richard Eckart de Castilho
There is already code scanning for annotations in the "generate" goal of the uimafit-maven-plugin. It may not be much effort to extend that to scan for and invoke such methods. -- Richard On 27.04.2014, at 10:39, Richard Eckart de Castilho wrote: > Maybe that choice should be left to the user.

Re: suggestion for default pipelines

2014-04-27 Thread Richard Eckart de Castilho
Maybe that choice should be left to the user. Factory methods could be marked using a special Java annotation that is scanned for at build time, e.g. something along the lines of @DescriptionGenerator static AnalysisEngineDescription getSentenceDetectorAnnotator() -- Richard On 24.04.2014, at

RE: suggestion for default pipelines

2014-04-26 Thread Miller, Timothy
That requires a bit more infrastructure, but would be really cool! From: Miller, Timothy [timothy.mil...@childrens.harvard.edu] Sent: Thursday, April 24, 2014 5:48 PM To: dev@ctakes.apache.org Subject: Re: suggestion for default pipelines Any preference

Re: suggestion for default pipelines

2014-04-24 Thread Miller, Timothy
Any preference for separate factory classes: class SentenceDetectorAnnotatorFactory: static AnalysisEngineDescription getSentenceDetectorAnnotator() VS static methods added to primitive annotators: class SentenceDetector (existing) static AnalysisEngineDescription getSentenceDetectorAnnotator

Re: suggestion for default pipelines

2014-04-16 Thread Richard Eckart de Castilho
It would be nice if uimaFIT provided a Maven plugin to automatically generate descriptors for aggregates. Maybe if we come up with a convention for factories, e.g. a "class with static methods that do not take any parameters and that return descriptors", or "methods that bear a specific Java annot

Re: suggestion for default pipelines

2014-04-15 Thread Steven Bethard
+1. And note that once you have a descriptor, you can generate the XML, so we should arrange to replace the current XML descriptors with ones generated automatically from the uimaFIT code. That should reduce some synchronization problems when the Java code was changed but the XML descriptor was not

RE: suggestion for default pipelines

2014-04-15 Thread Abraham Tom
you -Original Message- From: Finan, Sean [mailto:sean.fi...@childrens.harvard.edu] Sent: Tuesday, April 15, 2014 7:05 AM To: dev@ctakes.apache.org Subject: RE: suggestion for default pipelines +1 I think that a factory is a great idea. I (personally) dislike the descriptor schema, but I

RE: suggestion for default pipelines

2014-04-15 Thread Masanz, James J.
+1 -Original Message- From: Finan, Sean [mailto:sean.fi...@childrens.harvard.edu] Sent: Tuesday, April 15, 2014 9:05 AM To: dev@ctakes.apache.org Subject: RE: suggestion for default pipelines +1 I think that a factory is a great idea. I (personally) dislike the descriptor schema, but I

RE: suggestion for default pipelines

2014-04-15 Thread Finan, Sean
+1 I think that a factory is a great idea. I (personally) dislike the descriptor schema, but I think that deprecation is the way to go until a replacement comes along. -Original Message- From: Miller, Timothy [mailto:timothy.mil...@childrens.harvard.edu] Sent: Tuesday, April 15, 201