Bug 779676 (SOA-2041) - Adding description to expression in script
Summary: Adding description to expression in script
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: SOA-2041
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.3.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-17 15:23 UTC by Toshiya Kobayashi
Modified: 2012-07-31 04:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-31 04:49:09 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 781139 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker SOA-2041 0 Minor Closed Adding description to expression in script 2012-07-31 04:49:15 UTC

Internal Links: 781139

Description Toshiya Kobayashi 2010-04-17 15:23:58 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/501573
project_key: SOA

http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html-single/JBPM_Reference_Manual/index.html#script.element

The description of "expression"

===
the beanshell script. If you don't specify variable[b] elements, you can write the expression as the content of the script element (omitting the expression element tag).
=== 

This description is a bit confusing for users who think "expression as the content of the script element" is the basic function of script element. So I'd like to add one sentence to it, though it might be verbose.

===
the beanshell script. If you don't specify variable[b] elements, you can write the expression as the content of the script element (omitting the expression element tag). If you use "expression as the content of the script element" with variable and/or expression elements, the content of the script element will be ignored.
===

Comment 1 Toshiya Kobayashi 2010-04-17 15:26:20 UTC
Source code is easier to understand :)

http://anonsvn.jboss.org/repos/jbpm/jbpm3/tags/jbpm-3.2.7.CR3/modules/core/src/main/java/org/jbpm/graph/action/Script.java

 public void read(Element scriptElement, JpdlXmlReader jpdlReader) {
   if (scriptElement.isTextOnly()) {
     expression = scriptElement.getText();
   } else {
     this.variableAccesses = new HashSet(jpdlReader.readVariableAccesses(scriptElement));
     expression = scriptElement.element("expression").getText();
   }
 }

Comment 2 David Le Sage 2011-07-18 00:34:07 UTC
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage


Comment 3 David Le Sage 2011-07-18 00:37:13 UTC
Modified paragraph and sample source code added to the document.  Thanks.

Comment 4 Martin Vecera 2011-11-15 09:02:40 UTC
I believe that Toshiya posted the source code here to demonstarte the functionality for you to provide enough information to fix the documentation.

It is not a sample code, it shows internals of SOA-P that are likely to change.

This code should not be present in the docs definitely!

Comment 5 Toshiya Kobayashi 2011-11-22 00:58:28 UTC
Aha, Martin is correct. I just pasted the source code from actual jbpm source so that we can understand how script element works.
Please remove it from the document :)


Comment 6 Len DiMaggio 2011-11-29 17:15:26 UTC
Link: Added: This issue Cloned to SOA-3638



Note You need to log in before you can comment on or make changes to this bug.