bpel-dev http://dev.eclipse.org/mhonarc/lists/bpel-dev/maillist.html bpel-dev en-us Tue, 24 Nov 2009 16:50:13 GMT Tue, 24 Nov 2009 16:50:13 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) bpel-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/bpel-dev/maillist.html Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01023.html From: Michael Illiger2 &lt;MILLIGER@xxxxxxxxxx&gt; Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 To: &quot;BPEL Designer project developer discussions.&quot; &lt;bpel-dev@xxxxxxxxxxx&gt; Date: Tuesday, November 24, 2009, 8:29 PM Hey Jon... On Nov 24, 2009, at 10:17 AM, Simon D Moser <SMOSER@xxxxxxxxxx> wrote: Hi Joni, In any XML document, the "context node" is the root node of the document, e.g. the <schema> element in a XML Schema (XSD), the <definition> element in a WSDL or the <process> element in a BPEL file. Now a BPEL variable points either to a XSD element, an XSD Type Definition or a WSDL message - in other words, it points only to a specific "fragment" of the referenced XML document. Thus, when you have an xpath expression, you can only access that portion (because the bpel engine only knows about the {type, element or message}, but not the "context node" of the whole document. The Xpath processor at runtime can only access that portion, thus you cannot use location paths that point outside of the "known" fragment - using a $varName notation sets up the valid context, but restricts the processing to that particular XML subtree. [whereas in "pure" Xpath, you could use a "/" notation to select the root node of the whole document etc.] HTH Mit freundlichen Grüßen / Kind regards Simon Daniel Moser Team Lead BPEL Editor - Websphere Integration Developer (WID) IBM Software Group, Application and Integration Middleware Software Business Process Solutions Development 1 Phone: +49-7031-16-4304 IBM Deutschland (Embedded image moved to file: pic17971.gif) Fax: +49-7031-16-4890 Schoenaicher Str. 220 E-Mail: smoser@xxxxxxxxxx 71032 Boeblingen Germany IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 |------------> | From: | |------------> --------------------------------------------------------------------------------------------------------------------------------------------------| |Joni Lee <webcokies@xxxxxxxxx> | --------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> --------------------------------------------------------------------------------------------------------------------------------------------------| |"BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx> | --------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> --------------------------------------------------------------------------------------------------------------------------------------------------| |11/24/2009 04:45 PM | --------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> --------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 | --------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Sent by: | |------------> --------------------------------------------------------------------------------------------------------------------------------------------------| |bpel-dev-bounces@xxxxxxxxxxx | --------------------------------------------------------------------------------------------------------------------------------------------------| Hi Michael, Thank you many times, you save me from the wrong way. Since you are a master, would you please give me a light on this following rule under 8.2.4: "When XPath 1.0 is used as an expression language in WS-BPEL there is no context node available. Therefore the legal values of the XPath Expr ( http://www.w3.org/TR/xpath#NT-Expr) production must be restricted in order to prevent access to the context node. Specifically, the "LocationPath" (http://www.w3.org/TR/xpath#NT-LocationPath) production rule of "PathExpr" (http://www.w3.org/TR/xpath#NT-PathExpr) production rule MUST NOT be used when XPath is used as an expression language." --> but why we can use: <from>$variable.part/a/b/c</from>??? What is the restriction of XPath under 8.2.4? Although I google all the time. But I haven't really understand it yet. Thank you again. and have a nice day --- On Tue, 11/24/09, Michael Illiger2 <MILLIGER@xxxxxxxxxx> wrote: From: Michael Illiger2 <MILLIGER@xxxxxxxxxx> Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx> Date: Tuesday, November 24, 2009, 8:29 PM Hey Joni, You are not on the latest version of the BPEL 2.0 spec. ( http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html) Here it says in chapter 8.4: The from-spec MUST be one the following variants: <from variable="BPELVariableName" part="NCName"?> <query queryLanguage="anyURI"?>? queryContent </query> </from> <from partnerLink="NCName" endpointReference="myRole|partnerRole" /> <from variable="BPELVariableName" property="QName" /> <from expressionLanguage="anyURI"?>expression</from> <from><literal>literal value</literal></from> <from/> _______________________________________________ bpel-dev mailing list bpel-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/bpel-dev <pic17971.gif> _______________________________________________ bpel-dev mailing list bpel-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/bpel-dev ]]> Tue, 24 Nov 2009 16:45:45 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01023.html belkoura@xxxxxxx (Amine Belkoura) Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01022.html From: Michael Illiger2 &lt;MILLIGER@xxxxxxxxxx&gt; Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 To: &quot;BPEL Designer project developer discussions.&quot; &lt;bpel-dev@xxxxxxxxxxx&gt; Date: Tuesday, November 24, 2009, 8:29 PM Hey Jon... Hi Joni, In any XML document, the "context node" is the root node of the document, e.g. the <schema> element in a XML Schema (XSD), the <definition> element in a WSDL or the <process> element in a BPEL file. Now a BPEL variable points either to a XSD element, an XSD Type Definition or a WSDL message - in other words, it points only to a specific "fragment" of the referenced XML document. Thus, when you have an xpath expression, you can only access that portion (because the bpel engine only knows about the {type, element or message}, but not the "context node" of the whole document. The Xpath processor at runtime can only access that portion, thus you cannot use location paths that point outside of the "known" fragment - using a $varName notation sets up the valid context, but restricts the processing to that particular XML subtree. [whereas in "pure" Xpath, you could use a "/" notation to select the root node of the whole document etc.] HTH Mit freundlichen Grüßen / Kind regards Simon Daniel Moser Team Lead BPEL Editor - Websphere Integration Developer (WID) IBM Software Group, Application and Integration Middleware Software Business Process Solutions Development 1 Phone: +49-7031-16-4304 IBM Deutschland (Embedded image moved to file: pic17971.gif) Fax: +49-7031-16-4890 Schoenaicher Str. 220 E-Mail: smoser@xxxxxxxxxx 71032 Boeblingen Germany IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Joni Lee <webcokies@xxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |11/24/2009 04:45 PM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Sent by: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |bpel-dev-bounces@xxxxxxxxxxx | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hi Michael, Thank you many times, you save me from the wrong way. Since you are a master, would you please give me a light on this following rule under 8.2.4: "When XPath 1.0 is used as an expression language in WS-BPEL there is no context node available. Therefore the legal values of the XPath Expr ( http://www.w3.org/TR/xpath#NT-Expr) production must be restricted in order to prevent access to the context node. Specifically, the "LocationPath" (http://www.w3.org/TR/xpath#NT-LocationPath) production rule of "PathExpr" (http://www.w3.org/TR/xpath#NT-PathExpr) production rule MUST NOT be used when XPath is used as an expression language." --> but why we can use: <from>$variable.part/a/b/c</from>??? What is the restriction of XPath under 8.2.4? Although I google all the time. But I haven't really understand it yet. Thank you again. and have a nice day --- On Tue, 11/24/09, Michael Illiger2 <MILLIGER@xxxxxxxxxx> wrote: From: Michael Illiger2 <MILLIGER@xxxxxxxxxx> Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx> Date: Tuesday, November 24, 2009, 8:29 PM Hey Joni, You are not on the latest version of the BPEL 2.0 spec. ( http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html) Here it says in chapter 8.4: The from-spec MUST be one the following variants: <from variable="BPELVariableName" part="NCName"?> <query queryLanguage="anyURI"?>? queryContent </query> </from> <from partnerLink="NCName" endpointReference="myRole|partnerRole" /> <from variable="BPELVariableName" property="QName" /> <from expressionLanguage="anyURI"?>expression</from> <from><literal>literal value</literal></from> <from/> _______________________________________________ bpel-dev mailing list bpel-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/bpel-dev

