Help me please!! (Urgent!)

### Thank you for your reading my mail nevertheless you are busy !! HELLO! This is chihongkim from KOREA will hold WORLD-CUP in 2002. ___ I am developing a client/server project tha

Re: Unable to resolve namespace URI for 'ns2'. | not a classpath problem

"GOVINDA,RAJ (Non-HP-Sunnyvale,ex2)" wrote: > > Thanks for responding. But i have parser in front all other pakages, as i > mentioned in my previous mail. > When i startup server, classpath looks like this. > > Using CLASSPATH: > I:\Misc\dev\xerces-1_3_1\xerces.jar;C:\workarea\appserver\jakart

RE: Unable to resolve namespace URI for 'ns2'. | not a classpath problem

Thanks for responding. But i have parser in front all other pakages, as i mentioned in my previous mail. When i startup server, classpath looks like this. Using CLASSPATH: I:\Misc\dev\xerces-1_3_1\xerces.jar;C:\workarea\appserver\jakarta-tomcat-3.2 .3\classes;C:\workarea\appserver\jakarta-tomcat

RE: XMLParser throws out NullPointerException with a normal InputSour ce

My own code caused the problem. Sorry for the spam. Now I have a lot of faith in xerces parser now. BTW: anyone knows when xerces-j-2 is available for a big time? -Original Message- From: Richard Wu [mailto:[EMAIL PROTECTED]] Sent: July 23, 2001 2:55 PM To: '[EMAIL PROTECTED]' Subject: XM

RE: Newbie | Unable to resolve namespace URI for 'ns2'.

try this: In tomcat.bat, find the line that set CP and add xerces.jar in front of everything. Restart tomcat. Your tomcat.bat should look like: rem - Set Up The Runtime Classpath -- :setClasspath set CP=C:\tomcat\lib\xerces.jar;%TOMCAT_HOME%\classes Good

XMLParser throws out NullPointerException with a normal InputSource

I have run into NullPointerException thrown out almost at the end of an XML document process by org.apache.xerces.framework.XMLParser.java on line 969. A closer look at the code indicates the call, fScanner.parseSome(true), throws this exception, after all the element events are fired off. Here is

soap and xerces jars

Hello , I'm trying to make a client jar for my application which uses soap http requests only. The combined soap, xerces, mail, and activation jars are 2.18MB. I was wondering if anyone knows of a way to cut this size to something like 1MB. I've tried using a program called JarMaster to i

RE: Newbie | Unable to resolve namespace URI for 'ns2'.

I verified the classpath settings(both in tomcat server and client side). I have xerces parser before the other classes. I am still getting the same error. Unable to resolve namespace URI for 'ns2'.; advance thanks for solving this problem for me mohan -Original Message- From: Ratnakar

Re: httpRequest in my webservice ?

Please see the user's guide - under programming services it tells you how to get at SOAPContext via which you can get to the original HTTPRequest object (amongst other things). Sanjiva. - Original Message - From: "Naggi Rao" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July

httpRequest in my webservice ?

Hi all, Would it be possible for me to pass the Original HTTPRequest in to my WebService ? if so how Thanxs in advance, Naggi

RE: NS_URI_CURRENT_SCHEMA_XSI & NS_URI_CURRENT_SCHEMA_XSD

Try the sources from the CVS repository. I have seen 2000 in the traces with the current sources (as of July 5). -Original Message- From: Eduardo Yánez [mailto:[EMAIL PROTECTED]] Sent: sabato 21 luglio 2001 0.44 To: [EMAIL PROTECTED] Subject: NS_URI_CURRENT_SCHEMA_XSI & NS_URI_CURRENT_SC

Re: Faults and HTTP

I agree the spec is not perfect. One reason it has so many rough edges is that it was submitted to W3C, but never taken through the full spec process. The XML Protocol group will presumably produce a spec with fewer holes and/or ambiguities. Scott - Original Message - From: "Dirk-Willem

RE: NS_URI_CURRENT_SCHEMA_XSI & NS_URI_CURRENT_SCHEMA_XSD

Hi Eduardo, Did you re-compile all the source, or just the Consants.java file? Those constants are marked final. Thanks, -Matt > -Original Message- > From: Eduardo Yánez [mailto:[EMAIL PROTECTED]] > Sent: Friday, July 20, 2001 6:44 PM > To: [EMAIL PROTECTED] > Subject: NS_URI_CURRENT_SC