> From: Kevin Crowston <[email protected]> > Date: Sun, 20 Dec 2009 18:04:20 -0500 > To: [email protected]
Hello, > Sorry for the slow reply... That's OK > On 17 Dec 2009, at 8:06 AM, Alan Williams <[email protected]> wrote: > >> Second, when the workflow converted, all of the default values turned > >> into string constants. Their appearance prompted me to rewrite the > >> relevant bean scripts, which meant I could delete all the new string > >> constants. > > > > Are they that annoying? It sounds as if we should prioritise the > > ability to hide them. > Well, it was more the fact that they weren't really necessary since I could just edit the beanshell. That is, in 1.7, there seemed to be an advantage to using the builtin Java processors but in 2.1 they're the same as beanshell, and one custom bit of beanshell is a lot simpler than 2 string constants and a processor. I'd like to be able to hide them (and other non-essential services). > >> However, after deleting about 10 or 12, Taverna stopped > >> responding. I killed it after it was hung for a few minutes as > >> reported by Mac OS. This behaviour was repeatable--deleting a number > >> of processors in succession would seemingly hang Taverna. > > > > Can you send me a workflow that shows this? I've tried to replicate > > this here without success. > I'll have to pull out the passwords, but I can do that. Or let me try the 2.1 release first and see if it's still a problem. I tried to replicate it by taking one of Paul Fisher's big workflows and deleting everything one by one. I could do that and even undo/redo it and it seems to work OK. I also tried with a huge workflow that Peter Li sent me. It also went OK - although I'll admit I got bored before I'd deleted everything :-) > The SQL null handling remains a bit of an issue. SQL tables not infrequently have NULLs that ought to get passed to Taverna (and vice versa, from Taverna to the database). My hack of making a NULL into the string "null" is, well, a hack. I hope there's a better solution eventually. As Stian said (and as I feared) the "guts" of Taverna would object to trying to register null data. It will require quite a bit of thought to fix as Taverna will need to know if it is a null comming in place of a single value, a sublist or all the result. > Kevin Crowston Alan ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
