> Another question - should we maintain jdk1.1 compatibility (access
Hash
> table members through Enumeration)?
The code base no longer compiles with JDK 1.1. The number of places
where compilation fails is very limited, so it would be possible to work
to make a useful subset of the build work f
Do any other samples work? What XML parser (+version)
are you using? What servlet container? What
instructions did you follow for the installation?
Scott Nichol
--- ??? <[EMAIL PROTECTED]> wrote:
>
>
> I try to test sample SOAP code toworking with
> literal XML documents..
>
> but.. Fault
snichol 2002/10/15 20:33:20
Modified:java/docs/guide config.html
Log:
Add more information about securing the service manager and admin pages.
Revision ChangesPath
1.7 +36 -1 xml-soap/java/docs/guide/config.html
Index: config.html
===
Other samples work well..
xerces: 2.2
soap:2.3 & 2.2
Apache Tomcat : 4.1
i refered this site for installation..
http://www.scottnichol.com/apachesoapinstall.htm :-)
thanks a lot for your reply..
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: We
Exactly which sample are you running? What is the command line you are
running?
Scott Nichol
- Original Message -
From: "???" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 15, 2002 11:42 PM
Subject: RE: Fault Occured
> Other samples work well..
>
> xerces: 2.2
> s
*** Client Code
...
...
...
public Element getProduct (String sku)
throws SOAPException, MalformedURLException {
Parameter skuParam;
Call call = new Call();
call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
call.setTargetObjectURI("urn:examples:XMLPr
snichol 2002/10/15 20:58:11
Modified:java/docs changes.html
java/src/org/apache/soap/util/net HTTPUtils.java
Log:
Submitted by Pavel Ausianik ([EMAIL PROTECTED]):
Add client support for HTTP redirects.
Revision ChangesPath
1.49 +1 -0 xml-soa
Can you post a full stack trace? To get this, instead of something like
this on your client
System.out.println (" Fault Code: " + fault.getFaultCode ());
System.out.println (" Fault String: " + fault.getFaultString ());
just do something like
System.out.println (" Fault: " +
Here is the result...
Fault: [Attributes={}] [faultCode=SOAP-ENV:Server] [faultString=Exception from service
object: org/apache/soap/util/xml/XMLParserUtils]
[faultActorURI=/soap/servlet/rpcrouter] [DetailEntries=] [FaultEntries=] Server
Response:
-Original Message-
From
Is your service deployed with the following:
org.apache.soap.server.DOMFaultListener
Is it deployed on SOAP 2.2 or 2.3? With the above in the deployment
descriptor and SOAP 2.3 on the server, I would expect to see a stack
trace in the DetailEntries.
Scott Nichol
- Original Message -
SOAP 2.3.1 installed..
***
Fault: [Attributes={}] [faultCode=SOAP-ENV:Server] [faultString=Exception from
service object: org/apache/soap/util/xml/XMLParserUtils]
[faultActorURI=/soap/servlet/rpcrouter] [DetailEntries=
[(0)=java.lang.NoClassDefFoundError:
org/apache/soap/util/xml/XMLPar
Did you put your service class in %CATALINA_HOME%\classes?
Unfortunately, this does not work if the service class depends on
classes from Apache SOAP. You can either move your service classes to
%CATALINA_HOME%\webapps\soap\WEB-INF\classes, or do not use
XMLParserUtils. You can easily replace t
It works!!
Thank you kindly Scott.
-Original Message-
From: Scott Nichol [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 2:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Fault Occured
Did you put your service class in %CATALINA_HOME%\classes?
Unfortunately, this do
but..
why only this sample results like that... other sample codes work correctly ...
only put service class to %CATALINA_HOME%\classes, not to
%CATALINA_HOME%\webapps\soap\WEB-INF\classes
what's difference??
14 matches
Mail list logo