Attachment: pic17971.gif
Description: GIF image

]]> Tue, 24 Nov 2009 16:23:09 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01022.html SMOSER@xxxxxxx (Simon D Moser) Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01021.html
Hi Michael,
 
Thank you many times, you save me from the wrong way. Since you are a master, would you please give me a light on this following rule under 8.2.4:
 

"When XPath 1.0 is used as an _expression_ language in WS-BPEL there is no context node available. Therefore the legal values of the XPath Expr (http://www.w3.org/TR/xpath#NT-Expr) production must be restricted in order to prevent access to the context node.

Specifically, the "LocationPath" (http://www.w3.org/TR/xpath#NT-LocationPath) production rule of "PathExpr" (http://www.w3.org/TR/xpath#NT-PathExpr) production rule MUST NOT be used when XPath is used as an _expression_ language."
 
--> but why we can use:
<from>$variable.part/a/b/c</from>???
What is the restriction of XPath under 8.2.4? Although I google all the time. But I haven't really understand it yet.

Thank you again.
and have a nice day

--- On Tue, 11/24/09, Michael Illiger2 <MILLIGER@xxxxxxxxxx> wrote:

From: Michael Illiger2 <MILLIGER@xxxxxxxxxx>
Subject: Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0
To: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>
Date: Tuesday, November 24, 2009, 8:29 PM

Hey Joni,

You are not on the latest version of the BPEL 2.0 spec. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html)
Here it says in chapter 8.4:

