I have thought a bit further about problem in JBEHAVE-724 and I think it
is best to silently ignore the excess columns since the log displays the
parse result anyway, if the test fails the log information are probably
enough to figure out what is actually wrong.
On 25.02.2012 09:52, Mauro Talevi wrote:
Hi Alex,
generally JBehave uses the monitor pattern providing an interface that
expresses the events you're interested in monitoring. Logging is one of
the possible implementations of this interface. We don't use static
loggers because it does not play well with DI.
In the case of the ExamplesTable though we could collect these warning
events in a list member variable and then allow the user to retrieve it.
It would seem more practical as most of the times the ExamplesTable is
accessed directly by the users in their coding of the steps.
Cheers
On 24/02/2012 22:18, Alexander Lehmann wrote:
Hi,
I have fixed JBEHAVE-724 by basically ignoring the excess columns, I
would like to add some info message when a column are ignored, but I
am at a loss how to log something in jbehave.
If that is not possible, the excess data can be ignored silently.
bye, Alexander
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
