What should be change? I create process with onEntryScript in Designer and same process in Eclipse. I set Drools runtime and JBPM runtime to brms-standalone-5.3.1/jboss-as/client/{drools|jbpm}. But I cannot find any differences between this "description" and source codes which was generated by designer/eclipse.

there are still:
  - same namespaces
  - eclipse do not use CDATA in <script>

By the way, I am not able to import BPMN process from eclipse to designer. (import from designer to eclipse is ok). There occurs alert "Failed to import BPMN2. Check server logs for more details." and in server.log is ERROR org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'script' not found. (inputStream://dummyUriWithValidSuffix.xml, 22, 19)

I tried verified this issue for JBDS 5.0.0v20120615-1714-H213-GA and jBPM{Core|Task} 5.3.3.Final and I can reproduce this issue. Please can you write me, where I can found this fix in Eclipse plugin?

One thing that should happen is that the eclipse process editor should create the correct namespace now (<drools:script> instead of <script>). If you create a process with onEntry/Exit actions with the newest tooling it should import in designer fine without issues.

Checked and the fix was never merged into the jbpm product branch for 5.3.1. Let me know what to do - this BZ does not have a blocker flag set.

Done - since tooling uses the runtime parser you have to build the runtime and tooling in order to test the fix. 

To test you can create a simple task with onEntry and onExist action (can be dummy). In the generated BPMN2 you should see like:


<userTask id="_4" name="User Task" >
      <extensionElements>
        <tns:onEntry-script>
          <tns:script>System.out.println("OnEntry");</tns:script>
        </tns:onEntry-script>
        <tns:onExit-script>
          <tns:script>System.out.println("OnExit");</tns:script>
        </tns:onExit-script>
      </extensionElements>
      <ioSpecification>
        <inputSet>
        </inputSet>
        <outputSet>
        </outputSet>
      </ioSpecification>
    </userTask>

-- note the <tns:script> (namespaced) script node inside <tns:onEntry-script> (same should be on onExit-script). Previously the script node was not namespaced so was just <script> ... </script>.

moving to "modified" as fix is in jbpm production 5.2.x branch now

The bug is still present - script element remains without namespace.

Tested using JBDS 5.0.1.v20121025-1751-H2-GA (obtained from http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.1.GA.soa-tooling/) and BRMS 5.3.1.BRMS-ER4. If there is already a more recent JBDS plugin version to verify against, please let me know.

Unable to verify, since I am waiting for new JBDS plugin release.

Verified that the script element is properly namespaced on BRMS 5.3.1 CR1 and JBDS 5.0.2 GA (from update site http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-tooling/).

However, the process definition created in JBDS still fails to import into Guvnor. No specific error message is written to server.log (although Guvnor says that it should have been logged). Will continue investigating with Tihomir.

Could you please upload the bpmn2 created by the Eclipse editor?

Thanks.

Created attachment 657258 [details]
BPMN2 created by JBDS

Attached BPMN2 generated by JBDS which fails to import into Guvnor.

We have found that the error is somehow related to "tns:packageName" attribute of "process" element (see below). If this attribute is manually removed, the process definition created in JBDS imports successfully into Guvnor.

<definitions ...
    xmlns:tns="http://www.jboss.org/drools">

  <process ... tns:packageName="defaultPackage">
  ...

I'm not sure it's related to the packageName attribute, but I think the namespace definition.   targetNamespace="http://www.jboss.org/drools"

if you remove the targetNamespace it imports fine.

The BPMN2 generated by eclipse already has:
xmlns:tns="http://www.jboss.org/drools"
so I think there is no need to have  targetNamespace="http://www.jboss.org/drools" as well.

I think this is a separate issue which needs its own BZ. WDYT?

Agreed, I am going to file another BZ for this issue and marking this BZ as verified on BRMS 5.3.1 CR1 and JBDS 5.0.2 GA (from update site http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-tooling/).