The from-spec MUST be one the following variants:

<from variable="BPELVariableName" part="NCName"?>
   <query queryLanguage="anyURI"?>?
      queryContent
   </query>
</from>
<from partnerLink="NCName" endpointReference="myRole|partnerRole" />
<from variable="BPELVariableName" property="QName" />
<from expressionLanguage="anyURI"?>_expression_</from>
<from><literal>literal value</literal></from>
<from/>

]]> Tue, 24 Nov 2009 15:45:33 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01021.html webcokies@xxxxxxx (Joni Lee) Re: [bpel-dev] The design tool different from OASIS specification for BPEL2.0 http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01020.html Hey Joni, You are not on the latest version of the BPEL 2.0 spec. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html) Here it says in chapter 8.4: The from-spec MUST be one the following variants: &lt;from variable=&quot;BPELVariableName&quot; part=uot;NCName;?; n... Hey Joni,

You are not on the latest version of the BPEL 2.0 spec. (http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html)
Here it says in chapter 8.4:

The from-spec MUST be one the following variants:

<from variable="BPELVariableName" part="NCName"?>

   <query queryLanguage="anyURI"?>?

      queryContent

   </query>

</from>

<from partnerLink="NCName" endpointReference="myRole|partnerRole" />

<from variable="BPELVariableName" property="QName" />

<from expressionLanguage="anyURI"?>_expression_</from>

<from><literal>literal value</literal></from>

<from/>




That means that the following BPEL snippet is correct:

            <bpel:copy>
               <bpel:from part="parameters" variable="TravelBookingInput">
                   <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookRequest/startAirport]]></bpel:query>
               </bpel:from>
               <bpel:to part="parameters" variable="TravelBookingOutput">
                   <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookResponse/startAirport]]></bpel:query>
               </bpel:to>
           </bpel:copy>

However you can also use the $-XPath-Syntax to do the above assignment. (Use the "_expression_" option on the assignment properties page to do this)

        <bpel:copy>
               <bpel:from expressionLanguage="...">$TravelBookingInput.parameters/TravelBookRequest/startAirport</bpel:from>
               <bpel:to expressionLanguage="...">$TravelBookingOutput.parameters/TravelBookResponse/startAirport</bpel:to>
           </bpel:copy>

(Assuming "TravelBookingInput" and "TravelBookingOutput" are BPEL variables that point on WSDL messages and "parameters" is a WSDL part within those messages...)



Mit freundlichen Grüßen / Kind regards

Michael Illiger

Software Developer - BPEL Editor / WID
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions Development 1
Phone: +49-7031-16-1273  IBM Deutschland
E-Mail: milliger@xxxxxxxxxx  Schoenaicher Str. 220
 71032 Boeblingen
 Germany
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294




From: Joni Lee <webcokies@xxxxxxxxx>
To: bpel-dev@xxxxxxxxxxx
Date: 11/24/2009 12:38 AM
Subject: [bpel-dev] The design tool different from OASIS specification for        BPEL2.0
Sent by: bpel-dev-bounces@xxxxxxxxxxx




Hi,

As specified under 8.4 OASIS Specification:
http://www.oasis-open.org/apps/group_public/download.php/18714/#_Toc135660191
the from-spec MUST be one of the following variants:
<from variable="NCName" part="NCName"?/>

