Hi since nobody answered to my last post regarding this. I sucessfully merged Jetspeed and Soap on a binary level (see my last post) using Axis. I also developed a sample application accessing a soap service on the net (I found) via Axis and WSDL in a portlet.
(I also have a soap service serviced from my local database layer which also is accessed by jetspeed in the same webapp) So far it seems to work quite well. If anyone is interested I will write everything down and post the info. Just leave a comment in this thread if you are interested and I will write everything down the next few days. But what I acutally need is some info from the developers. I got a little bit butterflies in my stomach, by merging both systems within the same webapp on a binary level. The problem might be that, I had to remove the apache soap jar file and the old xalan file from the Jetspeed lib dir. (Xalan was replaced with the newer build in JDK 1.4.1 and Soap by the stuff which Axis delivers). So far the system runs really well, but does anyone of the developers have a clue what sideefects this might cause in the long term? I assume Xalan shouldn�t pose too much of a problem since it seems backward compatible, but the problem might be Soap/Axis. Since they might be used somewhere in the jetspeed sourcetree. Can anyone of the developers comment on this? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
