Does BPELUnit support visiting BPEL and WSDL files with annotations

[Nariman Ammar]

Hi,

I would like to annotate BPEL and WSDL files then visit annotations on elements inside those files (e.g. annotation added to a bpel variable). Does BPELUnit framework support that?

Thanks

[Antonio García Domínguez]

Hi Nariman,

Not directly, but you could approximate that with Documentation elements that had certain structure in their text. Then you could save the document and traverse it again, looking at the Documentation elements that you had. Would that work for your case?

You're welcome,

Antonio

--
Sie erhalten diese Nachricht, weil Sie in Google Groups E-Mails von der Gruppe "BPELUnit" abonniert haben.
Wenn Sie sich von dieser Gruppe abmelden und keine E-Mails mehr von dieser Gruppe erhalten möchten, senden Sie eine E-Mail an bpelunit+u...@googlegroups.com.
Weitere Optionen finden Sie unter https://groups.google.com/d/optout.

[Nariman Ammar]

Thank you. Apparently that does the job. but Im not sure I am using it correctly:

IVariable g = p.addVariable();

g.setName("g");

g.setMessageType(new QName(owlNamespace,"G"));

IDocumentation d = g.addDocumentation();

Element e = d.addDocumentationElement(new QName(plNamespace,"S"));

which produces:

  <bpel:variable name="g" messageType="mc:G" xmlns:mc="mc">

      <bpel:documentation>

        <pl:S xmlns:pl="pl"/>

      </bpel:documentation>

    </bpel:variable>

I would like to keep track of all document elements for that variable as a map from variable v to it's document element value v. If I refactor the Document interface or the Document class would that affect the functionality of the framework?

Thanks

[Antonio García Domínguez]

Hi Nariman,

That looks right to me. The problem is that Documentation and IDocumentation are automatically generated from the WS-BPEL 2.0 XML Schema files, so they would be overwritten by certain build processes. Instead, I'd advise writing a new class that builds that map.

Kind regards,

Antonio

[Daniel Lübke]

Hi,

the "generated" statement is not entirely correct. The BPEL Model is a manual developed facade around generated classes. However, introducing a map there would violate the model character. I would also opt for tracing the relationship in another class. Patches that increase model-related aspects are welcome, though.

Daniel

[Nariman Ammar]

I believe the Documentation element already provides the map that i need since it has a list of elements that I can use to keep a history of attribute, value pairs. 

So I don't think a map is needed.