<from partnerLink="NCName" endpointReference="myRole|partnerRole"/>

<from variable="NCName" property="QName"/>

<from expressionLanguage="anyURI"?>_expression_</from>

<from><literal>literal value</literal></from>
--------------------------------------------------------------------------------------------------------

I've just install BPEL2.0 for Eclipse. When I make an assign of one variable (messageType.part/query) to another variable (messageType.part/query), the code are displayed in <from><query></query></from>, which are not allowed in BPEL 2.0?

It has to be like this instead: <from>$message.part/query</from>
Or am I wrong with the 2.0 specification?
----------------------------------------------------------------------------------------------------------
           <bpel:copy>
               <bpel:from part="parameters" variable="TravelBookingInput">
                   <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookRequest/startAirport]]></bpel:query>
               </bpel:from>
               <bpel:to part="parameters" variable="TravelBookingOutput">
                   <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookResponse/startAirport]]></bpel:query>
               </bpel:to>
           </bpel:copy>

_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev

]]> Tue, 24 Nov 2009 13:29:18 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01020.html MILLIGER@xxxxxxx (Michael Illiger2) [bpel-dev] The design tool different from OASIS specification for BPEL2.0 http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01019.html Hi,As specified under 8.4 OASIS Specification:http://www.oasis-open.org/apps/group_public/download.php/18714/#_Toc135660191the from-spec MUST be one of the following variants: &lt;from variable="NCName" part="NCName"?/&gt;&lt;from partnerLink="NCName" endpointRefer... Hi,

As specified under 8.4 OASIS Specification:
http://www.oasis-open.org/apps/group_public/download.php/18714/#_Toc135660191
the from-spec MUST be one of the following variants: 
<from variable="NCName" part="NCName"?/>

<from partnerLink="NCName" endpointReference="myRole|partnerRole"/>

<from variable="NCName" property="QName"/>

<from expressionLanguage="anyURI"?>_expression_</from>

<from><literal>literal value</literal></from>
--------------------------------------------------------------------------------------------------------

I've just install BPEL2.0 for Eclipse. When I make an assign of one variable (messageType.part/query) to another variable (messageType.part/query), the code are displayed in <from><query></query></from>, which are not allowed in BPEL 2.0?

It has to be like this instead: <from>$message.part/query</from>
Or am I wrong with the 2.0 specification?
----------------------------------------------------------------------------------------------------------
            <bpel:copy>
                <bpel:from part="parameters" variable="TravelBookingInput">
                    <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookRequest/startAirport]]></bpel:query>
                </bpel:from>
                <bpel:to part="parameters" variable="TravelBookingOutput">
                    <bpel:query queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[TravelBookResponse/startAirport]]></bpel:query>
                </bpel:to>
            </bpel:copy>

]]> Mon, 23 Nov 2009 23:37:56 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01019.html webcokies@xxxxxxx (Joni Lee) [bpel-dev] partnerLink extension http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01018.html Hi,&#xA0;I want to extend the &quot;PartnerLink&quot; action like in the example:&lt;bpel:partnerlinks&gt;&#xA0;&#xA0; &lt;bpel:partnerlink name=&quot;QName&quot; ext:attrName=&quot;yes|no&quot; /&gt; &lt;/bpel:partnerlinks&gt;The xml validation allows this extension (no errors or warning),&#xA0;but it is possible to integ... I want to extend the "PartnerLink" action like in the example:

<bpel:partnerlinks>
   <bpel:partnerlink name="QName" ext:attrName="yes|no" />
</bpel:partnerlinks>

The xml validation allows this extension (no errors or warning), 
but it is possible to integrate this into the design (property view) like the selection of role?
If yes, how can I do it? 

Thanks

--
Valeria Viannei
]]> Mon, 09 Nov 2009 15:40:02 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01018.html valeriaviannei@xxxxxxx (valeria) [bpel-dev] Re: Write a custom extension activity - help http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01017.html Hi!I&#39;ve followed all the steps explained in the &quot;Write a custom extension activity.pdf&quot; and I&#39;ve downloaded the source code from cvs... but in the both cases i have the following errors (see log file in attach)Can you help me? Thanks!-- Valeria Viannei Att... Hi!
I've followed all the steps explained in the "Write a custom extension activity.pdf" and I've downloaded the source code from cvs...
but in the both cases i have the following errors (see log file in attach)
Can you help me?

