New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BPEL NCNames vs. BPELscript IDs #8

Open

GoogleCodeExporter opened this issue May 20, 2015 · 0 comments

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented May 20, 2015

What steps will reproduce the problem?
- using a 'real' NCName with points in BPELscript and translate it. (refer
to the example of issue 1)

What is the expected output? What do you see instead?
- The translated NCName should appear in the resulting BPEL code.
- mismatched input '.' expecting '{'

Solution:
- replace faulty ID handling by proper NCName support

Original issue reported on code.google.com by [email protected] on 15 Dec 2008 at 7:07

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment