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.
Summary: | Feature to encode and decode in a bpel mapping | ||
---|---|---|---|
Product: | soa | Reporter: | brynjargles <brynjargles> |
Component: | BPEL Mapper | Assignee: | Sergey Lunegov <slunegov> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
brynjargles
2008-07-01 09:16:46 UTC
Will look into this. 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. I think the issue #152020 is related 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. |