Thanks!

--
Valeria Viannei

Attachment: my_log.rtf
Description: RTF file

]]> Thu, 05 Nov 2009 10:40:25 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01017.html valeriaviannei@xxxxxxx (valeria) [bpel-dev] Project meta data is out of date for technology.bpel http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01016.html Michal, Simon, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release &quot;0.4.0&quot; is in the past, but the release is... Michal, Simon, Projects are required to keep meta data up to date using the MyFoundation Portal (http://portal.eclipse.org/). The following problems were found with this project's meta-data: * The date for release "0.4.0" is in the past, but the release is not marked as completed. If it is completed, it should be marked as completed; if it has been postponed, it should be given a new target date. * There is no next/future release of this project. All Eclipse projects must have a "next release" planned and scheduled. ]]> Thu, 05 Nov 2009 05:00:18 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01016.html emo@xxxxxxx (portal on behalf of emo) Re: [bpel-dev] How to change the default behavior of LeafBorder.paint() http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01015.html Hello, there needs to be some &quot;hard-coding&quot; here because you have to find out whether there are any extension point implementers. Your code looks good to me - evtl. you could put this stuff into org.eclipse.bpel.ui.extensions.BPELUIRegistry. That's where ... Hello,

there needs to be some "hard-coding" here because you have to find out whether there are any extension point implementers. Your code looks good to me  - evtl. you could put this stuff into org.eclipse.bpel.ui.extensions.BPELUIRegistry. That's where we handle all our other extension-points...
Mit freundlichen Grüßen / Kind regards

Michael Illiger

Software Developer - BPEL Editor / WID
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions Development 1
Phone: +49-7031-16-1273  IBM Deutschland
E-Mail: milliger@xxxxxxxxxx  Schoenaicher Str. 220
 71032 Boeblingen
 Germany
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294




From: zeng zhen <zengzn@xxxxxxxxx>
To: Michael Illiger2/Germany/IBM@IBMDE
Cc: "BPEL Designer project developer discussions." <bpel-dev@xxxxxxxxxxx>, bpel-dev-bounces@xxxxxxxxxxx
Date: 10/19/2009 06:02 PM
Subject: Re: [bpel-dev] How to change the default behavior of         LeafBorder.paint()




Hello, Michael,

thank you for your answer.
I still have a question about creating an extension point in bpel.ui.

I have defined an extension point with name "customvisual" in plugin.xml of bpel.ui

I have added following codes in org.eclipse.bpel.ui.editpart.border.LeafBorder to create an instance of the extension.
    protected void getExtensionLeafBorder() {
       
        instance = null;
       
        instance =  (LeafBorder) BPELUIRegistry.readCustomvisual("extension.leafborder");
        if (instance == null) {
            return ;
        }
    }

This instance is used in paint(IFigure figure, Graphics graphics, Insets insets) to adjust the visualization of the activity nodes.
My question is: is there a way to avoid modifying the source code of org.eclipse.bpel.ui.editpart.border.LeafBorder? Because the hardcoding is always bad.

thanks!

Zhen and Ting
2009/10/12 Michael Illiger2 <MILLIGER@xxxxxxxxxx>
Hello Ting,

as of today we don't have the possibility to adjust the visualization of the activity nodes using extension points.
So the answer is, yes - you would have to define an extension point in bpel.ui.

Mit freundlichen Grüßen / Kind regards

Michael Illiger

Software Developer - BPEL Editor / WID
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions Development 1
Phone: +49-7031-16-1273  IBM Deutschland
E-Mail: milliger@xxxxxxxxxx  Schoenaicher Str. 220
 71032 Boeblingen
 Germany
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294




From: ting wang <tting.wang@xxxxxxxxx>
To: bpel-dev@xxxxxxxxxxx
Cc: zhen zeng <zengzn@xxxxxxxxx>
Date: 10/12/2009 04:14 PM
Subject: [bpel-dev] How to change the default behavior of LeafBorder.paint()
Sent by: bpel-dev-bounces@xxxxxxxxxxx



Hallo,

I am trying to wirte an extension to change the default behavior of org.eclipse.bpel.ui.editparts.borders.LeafBorder, for example, the shape of the elements border. By default it is Rectangle and I want to change it into circle.

Is there an extension point, which i can use to implement it?
Or I have to define an extension point in org.eclipse.bpel.ui?

any answer is appreciate

--

Best Regards


Mit Freundlichen Grüßen

祝
    商祺

Ting Wang




"The bane of my existence is doing things
that I know the computer could do for me"
                       -- Dan Connolly_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev


]]> Tue, 20 Oct 2009 06:00:05 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01015.html MILLIGER@xxxxxxx (Michael Illiger2) Re: [bpel-dev] How to change the default behavior of LeafBorder.paint() http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01014.html Hello, Michael,thank you for your answer.I still have a question about creating an extension point in bpel.ui.I have defined an extension point with name &quot;customvisual&quot; in plugin.xml of bpel.ui I have added following codes in org.eclipse.bpel.ui.editpart.b...
thank you for your answer.
I still have a question about creating an extension point in bpel.ui.

