Sorry, but there's no way that we can break encapsulation by exposing that field.
I'm not following your logic about why you need access to the underlying StringBuffer - it would seem that using composition would be more appropriate. Go ahead and lay out the algorithm you are thinking about using and I'll see if I can make some suggestions. I'll also mention that SimpleTextExtractionStrategy is really, really simple. It was intended to provide a very simple example of how one might write their own extraction strategy. -- View this message in context: http://itext-general.2136553.n4.nabble.com/Quickfix-Make-result-field-in-SimpleTextExtractionStrategy-accessible-tp4658394p4658401.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
