This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 138685 - Feature to encode and decode in a bpel mapping
Summary: Feature to encode and decode in a bpel mapping
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Sergey Lunegov
Depends on:
Reported: 2008-07-01 09:16 UTC by brynjargles
Modified: 2011-11-30 16:20 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description brynjargles 2008-07-01 09:16:46 UTC
Currently it seems impossible to partially encode/decode using the customencoder-1.0. 


John Doe;Engineer;30
Ola Nordmann;Manager;35

mapping to

        <Name>John Doe</Name>
        <Name>Ola Nordmann</Name>

A current workaround would be to create another CA that does nothing but encoding or decoding and transfer the flat 
file to/from that CA over file or JMS.

However if the bpel mapper had encode and decode functions (probably organized in the Node category), this would be 
easy to achieve. It would be a more flexible solution than adding the ability to partially encode/decode to the 
customencoder-1.0, since you then would have to add BCs just for the sake of encoding/decoding.
Comment 1 Sergey Lunegov 2008-07-02 10:32:35 UTC
Will look into this.
Comment 2 Nikita Krjukov 2008-07-16 20:32:22 UTC
I agree, the shortage of functions is a real problem in XPath 1.0.  :-( 
For example, I can't find a function which is analog of the Java's String.indexOf()
I believe the XPath 2.0 has much more sophisticated functions. So it would be possible to do such simple encoding or
decoding with sequence of XPath functions' calls. But it isn't useful anyway because it requires repeating declaring the
same sequence each time it's necessary to do the same piece of job. Unfortunately BPEL doesn't support declaring new
XPath functions. But fortunately it doesn't prohibit it as well. 
BPEL allows writing expressions not only with the XPath. The XPath 1.0 is considered as the default expression language.
So I think any extensions can be suggested in case we use a language other then XPath (Java, for example) or at least
the XPath with some extensions. But I think we should assign the expressionLanguage (queryLanguage) attribute to inform
runtime about extensions. 
Comment 3 Nikita Krjukov 2008-12-22 15:19:33 UTC
I think the issue #152020 is related
Comment 4 brynjargles 2008-12-22 15:32:25 UTC
From an implementation point of view issue #152020 may very well be related. Still I believe that the custom encoder
editor is very good once you learn it. From a user perspective it would be nice to be able to use that same tool to
partially encode/decode using the customencoder-1.0.