Try checking http://msdn.microsoft.com/xml. There are some tools available.

Alexander Klyubin

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Douglas D.
Dickinson
Sent: Tuesday, February 13, 2001 02:55
To: jboss-user
Subject: [jBoss-User] ZOAP: need a SOAP client to test with...


I appologize is the message is a bit confused,
but the truth is that I *am* confused!

After some fiddling I *believe* that I have ZOAP creating SOAP interfaces
for the EJBs that I deploy.
(At least jboss no longer throws exceptions when I drop my .jar into
jboss/deploy/)

My main question is:
Where can I find a *simple* tool to allow me to:
  - see what the zoap-deployed soap interfaces look like.
  - fire SOAP queries at my deployed EJB via SOAP.

Other questions:
  - What port(s) are the zoap interfaces on?
  - Anyone using  Perl's SOAP::Lite module?

As I understand it there are 2 different ways to zoap-enable an EJB jar:
(1) Simple:  Add to META-INF/jboss.xml
      This is almost working for me
(2) Complex: META-INF/com/me/ClassNames*.scl & *.xsd
      This seems to be the method use in test-bean.jar/test-client.jar

I tried looking into the zoap/src/test/Test*.java code but for several
reasons I find it very difficult to understand:
  - I've never seen junit before.
  - It creates & destroys a custom web server between each test.
  - I have no idea what the *.scl or *.xsd files are or how they are
created.

Any clarifications greatly appreciated.
( Please forgive my ignorance I'm very new to all of:  EJBs, SOAP, jboss, &
zoap !-)

Many thanks in advance,
DouglasDD
--
   Douglas D. Dickinson   =^..^=   [EMAIL PROTECTED]



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]




--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to