SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Tuesday, October 18

18-Oct-2005

Soap - new views
(what happened since last episode)
For some unknown reason, things got worse: no way to build, nor deploy; perhaps after Tomcat has stopped and restarted, something changed in the Java environment; Who knows....
Not all details are at hand, but the weirdest things happened. Restarting Tomcat seems to have solved the problem.
But once build succeeded, created a jar file. But by no means got it deployed. Very annoying, since not any clue was found....
(Today's episode)
Idea # 1: What I could try is copy the .jar files to axis's web-inf directory. But that didn't help.
Idea # 2: Subscribed to axis-user mailing list and posted the problem. Got two hints:

  • Add the WSDD-data manually in server-config.wsdd.
  • Look what is shown when debug enabled.

The first isue is to find the right server-config.wsdd. There are several... Searching for the one(s) that have the deployed services in it, from Tomcat's home directory downwards, revealed the one in Tomcat's [.webapps.axis.WEB-INF] directory. Added the part in there, restarted Tomcat, but no reaction....
Idea # 3: Copy the .jar files to [webapps.axis.WEB-INF.classes]? No solution. expand them there?
Now things got REALLY worse: whenever axis/services was accessed. it ends up with a fatal error. Removing the whole lot, and the problem was gone...
Idea # 4: Look in Tomcat's logging. Found a clue there, why deployment failed: cannot locate the type-mapping - the first one in the wsdd!
Idea # 5: Copy the jar files to [.webapps.axis.WEB-INF.lib].
Don't forget to restart Tomcat.

IT SHOWS UP!

Even beter: IT WORKS. Even from the .NET application on the other side.

Next, adapt the code, rebuild the single class and rebuild the .jar file, and copy it.
But: Nothing changed ???
Looking for clues, scanned for all .jar files: No wonder if the created jar-file is in another location. After the right one was copied, it works, and gives the expected answers.
(Preview of next episode)
The only thing still to check is the outcome of using the DCL code. If that works (as I expect it will since it did in the test program) the research is to be finished.
(to be continued)

0 Comments:

Post a Comment

<< Home