Hello,
I've checked the bugzilla bug database and the archives
on this list and don't think this is a known problem, so I'm describing
it here to see if I'm an idiot or if its a real problem.
I soapv2.2 on linux (mandrake 8.1, kernel 2.4.x)
running in both tomcat 4.x and iplanet 6.0SP2,
In org/apache/soap/providers/RPCJavaProvider.java please change 4th from
last line of code from:
throw new SOAPException( Constants.FAULT_CODE_SERVER, e.toString() );
to something like:
throw new SOAPException( Constants.FAULT_CODE_SERVER, "Error invoking "
+call, e);
I need this to get th
Take a look at http://www.capeclear.com./capestudio - anongst other things
it will generate VB client code for you given the WSDL description of the
service.
Regards
John
-Original Message-
From: Vaibhav Joshi [mailto:[EMAIL PROTECTED]]
Sent: 17 April 2002 19:29
To: '[EMAIL PROTECTED]'
S
I've just finished an outline of processing for an RPC call. You can view it at
http://mywebpages.comcast.net/scottnichol/apachesoapprocessing.htm
Scott Nichol
- Original Message -
From: "Mikko Laanti" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 03, 2002 7:03 AM
S
You have discovered an unimplemented feature. The StatelessEJBProvider is
supposed to make sure the method in the call (select_vegreh) is one of the
listed methods in the deployment descriptor, but it does not. The
RPCJavaProvider implements this by calling RPCRouter#validCall. The
StatelessEJB
The Apache SOAP code creates envelopes for you based on the code that is
executed. For example, a client will call SOAPMappingRegistry#mapType to
specify a serializer for a type (Java class), create a Vector of Parameter
instances and specify the target URI, encoding, method name and endpoint (UR
You
use SOAP API to create a SOAP envelopes. Such as the API of Apache
SOAP.
Shashi
Anand
-Original Message-From: pop m
[mailto:[EMAIL PROTECTED]]Sent: Thursday, April 18, 2002 8:57
PMTo: [EMAIL PROTECTED]Subject: SOAP
envelope
I have just understood
that I don't
Hi everybody !
I am going to
introduce you my problem:
I've a SOAP
DeploymentDescriptor showed below:
scope="Application"
methods="xyz">
org.apache.soap.server.DOMFaultListener
My java soap client looks
like:
try { U
I have just understood
that I don't need to write SOAP envelopes,
they are being created for
us. (by DeploymentDescriptor)
But in much documentations
I meet such code like:
/SOAP-ENV:Envelope>
and I really am a little
bit confused. For me it sounds like
Your Web server at address:port must be accessible through the firewall. The
actions you need to take depend on what the firewall is doing. For example, if
the firewall is doing IP filtering, you must open up address:port or perhaps
create a proxy to that address:port. If the firewall is doing
For getInstances(String s, String s1,String s2,String s3), you would do
Serializer.startBody
Serializer.startElement Method, MULTICITY_NS, NS_URI_SOAP_ENC, "mc"
'In the Java client, this corresponds to a new Parameter(...)
Serializer.startElemen
I have not experienced a similar problem, but I have an observation. When you
run under Tomcat 4.x, your Apache SOAP code will use the versions of Xerces,
JavaMail and JAF that are bundled with Tomcat. Under Tomcat 3.x, your Tomcat
startup script had to be changed to point to versions of those j
Hi everybody !
I am using Orion 1.5.4
app.server and Apache SOAP 2.2 on my machine which I'll call X.
X machine is behind the
firewall.
I also have an application
running on this application server who has EJB components.
I've written a soap client
to acces one of my EJB components, it loo
13 matches
Mail list logo
