Well, with flowscript we still have our rhino bug that one developer is working on.
With Javaflow, we are having this session issue that we are trying to get resolved. So, at this point, we are keeping both options open. I have to say, a big positive on Javaflow is the type safety and the fun of working in Java. The downside was that the documentation is lacking compared to flowscript. (But I did get to have some fun looking through the source...) Does javaflow have dynamic class loading? I thought I read that somewhere. Thanks for all the help. I am sure it won't be the last question I ask about javaflow. Irv On 7/2/05, Torsten Curdt <[EMAIL PROTECTED]> wrote: > > Brave is an interesting term... :-) > > :-) > > > We have to work in Weblogic. There is a nasty bug in Rhino that is > > preventing it from working in Weblogic 8.1. We are working on > > resolution from BEA but not holding our breath. We have to comment > > tomorrow on whether or not switching to JavaFlow will solve our > > problem. Takes a little while to get used to, but nice to have strong > > type checking again :-) > > So any decision made yet? > > > Thanks for the help. > > No worries > > cheers > -- > Torsten > > > >
