Closed GoogleCodeExporter closed 8 years ago
Original comment by pvogren@gmail.com
on 1 May 2010 at 5:30
ok. I renamed TokenFactory to TokenBuilder and greatly simplified the
interface. Now you instantiate a TokenBuilder with the token class and
sentence class and optionally the feature names for part-of-speech tags and
stems. Subsequently you call buildTokens and pass in a JCas, some text, the
token text (optional), the pos tags (optional), and the stems (optional).
An instance of TokenBuilder is provided for free if your test inherits from the
newly added Test_ImplBase (see issue #21).
Anyways, I think the resulting unit tests which now use TokenBuilder are much
cleaner and I am no longer embarrassed by this interface.
Original comment by pvogren@gmail.com
on 11 Jun 2010 at 4:07
Original issue reported on code.google.com by
pvogren@gmail.com
on 1 May 2010 at 2:54