Hey Jianwu, Your changes to Kepler.java (r25215 and r25216, I believe) for bug#5115 are in 2.1, since 2.1 shares build-area with trunk, and you fixed this bug before I cut 2.1 (with an, at the time, up to date build-area). Derik
On Oct 24, 2010, at 3:37 PM, Jianwu Wang wrote: > Hi Ryan, > > I tried Tools->Module Manager in Kepler 2.0, I can see suites > and modules for both 2.0 and 2.1. It's weired that you find other > there. Please start Kepler from batch command, e.g. kepler.sh/ > kepler.bat of your kepler installation directory, and see whether it > has some exception or error message there. > > About HTTP Proxy Settings, I think I fixed it in Kepler trunk. > You can find more information > athttp://bugzilla.ecoinformatics.org/show_bug.cgi?id=5115 > > andhttp://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2010-July/002275.html > > . But Kepler 2.1 is released based on Kepler 2.0, not trunk. So > Kepler 2.1 will still have the problem. The upcoming Kepler 2.2 is > based on Kepler trunk, and this fix will be in Kepler 2.2. > Best wishes > > Sincerely yours > > Jianwu Wang > jianwu at sdsc.edu > http://users.sdsc.edu/~jianwu/ > > Assistant Project Scientist > Scientific Workflow Automation Technologies (SWAT) Laboratory > San Diego Supercomputer Center > University of California, San Diego > San Diego, CA, U.S.A. > > On 10/24/2010 12:14 PM, Timmons, Ryan P wrote: >> >> Greetings Kepler users, >> >> I am having issues in a couple of areas. One is the Tools->Module >> Manager, it cannot find any modules (such as the update from 2.0 to >> 2.1). >> The other is with the Web Service Actor, it gives this message when >> I specify a WSDL: >> Error evaluating expression: >> http://s3.amazonaws.com/doc/2006-03-01/AmazonS3.wsdl >> in .Unnamed1.Web Service Actor.wsdlUrl >> Because: >> Could not run WSDL parser. >> in .Unnamed1.Web Service Actor >> Because: >> Connection timed out: connect >> >> Please enter a new value: >> >> (Don?t mind the AmazonS3.wsdl, was trying just anything to see if >> it works. Confirmed using my browser that the WSDL exists). >> >> I believe it is the proxy settings, as it?s a laptop and when I >> take it home where there is no proxy the above items work. Also I >> was able to use the Web Service Actor to invoke a WSDL service that >> resided within my corporate network. >> >> I found this message from searching: >> http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2009-March/001360.html >> and tried launching from an edited kepler.bat along those lines, >> but did not resolve. >> >> Any help would be much appreciated, thanks in advance. >> >> Ryan >> >> >> Ryan Timmons >> Software Engineer, LMSSC ATC >> ryan.p.timmons at lmco.com >> Cell: 248-895-1935 >> >> _______________________________________________ >> Kepler-users mailing list >> Kepler-users at kepler-project.org >> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users > _______________________________________________ > Kepler-users mailing list > Kepler-users at kepler-project.org > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users ---------- Derik Barseghian http://nceas.ucsb.edu/ecoinfo | office: 805-893-5127 Rm 3411, Marine Science Research Building, UCSB Santa Barbara, CA, 93106-6150
