Skip to content

BPEL NCNames vs. BPELscript IDs #8

@GoogleCodeExporter

Description

@GoogleCodeExporter
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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions