Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 288935 - org.eclipse.bpel.xpath10.LiteralExpr doesn't parse the literal correctly
Summary: org.eclipse.bpel.xpath10.LiteralExpr doesn't parse the literal correctly
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BPEL (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: BPEL Runtime Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-09 08:39 EDT by bjoern.ricks CLA
Modified: 2022-10-03 11:11 EDT (History)
1 user (show)

See Also:


Attachments
Bugfix (545 bytes, patch)
2009-09-09 08:41 EDT, bjoern.ricks CLA
bbrodt: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description bjoern.ricks CLA 2009-09-09 08:39:44 EDT
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.13) Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13 XPCOMViewer/1.0a1
Build Identifier: 

The method protected String parseLiteral (String string) in org.eclipse.bpel.xpath10.LiteralExpr returns string.substring(1, string.length()-2), that is not correct. It should be string.substring(1, string.length()-1)

Reproducible: Always
Comment 1 bjoern.ricks CLA 2009-09-09 08:41:53 EDT
Created attachment 146742 [details]
Bugfix
Comment 2 Simon Moser CLA 2009-11-11 14:09:42 EST
reviewed and committed the patch
Comment 3 Robert Brodt CLA 2012-04-18 14:49:14 EDT
Comment on attachment 146742 [details]
Bugfix

Updated iplog flag for v1.0 release review.