[kepler-dev] What is this?
ludaesch at sdsc.edu
Fri Oct 15 15:29:44 PDT 2004
>>>>> "IA" == Ilkay Altintas <altintas at sdsc.edu> writes:
>> -----Original Message-----
>> From: Edward A. Lee [mailto:eal at eecs.berkeley.edu]
>> Sent: Friday, October 15, 2004 5:24 AM
>> To: Ilkay Altintas
>> Cc: Christopher Brooks; Rod Spears; kepler list
>> Subject: RE: [kepler-dev] What is this?
>> At 01:29 PM 10/14/2004 -0700, Ilkay Altintas wrote:
>> >The problem is, since attributeChanged is being called
>> >everytime I update the operation names, or in the constructor, etc..
>> >So when I save and reopen the test workflows, all the link to
>> >the configured actor is gone because the ports have been
>> Even if you fix this, I think that deleting ports is risky because
>> it discards user data. Perhaps a reasonable compromise would be to
>> delete a port only if the newly selected service does not require
>> a port with the same name... This way, if you switch services
>> but they have common port names, you don't lose connections...
I like the idea that updating the WSDL url (or WS operation) to
another WS/operation having some of the same ports *keeps* and reuses
those ports instead of dropping them.. if we could do that, it would
IA> Thanks for the tip... In the case of the web service actor, I
IA> believe checking the port names wouldn't solve the problem
IA> because everytime I open the workflow, the operation name is
IA> being set to empty string again and everytime I add a new
isn't that where the problem is? Why is the operation the empty
When I save an instantiated WS actor (let's say WS_blast_simple),
doesn't the saved version "remember" the WSDL URL and operation name??
IA> choice to the operation name, the attributeChanged is being
IA> called again.
IA> So I checked the url, operation name and state of the actor
IA> before the url and operation had changed. Depending on that
IA> state, I apply the changes (sometimes partially) or not. It
IA> looks like this has solved the problem for now.
IA> I was wondering if there could be a safer way of doing GUI and
IA> port updates without having to do it right when the attributes
IA> are changed. Like collecting the changes somehow and applying
IA> them at once so that the changes in the middle won't change
IA> the GUI and port configuration. Would changeRequest() be used
IA> for this purpose?
>> Edward A. Lee, Professor
>> 518 Cory Hall, UC Berkeley, Berkeley, CA 94720
>> phone: 510-642-0455, fax: 510-642-2739
>> eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal
IA> kepler-dev mailing list
IA> kepler-dev at ecoinformatics.org
More information about the Kepler-dev