[kepler-dev] What is this?

[Ilkay Altintas]

Thanks Christopher. I think that was caused by something I
changed in the web service actor. I fixed it now.

I have a question on the web service actor. (I'm asking this
question assuming that you have access to the webservice
actor code...)

As you know given some configuration parameters, the web
service actor configures itself to execute a specific WS.
I have two basic configuration parameters for this purpose:
 1. The URL for the description of the service
 2. The name of an operation specified by this url

So when the user enters a wsdl(service) URL, I update the
list of available operations for the service. And when the
user selects one of these operations, I create input and
output ports for this service. Whenever a new operation
 name is selected or a different url is entered, I delete
all the ports and apply this procedure in the attributeChanged
method.

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
renewed.

attributeChanged is probably not the best place to create ports
but I don't know anywhere else to do such a change. (Or even
GUI/icon changes that depend on the attributes.)

I solved this before by checking if the operation name or wsdl
url had really changed. But I believe it is a kind of a hack
and doesn't solve the problem. Indeed after I renewed the
actor to make the operation names choice style (selectable),
it started causing problems again.

I will be very happy if you have any ideas to help me with this.
A test workflow for this can  be found in the workflows/test
directory in the Kepler CVS main branch. (WebServiceTest.xml)

Thanks in advance,
Ilkay


> -----Original Message-----
> From: kepler-dev-admin at ecoinformatics.org
> [mailto:kepler-dev-admin at ecoinformatics.org]On Behalf Of Christopher
> Brooks
> Sent: Thursday, October 14, 2004 1:10 PM
> To: Ilkay Altintas
> Cc: Rod Spears; kepler list
> Subject: Re: [kepler-dev] What is this?
>
>
> Ilkay,
> Jython takes a few moments to handle the jar files,
>
> I suspect that something else would be causing your vergil
> process to hang.
>
> In the window where you start up, try typing Control-Break to get a
> stack trace.  We've tried hard to make sure that error messages get
> reported to either a stack trace window or worst case, stderr, but
> we've probably missed a few
>
>
> BTW - I'm not at all happy with how Jython (the Java implementation of
> Python) does this.  I think that using Jython in an applet or unsigned
> WebStart application would be difficult.   Jacl does not have this
> problem.
>
>
> _Christopher
>
> --------
>
>     Does it take some time to load because of that or require something
>     else to instantiate? Looks like my build prints
>        " [echo] java.library.path=c:/WINDOWS/system32
>          [java] *sys-package-mgr*: processing modified jar,
>     'C:\project\kepler\build\kepler-configs.jar' "
>
>     and it stops there without opening the vergil interface? This
> happens only
>     in
>     one of my windows machines.
>
>     Thanks,
>     --Ilkay
>
>     > -----Original Message-----
>     > From: kepler-dev-admin at ecoinformatics.org
>     > [mailto:kepler-dev-admin at ecoinformatics.org]On Behalf Of Christopher
>     > Brooks
>     > Sent: Thursday, October 14, 2004 7:23 AM
>     > To: Rod Spears
>     > Cc: kepler list
>     > Subject: Re: [kepler-dev] What is this?
>     >
>     >
>     > The *sys-package-mgr* lines are from the Python actor.
>     > It caches the jars.
>     > Kepler is probably instantiating the Python actor at start up.
>     > In Ptolemy II, the Python actor usually only gets instantiated when
>     > the folder in the actor library that the Python actor is in
> is opened.
>     > My guess is that this is changed in Kepler?
>     >
>     > BTW - The actor library functionality by Chad and Shawn looks very
>     > cool.  I've not had the time to thoroughly look at it, but it seems
>     > like a win.
>     >
>     > _Christopher
>     >
>     > --------
>     >
>     >     Where did this start coming from?
>     >          [java] *sys-package-mgr*: processing modified jar,
>     >     '/home/globus/ptII4.0.1/lib/kepler-configs.jar'
>     >          [java] *sys-package-mgr*: processing modified jar,
>     >     '/home/globus/ptII4.0.1/lib/kepler.jar'
>     >
>     >
>     >     Rod
>     >
>     >
>     >     _______________________________________________
>     >     kepler-dev mailing list
>     >     kepler-dev at ecoinformatics.org
>     >     http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>     > --------
>     > _______________________________________________
>     > kepler-dev mailing list
>     > kepler-dev at ecoinformatics.org
>     > http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>     >
>
>     _______________________________________________
>     kepler-dev mailing list
>     kepler-dev at ecoinformatics.org
>     http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
> --------
> _______________________________________________
> kepler-dev mailing list
> kepler-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>