Hi, Regarding adding composite and MoML class actors in the actor tree, I put in a bug in the Kepler bug tracker a while ago, but to my knowledge it is not fixed yet. See:
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=1851 You can observe the problem when you try some of our actors from the Resurgence project under Domain Specific/Computational Chemistry (some actors appear after printing an error, some hang up the Kepler interface). Any hints are very welcome! Good to know that I am not the only one who would like to have this working :-) Best regards, Wibke Dr. Wibke Sudholt Computational Grid Lead Institute of Organic Chemistry University of Zurich Winterthurerstrasse 190 CH-8057 Zurich Switzerland Phone: +41 44 635 4222 Email: wibke at oci.unizh.ch Web: http://www.baldridge.unizh.ch/~wibke/ On 19.05.2005 2:18, "Ralph Seguin" <seguin at lmsal.com> wrote: > Ok. > Sorry for the spammish and huge email (attachments). > > I've made certain that the .jar is in the CLASSPATH > (modified the lax.class.path var in the kepler_alpha6.lax > file) and it is definitely coming up. > The actors that I'm trying to add are all composite actors > from our COSEC/SolarSoft package. I had no trouble doing > it in Ptolemy II. > The tutorial covers adding an atomic actors, but this did > not work for these composite actors. I _HIGHLY_ recommend > coming up with a better import/add/unique id system... :-) > I've attached the annotations.owl and ontology.owl as I > think they should be given our service description file > (also attached). > I can also send the .jar if you are interested. I'm also > trying to get several other packages added. > > BTW- I also found out that the intro.htm and > welcomeMessage.xml files are used from the .jar file, and > not the files that are in the dir tree. > > Thanks. > -Ralph > seguin at lmsal.com > > > >> As you discovered, the procedure for adding actors to >> Kepler is >> quite a bit different than for Ptolemy. (And, currently, >> not easy and >> obvious.) annotations.owl and ontology.owl are the key >> files for adding >> to the actor list, but I suspect that your main problem >> is getting >> Kepler to see the jar file you refer to. All jar files >> need to added to >> the classpath. If you are running kepler from ant (using >> 'ant run-dev') >> then placing your jar inside the $Kepler/lib/jar >> directory should make >> it visible. Then just opening the appropriate workflow >> (*.xml file) >> should work even if your actor is not present on >> Kepler's actor list. If >> you use the .bat or .sh files, then your jar file must >> be explicitly >> added to the classpaths in these files (I don't know >> what OS or version >> your are using.) If you are using the 1.6alpha >> installers from the >> Kepler web page, adding to the classpath is tricky and I >> suggest using >> the .bat or .sh files. >> >> To add your actor to Keplers list, you can just right >> click on the >> appropriate caregory in the actor tree and add it by >> entering the Java >> class name if it is an atomic actor. Currenly, composite >> actors cannot >> be added this way. > > _______________________________________________ > Kepler-users mailing list > Kepler-users at ecoinformatics.org > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users >
