This has been done many times. But I guess my response is why? I have done it just to do it but not for a production effort. It adds way too much to the maintainability.
What are you going to do in Java that can’t be done in Tcl with 1/10th of the effort?
There are times when I have needed Java and I have used it. But, for strict message parsing, which is 98% of what we do, Tcl is *MUCH* better
With that said, if it makes you feel better to do Java, or if you have a true reasons to use it, go for it. That’s why we put it there. But there are no engine APIs written in Java. To access the engine, you still call Tcl from your Java class.
Just my humble opinion. If I were not so shy, I would tell you what I truely think 😉
Charlie
.
.