I have defined an extension point with name "customvisual" in plugin.xml of bpel.ui

I have added following codes in org.eclipse.bpel.ui.editpart.border.LeafBorder to create an instance of the extension.
ÂÂÂ protected void getExtensionLeafBorder() {
ÂÂÂ ÂÂÂ
ÂÂÂ ÂÂÂ instance = null;
ÂÂÂ ÂÂÂ
ÂÂÂ ÂÂÂ instance =Â (LeafBorder) BPELUIRegistry.readCustomvisual("extension.leafborder");
ÂÂÂ ÂÂÂ if (instance == null) {
ÂÂÂ ÂÂÂ ÂÂÂ return ;
ÂÂÂ ÂÂÂ }
ÂÂÂ }

This instance is used in paint(IFigure figure, Graphics graphics, Insets insets) to adjust the visualization of the activity nodes.
My question is: is there a way to avoid modifying the source code of org.eclipse.bpel.ui.editpart.border.LeafBorder? Because the hardcoding is always bad.

thanks!

Zhen and Ting


2009/10/12 Michael Illiger2 <MILLIGER@xxxxxxxxxx>
Hello Ting,

as of today we don't have the possibility to adjust the visualization of the activity nodes using extension points.
So the answer is, yes - you would have to define an extension point in bpel.ui.
Mit freundlichen GrÃÃen / Kind regards

Michael Illiger

Software Developer - BPEL Editor / WID
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions Development 1
Phone: +49-7031-16-1273 ÂIBM Deutschland
E-Mail: milliger@xxxxxxxxxx ÂSchoenaicher Str. 220
Â71032 Boeblingen
ÂGermany
IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
GeschÃftsfÃhrung: Erich Baier
Sitz der Gesellschaft: BÃblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294




From: ting wang <tting.wang@xxxxxxxxx>
To: bpel-dev@xxxxxxxxxxx
Cc: zhen zeng <zengzn@xxxxxxxxx>
Date: 10/12/2009 04:14 PM
Subject: [bpel-dev] How to change the default behavior of LeafBorder.paint()
Sent by: bpel-dev-bounces@xxxxxxxxxxx




Hallo,

I am trying to wirte an extension to change the default behavior of org.eclipse.bpel.ui.editparts.borders.LeafBorder, for example, the shape of the elements border. By default it is Rectangle and I want to change it into circle.

Is there an extension point, which i can use to implement it?
Or I have to define an extension point in org.eclipse.bpel.ui?

any answer is appreciate

--

Best Regards


Mit Freundlichen GrÃÃen

ç
  åç

Ting Wang




"The bane of my existence is doing things
that I know the computer could do for me"
           Â-- Dan Connolly_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev


]]> Mon, 19 Oct 2009 16:00:52 GMT http://dev.eclipse.org/mhonarc/lists/bpel-dev/msg01014.html zengzn@xxxxxxx (zeng zhen)