[kepler-users] Problems with Actor - WebService With ComplexTypes

Luis Assunção lass at isel.ipl.pt
Fri Apr 4 07:29:38 PDT 2008


Hi Daniel

I tested with a spell checker available at
http://ws.cdyne.com/SpellChecker/check.asmx
See the kepler workflow attached.
The output works if results are simple types like strings, but I don't
understand the way to continue using the result that is a complex type (an
array of objects where each object represents the misspelled word as well un
string array with word suggestions).
I have tried with XMLdisassembler but I have an exception!
See also attached a JPG file with a screen from execution a test with a
simple application client that invoke the same Web service. 

Regards
Luis Assuncao


-----Original Message-----
From: kepler-users-bounces at ecoinformatics.org
[mailto:kepler-users-bounces at ecoinformatics.org] On Behalf Of Luis Assunção
Sent: Friday, April 04, 2008 12:06 AM
To: 'Daniel Crawl'
Cc: kepler-users at ecoinformatics.org
Subject: Re: [kepler-users] Problems with Actor - WebService With
ComplexTypes

Hi Daniel

First of all, thank for your interest in my problem, but I really believe
Kepler mainly to run workflows based on Web Services invocation. However the
web services have complex types like classes or arrays.
About the current web service, yes, unfortunately it runs on local machine
and it's impossible to reach it outside my school (because local machines
are connected to a local network with dynamic IPs from DHCP server).
But I understood that is better if the web service is public. 
I promise that I will try to test a similar web service in Java environment
and deployed on Tomcat web server. Other thing I can do is trying to find a
public web service with complex types, for instance from Google or Amazon in
order to achieve new conclusions.
However as you request see attach the WSDL file for my local ASP.NET web
service running on Windows machine (deployed in IIS).

Regards
Luis


-----Original Message-----
From: Daniel Crawl [mailto:crawl at sdsc.edu]
Sent: quinta-feira, 3 de Abril de 2008 21:36
To: Luis Assunção
Cc: kepler-users at ecoinformatics.org
Subject: Re: [kepler-users] Problems with Actor - WebService With
ComplexTypes


Hi Luis,

The web service in your workflow has a private IP address
(10.x.x.x) that I cannot reach. Does it have a public one?

Could you send me the WSDL for the web service?

Have you tested the web service with a client different
from the web service actor?

Thanks,

  --dan



