On Monday 14 October 2002 20:49, David Sean Taylor wrote: > I agree > > > I will post a small example tomorrow evening as well in this thread. > > I'd like to take Axis as a jar file, and have an ant deploy task > automatically merge it into the Jetspeed war. > (Or if someone has a better solution...) > We shouldn't be duplicating any Axis files in Jetspeed. > Look forward to your posting
I'm not sure if that really is a good solution. The problem I saw was that Axis relies on a load of other Apache libraries. I'm not sure how problematic the compatiblity of various library versions is. But doing that might work for certain Jetspeed/Axis combinations (like it seems to work with 1.4b1/Axis 1.0) but as soon as there is another major inclusion of a library in Turbine, the whole merge might be problematic again. Since I'm not involved in Jakarta projects I'm not really sure how the project synchronisation is handled, all I could see was that most projects try to keep downward compatiblity tests by extensive unit testing. But I think the best thing would be if axis would be merged in some way into Turbine (where it actually would fit perfectly into) or at least there should be some kind of coordination between both projects so that a merge is possible. I don't really like the idea of having Axis running as a separate webapp only. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
