[
http://jira.codehaus.org/browse/JBEHAVE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197799#action_197799
]
Mauro Talevi commented on JBEHAVE-206:
--------------------------------------
One quick workaround could be to support reading content from a file, e.g.
Examples:
/path/to/file/with/examples/table
If the content of the Examples starts with a "|" it would be understood to be
inlined, else it would be contained in the file specified by the path.
Not ideal as it becomes less visible from scenario text, but it would get
around the issue of the parsing.
> Regex overflow in using Examples table
> --------------------------------------
>
> Key: JBEHAVE-206
> URL: http://jira.codehaus.org/browse/JBEHAVE-206
> Project: JBehave
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.3, 2.3.1, 2.3.2
> Environment: Windows
> Reporter: Mauro Talevi
> Fix For: 2.4
>
>
> It's the old Windows regex issue
> (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6337993) that raises its
> head once more, this time in the examples tables. It seems to be related to
> the number of rows and how similar they are amongst each other. It also
> seems to be sensitive to the content of the first couple of columns, i.e. if
> the first and/or second column content differ the problem does not always
> manifest itself.
> Solutions: either refactor regex parsing to not use patterns such as (x|y)*
> or provide an alternative implementation or parser based on a pluggable regex
> impl, different from the JDK one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email