Luis Assunção wrote:
> Hi Daniel
>
> After more work around I think the problem happen when the input port of
the
> Actor is a ComplexType? 
> Probably the following exception give you more exact information!
> See also the attach xml file from new workflow around the same web
service.
>
> Regards
> Luis
>
> ptolemy.kernel.util.IllegalActionException: RemoteException: Server was
> unable to process request. ---> Object reference not set to an instance of
> an object.
>   in .ComplexTypes2.WSWithComplexTypes2
> 	at org.sdm.spa.WSWithComplexTypes.fire(WSWithComplexTypes.java:394)
> 	at ptolemy.actor.AtomicActor.iterate(AtomicActor.java:398)
> 	at
>
ptolemy.actor.sched.StaticSchedulingDirector.fire(StaticSchedulingDirector.j
> ava:170)
> 	at ptolemy.actor.CompositeActor.fire(CompositeActor.java:400)
> 	at ptolemy.actor.Manager.iterate(Manager.java:688)
> 	at ptolemy.actor.Manager.execute(Manager.java:332)
> 	at ptolemy.actor.Manager.run(Manager.java:1071)
> 	at ptolemy.actor.Manager$3.run(Manager.java:1112)
>   
>
> -----Original Message-----
> From: kepler-users-bounces at ecoinformatics.org
> [mailto:kepler-users-bounces at ecoinformatics.org] On Behalf Of Luis
Assunção
> Sent: Wednesday, April 02, 2008 12:27 PM
> To: 'Daniel Crawl'
> Cc: kepler-users at ecoinformatics.org
> Subject: Re: [kepler-users] Problems with Actor - WebService With
> ComplexTypes
>
> Hi Daniel
>
> See attach the xml file from workflow.
> The Web Service is running on a local machine in ASP .NET Web service. It
is
> very simple (I wrote it only for test kepler with web service actor that
> support complex types) and the type used as input/output methods is a
simple
> Class with 3 fields of the type string. In future I will need kepler to
> invoke Web services with more complex data types, for instance, an
> aggregated Class based on other classes. 
>
> Thanks in advance
> Luis Assuncao
>
> -----Original Message-----
> From: Daniel Crawl [mailto:crawl at sdsc.edu]
> Sent: Wednesday, April 02, 2008 12:38 AM
> To: Luis Assunção
> Cc: kepler-users at ecoinformatics.org
> Subject: Re: [kepler-users] Problems with Actor - WebService With
> ComplexTypes
>
>
> Hi Luis,
>
> Could you send the workflow xml file? I would like to know
> what web service URL causes this problem.
>
> Thanks,
>
>   --dan
>
> Luis Assunção wrote:
>   
>> Hi
>>
>> After I have waited for Web Service Actor with complex types, finally 
>> I saw that this feature is available in Kepler version 1.0 rc1.
>>
>> Unfortunately I am disappointed because I tested with very simple 
>> workflow, see attached bitmap from kepler design,  (first actor call a 
>> method getContact that return a complex type (ct) and the second actor 
>> call other method that receive the result from 1^st actor (ct) and 
>> then return the same complex type (ct).
>>
>> If I only call the first method works, but if call the second method 
>> (see below) I have the following exception:
>>
>>  
>>
>> ptolemy.kernel.util.IllegalActionException: Attempt to link more than 
>> one relation to a single port.
>>
>>   in .ComplexTypes.normalizeContact.ct and .ComplexTypes.ct
>>
>>                 at 
>> ptolemy.actor.IOPort._checkMultiportLink(IOPort.java:3811)
>>
>>                 at ptolemy.actor.IOPort._checkLink(IOPort.java:3255)
>>
>>                 at 
>> ptolemy.actor.TypedIOPort._checkLink(TypedIOPort.java:736)
>>
>>                 at 
>> ptolemy.kernel.ComponentPort.link(ComponentPort.java:540)
>>
>>                 at ptolemy.actor.IOPort.link(IOPort.java:2217)
>>
>>                 at 
>>
>>     
>
org.sdm.spa.WSWithComplexTypes._addPortForComposite(WSWithComplexTypes.java:
> 1182)
>   
>>                 at 
>>
org.sdm.spa.WSWithComplexTypes._createOnePort(WSWithComplexTypes.java:946)
>>
>>                 at 
>>
>>     
>
org.sdm.spa.WSWithComplexTypes._genInputPortsAndActors(WSWithComplexTypes.ja
> va:594)
>   
>>                 at 
>> org.sdm.spa.WSWithComplexTypes._initMethod(WSWithComplexTypes.java:573)
>>
>>                 at 
>> org.sdm.spa.WSWithComplexTypes.preinitialize(WSWithComplexTypes.java:363)
>>
>>                 at
ptolemy.actor.Director.preinitialize(Director.java:865)
>>
>>                 at 
>>
ptolemy.domains.sdf.kernel.SDFDirector.preinitialize(SDFDirector.java:527)
>>
>>                 at 
>> ptolemy.actor.CompositeActor.preinitialize(CompositeActor.java:1103)
>>
>>                 at 
>> ptolemy.actor.Manager.preinitializeAndResolveTypes(Manager.java:913)
>>
>>                 at ptolemy.actor.Manager.initialize(Manager.java:578)
>>
>>                 at ptolemy.actor.Manager.execute(Manager.java:321)
>>
>>                 at ptolemy.actor.Manager.run(Manager.java:1071)
>>
>>                 at ptolemy.actor.Manager$3.run(Manager.java:1112)
>>
>> There is someone can give me some help ?
>>
>>  
>>
>> Luis Assuncao
>>
>> lass at isel.ipl.pt
>>
>>  
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at ecoinformatics.org
>>
http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
>>   
>>     
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WS-spell-checker.xml
Type: text/xml
Size: 52993 bytes
Desc: not available
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20080404/72fe00af/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: executionScreen.JPG
Type: image/jpeg
Size: 36516 bytes
Desc: not available
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20080404/72fe00af/attachment.jpe>


More information about the Kepler-users mailing list