You are viewing a plain text version of this content. The canonical link for it is here.

Posted to soap-user@ws.apache.org by Cory Isaacson <ci...@capita2.com> on 2000/08/19 19:40:42 UTC

Configuration Problem

When running the new SOAP 2.0 I get the following error when I try to run the RPC servlet:

org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed.
 at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
 at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
 at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
 at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
 at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
 at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
 at org.apache.soap.rpc.Call.invoke(Call.java:157)
 at samples.stockquote.GetQuote.main(GetQuote.java:103)

I registered the RPCRouterServlet class as my servlet. Is this the correct class? The only other one I see is the RPCRouter class, but I'm not sure if that's a servlet.

Thanks,

Cory

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

As a last resort I will, but I think the earlier message about the Servlet SDK sounds correct. Hopefully WebSphere will work with that version.

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 6:00 PM
Subject: Re: Configuration Problem

Somehow I don't think this is about the compiler. Sorry, I don't have the
download of winCVS.
One other thought, I know your ultimate goal is websphere, but grab tomcat
and maybe try that. You can run tomcat alone (as a webserver/servlet engine)
and it would provide a lighter wieght testing environment. Plus, it eliminates
a load of variables with websphere. I know it's probably the last thing you want
to do is install yet another piece of software, but I don't think you'll regret it.

Cory Isaacson wrote:

Rich, I agree its strange. I wonder however if it could be because of the JDK I'm running. Let me know what you find from the build, and I'll try and make a build here as well. By the way, do you have a way to get WinCVS? I went to the site and they turned off all of the downloads as they couldn't handle the traffic. If not I'll just try making a bat file. Thanks, Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 4:38 PM
Subject: Re: Configuration Problem
Seems screwy. That doesn't seem like code that would generate an Illega...tion.
By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.
So, it sounds like it's not even gotten to the point where you are doing the
invoke on the provider. It's something wrong in the router itself, and if it
really cracked getting the Reader, may the request is corrupt or something.
Or, you've got some code out of synch or something. I'm set up to do my own
builds, and that way I can get at the code, so maybe your right to go ahead
and get at the soap code itself.

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Rich, I think you're right, and for sure the provider class is not being entered (I have a print statement right at the top of my method). I checked the deployment through the admin page, and it looks to be correct. See the data below. I couldn't have made a simpler example (just returns a string with no parameters and no serialization). I also hard-coded all of the URL parameters, etc. to be sure they were correct. The rpcrouter is definitely being called, and then gets stuck at the IllegalArgumentException, which occurs from the following in the rpcrouter (if the source I have matches the soap.jar I am using): Reader requestReader = req.getReader (); This seems like a pretty harmless call, as its just getting the reader from the Servlet request object, something I do all the time with no problem. Unless you have any other ideas, the only think I can think of is to do a build from the source and try to add more debug statements. Thanks, Cory

'urn:SurgeTest' Service Deployment Descriptor
Property Details
ID urn:SurgeTest
Scope Application
Provider Type java
Provider Class sample.surgetest.SurgeTestProvider
Use Static Class false
Methods getTest
Type Mappings

----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:58 PM
Subject: Re: Configuration Problem
Ok, so the router apparently finds the provider and invokes
a method on it right? But the provider doesn't seem to be entered?
Otherwise I assume we would get
a much clearer error message. Have you brought up a browser
and pointed it to http://localhost:8080/soap/admin to get the admin
page and then do a list to see if your providers are in fact deployed.
Then maybe look at the deployment details and make sure it all looks right.
I'm wondering if this isn't one of those cases (in light of a recent release change)
that there isn't something stale out there, or two versions and the wrong one
getting used thing. For example, the soap layer has a serialized file that it
stores deployment info so that when it starts up again it redeploys what's
already been deployed. That should probably be wacked, and then redeploy.

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Rich, I wrote another simple set of classes, and you're correct -- they are not running. Any idea why? I checked the classpath on my server and it seems to be OK, but the provider class doesn't get fired. I'm running from soap.jar so its a little hard to debug anything in soap itself. Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:20 PM
Subject: Re: Configuration Problem
Not sure. Maybe try another demo.Since this is a new
release (i'm still on the previous) just put up friday,
it hasn't been used by a lot of people, so maybe you're
up against a bug.
Also, can you use some println's in your provider to see
if you're reaching it? I assume the router found it and it's
deployed properly, otherwise you'd have a different error.

Cory Isaacson wrote:

Rich, I got the TcpTunnelGui working fine now. I now see how it works. The call looks good from the client, but the provider is returning: java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet runs for sure if I type the URL manually into my browser (I get the error about not processing 'GET' requests). If the provider is not running, how could I tell that? Thanks, Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 2:34 PM
Subject: Re: Configuration Problem
RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
2.0 yet. I have seen this error when the router doesn't run at all. The element that the
provider was supposed to produce, is null and thus NOT well-formed. If you're not getting to
the router, then the provider isn't running. Just a thought.
Cory Isaacson wrote:

When running the new SOAP 2.0 I get the following error when I try to run the RPC servlet: org.xml.sax.SAXParseException: The markup in the document preceding the root element must be well-formed.
at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
at org.apache.soap.rpc.Call.invoke(Call.java:157)
at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the RPCRouterServlet class as my servlet. Is this the correct class? The only other one I see is the RPCRouter class, but I'm not sure if that's a servlet. Thanks, Cory

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

As a last resort I will, but I think the earlier message about the Servlet SDK sounds correct. Hopefully WebSphere will work with that version.

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 6:00 PM
Subject: Re: Configuration Problem

Cory Isaacson wrote:

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Somehow I don't  think this is about the compiler. Sorry, I don't have the
download of winCVS.

One other thought, I know your ultimate goal is websphere, but grab tomcat
and maybe try that. You can run tomcat alone (as a webserver/servlet engine)
and it would provide a lighter wieght testing environment. Plus, it eliminates
a load of variables with websphere. I know it's probably the last thing you want
to do is install yet another piece of software, but I don't think you'll regret it.


Cory Isaacson wrote:

>  Rich, I agree its strange. I wonder however if it could be because of the JDK I'm running. Let me
> know what you find from the build, and I'll try and make a build here as well. By the way, do you
> have a way to get WinCVS? I went to the site and they turned off all of the downloads as they
> couldn't handle the traffic. If not I'll just try making a bat file. Thanks, Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 4:38 PM
>      Subject: Re: Configuration Problem
>       Seems screwy. That doesn't seem like code that would generate an Illega...tion.
>      By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.
>
>      So, it sounds like it's not even gotten to the point where you are doing the
>      invoke on the provider. It's something wrong in the router itself, and if it
>      really cracked getting the Reader, may the request is corrupt or something.
>      Or, you've got some code out of synch or something. I'm set up to do my own
>      builds, and that way I can get at the code, so maybe your right to go ahead
>      and get at the soap code itself.
>
>      Anyway, sorry I don't have a better suggestion.
>
>      Cory Isaacson wrote:
>
>     >  Rich, I think you're right, and for sure the provider class is not being entered (I
>     > have a print statement right at the top of my method). I checked the deployment
>     > through the admin page, and it looks to be correct. See the data below. I couldn't
>     > have made a simpler example (just returns a string with no parameters and no
>     > serialization). I also hard-coded all of the URL parameters, etc. to be sure they were
>     > correct. The rpcrouter is definitely being called, and then gets stuck at the
>     > IllegalArgumentException, which occurs from the following in the rpcrouter (if the
>     > source I have matches the soap.jar I am using): Reader requestReader = req.getReader
>     > (); This seems like a pretty harmless call, as its just getting the reader from the
>     > Servlet request object, something I do all the time with no problem. Unless you have
>     > any other ideas, the only think I can think of is to do a build from the source and
>     > try to add more debug statements. Thanks, Cory
>     >

                                    'urn:SurgeTest' Service Deployment Descriptor

                     Property                                          Details
         ID                              urn:SurgeTest
         Scope                           Application
         Provider Type                   java
         Provider Class                  sample.surgetest.SurgeTestProvider
         Use Static Class                false
         Methods                         getTest
         Type Mappings
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 3:58 PM
>     >      Subject: Re: Configuration Problem
>     >       Ok, so the router apparently finds the provider and invokes
>     >      a method on it right? But the provider doesn't seem to be entered?
>     >      Otherwise I assume we would get
>     >      a much clearer error message. Have you brought up a browser
>     >      and pointed it to http://localhost:8080/soap/admin to get the admin
>     >      page and then do a list to see if your providers are in fact deployed.
>     >      Then maybe look at the deployment details and make sure it all looks right.
>     >
>     >      I'm wondering if this isn't one of those cases (in light of a recent release
>     >      change)
>     >      that there isn't something stale out there, or two versions and the wrong
>     >      one
>     >      getting used thing. For example, the soap layer has a serialized file that
>     >      it
>     >      stores deployment info so that when it starts up again it redeploys what's
>     >      already been deployed. That should probably be wacked, and then redeploy.
>     >
>     >      Also, back when we were using jdp for the router, a stale servlet class
>     >      (generated from the jsp) could screw you as well. Not sure if Websphere
>     >      stashes servlet classes any where.
>     >
>     >      A few ideas.
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      >  Rich, I wrote another simple set of classes, and you're correct -- they
>     >      > are not running. Any idea why? I checked the classpath on my server and it
>     >      > seems to be OK, but the provider class doesn't get fired. I'm running from
>     >      > soap.jar so its a little hard to debug anything in soap itself. Cory
>     >      >
>     >      >      ----- Original Message -----
>     >      >      From: Rich Johns
>     >      >      To: soap-user@xml.apache.org
>     >      >      Sent: Saturday, August 19, 2000 3:20 PM
>     >      >      Subject: Re: Configuration Problem
>     >      >       Not sure. Maybe try another demo.Since this is a new
>     >      >      release (i'm still on the previous) just put up friday,
>     >      >      it hasn't been used by a lot of people, so maybe you're
>     >      >      up against a bug.
>     >      >
>     >      >      Also, can you use some println's in your provider to see
>     >      >      if you're reaching it? I assume the router found it and it's
>     >      >      deployed properly, otherwise you'd have a different error.
>     >      >
>     >      >
>     >      >      Cory Isaacson wrote:
>     >      >
>     >      >     >   Rich, I got the TcpTunnelGui working fine now. I now see how
>     >      >     >  it works. The call looks good from the client, but the provider
>     >      >     >  is returning: java.lang.IllegalArgumentException:
>     >      >     >  sun.io.ByteToCharUTF-8
>     >      >     >   at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)
>     >      >     >  The servlet runs for sure if I type the URL manually into my
>     >      >     >  browser (I get the error about not processing 'GET' requests).
>     >      >     >  If the provider is not running, how could I tell that? Thanks,
>     >      >     >  Cory
>     >      >     >
>     >      >     >       ----- Original Message -----
>     >      >     >       From: Rich Johns
>     >      >     >       To: soap-user@xml.apache.org
>     >      >     >       Sent: Saturday, August 19, 2000 2:34 PM
>     >      >     >       Subject: Re: Configuration Problem
>     >      >     >        RPCRouterServlet is the right one. As far as the
>     >      >     >       error, not sure. I haven't pulled down
>     >      >     >       2.0 yet.  I have seen this error when the router
>     >      >     >       doesn't run at all. The element that the
>     >      >     >       provider was supposed to produce, is null and thus
>     >      >     >       NOT well-formed. If you're not getting to
>     >      >     >       the router, then the provider isn't running. Just a
>     >      >     >       thought.
>     >      >     >
>     >      >     >       Cory Isaacson wrote:
>     >      >     >
>     >      >     >      > When running the new SOAP 2.0 I get the following
>     >      >     >      > error when I try to run the RPC servlet:
>     >      >     >      > org.xml.sax.SAXParseException: The markup in the
>     >      >     >      > document preceding the root element must be
>     >      >     >      > well-formed.
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
>     >      >     >      > Code)
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >     >      >
>     >      >     >      >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >     >      >  at
>     >      >     >      > samples.stockquote.GetQuote.main(GetQuote.java:103)
>     >      >     >      > I registered the RPCRouterServlet class as my
>     >      >     >      > servlet. Is this the correct class? The only other
>     >      >     >      > one I see is the RPCRouter class, but I'm not sure
>     >      >     >      > if that's a servlet. Thanks, Cory
>     >      >     >

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Somehow I don't  think this is about the compiler. Sorry, I don't have the
download of winCVS.

One other thought, I know your ultimate goal is websphere, but grab tomcat
and maybe try that. You can run tomcat alone (as a webserver/servlet engine)
and it would provide a lighter wieght testing environment. Plus, it eliminates
a load of variables with websphere. I know it's probably the last thing you want
to do is install yet another piece of software, but I don't think you'll regret it.


Cory Isaacson wrote:

>  Rich, I agree its strange. I wonder however if it could be because of the JDK I'm running. Let me
> know what you find from the build, and I'll try and make a build here as well. By the way, do you
> have a way to get WinCVS? I went to the site and they turned off all of the downloads as they
> couldn't handle the traffic. If not I'll just try making a bat file. Thanks, Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 4:38 PM
>      Subject: Re: Configuration Problem
>       Seems screwy. That doesn't seem like code that would generate an Illega...tion.
>      By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.
>
>      So, it sounds like it's not even gotten to the point where you are doing the
>      invoke on the provider. It's something wrong in the router itself, and if it
>      really cracked getting the Reader, may the request is corrupt or something.
>      Or, you've got some code out of synch or something. I'm set up to do my own
>      builds, and that way I can get at the code, so maybe your right to go ahead
>      and get at the soap code itself.
>
>      Anyway, sorry I don't have a better suggestion.
>
>      Cory Isaacson wrote:
>
>     >  Rich, I think you're right, and for sure the provider class is not being entered (I
>     > have a print statement right at the top of my method). I checked the deployment
>     > through the admin page, and it looks to be correct. See the data below. I couldn't
>     > have made a simpler example (just returns a string with no parameters and no
>     > serialization). I also hard-coded all of the URL parameters, etc. to be sure they were
>     > correct. The rpcrouter is definitely being called, and then gets stuck at the
>     > IllegalArgumentException, which occurs from the following in the rpcrouter (if the
>     > source I have matches the soap.jar I am using): Reader requestReader = req.getReader
>     > (); This seems like a pretty harmless call, as its just getting the reader from the
>     > Servlet request object, something I do all the time with no problem. Unless you have
>     > any other ideas, the only think I can think of is to do a build from the source and
>     > try to add more debug statements. Thanks, Cory
>     >

                                    'urn:SurgeTest' Service Deployment Descriptor

                     Property                                          Details
         ID                              urn:SurgeTest
         Scope                           Application
         Provider Type                   java
         Provider Class                  sample.surgetest.SurgeTestProvider
         Use Static Class                false
         Methods                         getTest
         Type Mappings
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 3:58 PM
>     >      Subject: Re: Configuration Problem
>     >       Ok, so the router apparently finds the provider and invokes
>     >      a method on it right? But the provider doesn't seem to be entered?
>     >      Otherwise I assume we would get
>     >      a much clearer error message. Have you brought up a browser
>     >      and pointed it to http://localhost:8080/soap/admin to get the admin
>     >      page and then do a list to see if your providers are in fact deployed.
>     >      Then maybe look at the deployment details and make sure it all looks right.
>     >
>     >      I'm wondering if this isn't one of those cases (in light of a recent release
>     >      change)
>     >      that there isn't something stale out there, or two versions and the wrong
>     >      one
>     >      getting used thing. For example, the soap layer has a serialized file that
>     >      it
>     >      stores deployment info so that when it starts up again it redeploys what's
>     >      already been deployed. That should probably be wacked, and then redeploy.
>     >
>     >      Also, back when we were using jdp for the router, a stale servlet class
>     >      (generated from the jsp) could screw you as well. Not sure if Websphere
>     >      stashes servlet classes any where.
>     >
>     >      A few ideas.
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      >  Rich, I wrote another simple set of classes, and you're correct -- they
>     >      > are not running. Any idea why? I checked the classpath on my server and it
>     >      > seems to be OK, but the provider class doesn't get fired. I'm running from
>     >      > soap.jar so its a little hard to debug anything in soap itself. Cory
>     >      >
>     >      >      ----- Original Message -----
>     >      >      From: Rich Johns
>     >      >      To: soap-user@xml.apache.org
>     >      >      Sent: Saturday, August 19, 2000 3:20 PM
>     >      >      Subject: Re: Configuration Problem
>     >      >       Not sure. Maybe try another demo.Since this is a new
>     >      >      release (i'm still on the previous) just put up friday,
>     >      >      it hasn't been used by a lot of people, so maybe you're
>     >      >      up against a bug.
>     >      >
>     >      >      Also, can you use some println's in your provider to see
>     >      >      if you're reaching it? I assume the router found it and it's
>     >      >      deployed properly, otherwise you'd have a different error.
>     >      >
>     >      >
>     >      >      Cory Isaacson wrote:
>     >      >
>     >      >     >   Rich, I got the TcpTunnelGui working fine now. I now see how
>     >      >     >  it works. The call looks good from the client, but the provider
>     >      >     >  is returning: java.lang.IllegalArgumentException:
>     >      >     >  sun.io.ByteToCharUTF-8
>     >      >     >   at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)
>     >      >     >  The servlet runs for sure if I type the URL manually into my
>     >      >     >  browser (I get the error about not processing 'GET' requests).
>     >      >     >  If the provider is not running, how could I tell that? Thanks,
>     >      >     >  Cory
>     >      >     >
>     >      >     >       ----- Original Message -----
>     >      >     >       From: Rich Johns
>     >      >     >       To: soap-user@xml.apache.org
>     >      >     >       Sent: Saturday, August 19, 2000 2:34 PM
>     >      >     >       Subject: Re: Configuration Problem
>     >      >     >        RPCRouterServlet is the right one. As far as the
>     >      >     >       error, not sure. I haven't pulled down
>     >      >     >       2.0 yet.  I have seen this error when the router
>     >      >     >       doesn't run at all. The element that the
>     >      >     >       provider was supposed to produce, is null and thus
>     >      >     >       NOT well-formed. If you're not getting to
>     >      >     >       the router, then the provider isn't running. Just a
>     >      >     >       thought.
>     >      >     >
>     >      >     >       Cory Isaacson wrote:
>     >      >     >
>     >      >     >      > When running the new SOAP 2.0 I get the following
>     >      >     >      > error when I try to run the RPC servlet:
>     >      >     >      > org.xml.sax.SAXParseException: The markup in the
>     >      >     >      > document preceding the root element must be
>     >      >     >      > well-formed.
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
>     >      >     >      > Code)
>     >      >     >      >  at
>     >      >     >      > org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >     >      >
>     >      >     >      >  at
>     >      >     >      > org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >     >      >
>     >      >     >      >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >     >      >  at
>     >      >     >      > samples.stockquote.GetQuote.main(GetQuote.java:103)
>     >      >     >      > I registered the RPCRouterServlet class as my
>     >      >     >      > servlet. Is this the correct class? The only other
>     >      >     >      > one I see is the RPCRouter class, but I'm not sure
>     >      >     >      > if that's a servlet. Thanks, Cory
>     >      >     >

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I agree its strange. I wonder however if it could be because of the JDK I'm running. Let me know what you find from the build, and I'll try and make a build here as well.

By the way, do you have a way to get WinCVS? I went to the site and they turned off all of the downloads as they couldn't handle the traffic. If not I'll just try making a bat file.

Thanks,

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 4:38 PM
Subject: Re: Configuration Problem

Seems screwy. That doesn't seem like code that would generate an Illega...tion.
By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.
So, it sounds like it's not even gotten to the point where you are doing the
invoke on the provider. It's something wrong in the router itself, and if it
really cracked getting the Reader, may the request is corrupt or something.
Or, you've got some code out of synch or something. I'm set up to do my own
builds, and that way I can get at the code, so maybe your right to go ahead
and get at the soap code itself.

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I agree its strange. I wonder however if it could be because of the JDK I'm running. Let me know what you find from the build, and I'll try and make a build here as well.

By the way, do you have a way to get WinCVS? I went to the site and they turned off all of the downloads as they couldn't handle the traffic. If not I'll just try making a bat file.

Thanks,

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 4:38 PM
Subject: Re: Configuration Problem

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Steven,

I checked and WebSphere is using the Servlet 2.1 API, and the latest is 2.2. Any way to tell if 2.2 is required? As IBM is so involved with the development process, I should be able to get it to work with their server.

Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 5:22 PM
Subject: RE: Configuration Problem

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of course.. :-)

-----Original Message-----
From: Rich Johns [mailto:rjohns@vignette.com]
Sent: Saturday, August 19, 2000 3:38 PM
To: soap-user@xml.apache.org
Subject: Re: Configuration Problem

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Steven,

Then that's it, because I'm using JDK1.1.7 with IBM Websphere, and I think its Servlets 1.1. I'm not sure if the server will work if I upgrade, but I'll try it.

Thanks,

Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 5:22 PM
Subject: RE: Configuration Problem

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of course.. :-)

-----Original Message-----
From: Rich Johns [mailto:rjohns@vignette.com]
Sent: Saturday, August 19, 2000 3:38 PM
To: soap-user@xml.apache.org
Subject: Re: Configuration Problem

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Steven,

Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 5:22 PM
Subject: RE: Configuration Problem

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of course.. :-)

-----Original Message-----
From: Rich Johns [mailto:rjohns@vignette.com]
Sent: Saturday, August 19, 2000 3:38 PM
To: soap-user@xml.apache.org
Subject: Re: Configuration Problem

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Steven,

Then that's it, because I'm using JDK1.1.7 with IBM Websphere, and I think its Servlets 1.1. I'm not sure if the server will work if I upgrade, but I'll try it.

Thanks,

Cory
----- Original Message -----
From: Steven J. McDowall
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 5:22 PM
Subject: RE: Configuration Problem

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of course.. :-)

-----Original Message-----
From: Rich Johns [mailto:rjohns@vignette.com]
Sent: Saturday, August 19, 2000 3:38 PM
To: soap-user@xml.apache.org
Subject: Re: Configuration Problem

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

RE: Configuration Problem

Posted by "Steven J. McDowall" <sj...@visi.com>.

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think
the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of
course.. :-)

  -----Original Message-----
  From: Rich Johns [mailto:rjohns@vignette.com]
  Sent: Saturday, August 19, 2000 3:38 PM
  To: soap-user@xml.apache.org
  Subject: Re: Configuration Problem


  Seems screwy. That doesn't seem like code that would generate an
Illega...tion.
  By the way, do you mean RPCRouterServlet? That's where I found the
req.getReader() line.
  So, it sounds like it's not even gotten to the point where you are doing
the
  invoke on the provider. It's something wrong in the router itself, and if
it
  really cracked getting the Reader, may the request is corrupt or
something.
  Or, you've got some code out of synch or something. I'm set up to do my
own
  builds, and that way I can get at the code, so maybe your right to go
ahead
  and get at the soap code itself.

  Anyway, sorry I don't have a better suggestion.

  Cory Isaacson wrote:

     Rich, I think you're right, and for sure the provider class is not
being entered (I have a print statement right at the top of my method). I
checked the deployment through the admin page, and it looks to be correct.
See the data below. I couldn't have made a simpler example (just returns a
string with no parameters and no serialization). I also hard-coded all of
the URL parameters, etc. to be sure they were correct. The rpcrouter is
definitely being called, and then gets stuck at the
IllegalArgumentException, which occurs from the following in the rpcrouter
(if the source I have matches the soap.jar I am using): Reader requestReader
= req.getReader (); This seems like a pretty harmless call, as its just
getting the reader from the Servlet request object, something I do all the
time with no problem. Unless you have any other ideas, the only think I can
think of is to do a build from the source and try to add more debug
statements. Thanks, Cory
       'urn:SurgeTest' Service Deployment Descriptor
          Property Details
          ID urn:SurgeTest
          Scope Application
          Provider Type java
          Provider Class sample.surgetest.SurgeTestProvider
          Use Static Class false
          Methods getTest
          Type Mappings

      ----- Original Message -----
      From: Rich Johns
      To: soap-user@xml.apache.org
      Sent: Saturday, August 19, 2000 3:58 PM
      Subject: Re: Configuration Problem
       Ok, so the router apparently finds the provider and invokes
      a method on it right? But the provider doesn't seem to be entered?
      Otherwise I assume we would get
      a much clearer error message. Have you brought up a browser
      and pointed it to http://localhost:8080/soap/admin to get the admin
      page and then do a list to see if your providers are in fact deployed.
      Then maybe look at the deployment details and make sure it all looks
right.
      I'm wondering if this isn't one of those cases (in light of a recent
release change)
      that there isn't something stale out there, or two versions and the
wrong one
      getting used thing. For example, the soap layer has a serialized file
that it
      stores deployment info so that when it starts up again it redeploys
what's
      already been deployed. That should probably be wacked, and then
redeploy.

      Also, back when we were using jdp for the router, a stale servlet
class
      (generated from the jsp) could screw you as well. Not sure if
Websphere
      stashes servlet classes any where.

      A few ideas.

      Cory Isaacson wrote:

         Rich, I wrote another simple set of classes, and you're correct --
they are not running. Any idea why? I checked the classpath on my server and
it seems to be OK, but the provider class doesn't get fired. I'm running
from soap.jar so its a little hard to debug anything in soap itself. Cory
          ----- Original Message -----
          From: Rich Johns
          To: soap-user@xml.apache.org
          Sent: Saturday, August 19, 2000 3:20 PM
          Subject: Re: Configuration Problem
           Not sure. Maybe try another demo.Since this is a new
          release (i'm still on the previous) just put up friday,
          it hasn't been used by a lot of people, so maybe you're
          up against a bug.
          Also, can you use some println's in your provider to see
          if you're reaching it? I assume the router found it and it's
          deployed properly, otherwise you'd have a different error.


          Cory Isaacson wrote:

             Rich, I got the TcpTunnelGui working fine now. I now see how it
works. The call looks good from the client, but the provider is returning:
java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
             at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)
The servlet runs for sure if I type the URL manually into my browser (I get
the error about not processing 'GET' requests). If the provider is not
running, how could I tell that? Thanks, Cory
              ----- Original Message -----
              From: Rich Johns
              To: soap-user@xml.apache.org
              Sent: Saturday, August 19, 2000 2:34 PM
              Subject: Re: Configuration Problem
               RPCRouterServlet is the right one. As far as the error, not
sure. I haven't pulled down
              2.0 yet.  I have seen this error when the router doesn't run
at all. The element that the
              provider was supposed to produce, is null and thus NOT
well-formed. If you're not getting to
              the router, then the provider isn't running. Just a thought.
              Cory Isaacson wrote:

                When running the new SOAP 2.0 I get the following error when
I try to run the RPC servlet: org.xml.sax.SAXParseException: The markup in
the document preceding the root element must be well-formed.
                 at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
                 at
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocume
ntScanner.java:625)
                 at
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
LDocumentScanner.java:804)
                 at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
                 at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
                 at
org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
5)
                 at org.apache.soap.rpc.Call.invoke(Call.java:157)
                 at samples.stockquote.GetQuote.main(GetQuote.java:103) I
registered the RPCRouterServlet class as my servlet. Is this the correct
class? The only other one I see is the RPCRouter class, but I'm not sure if
that's a servlet. Thanks, Cory

RE: Configuration Problem

Posted by "Steven J. McDowall" <sj...@visi.com>.

Hmm.. Make sure the right (newest) Servlet JSDK is being used too.. I think
the UTF8 is
"new" to JSDK 1.2 .. Make sure that is in the path as well (classpath of
course.. :-)

  -----Original Message-----
  From: Rich Johns [mailto:rjohns@vignette.com]
  Sent: Saturday, August 19, 2000 3:38 PM
  To: soap-user@xml.apache.org
  Subject: Re: Configuration Problem


  Seems screwy. That doesn't seem like code that would generate an
Illega...tion.
  By the way, do you mean RPCRouterServlet? That's where I found the
req.getReader() line.
  So, it sounds like it's not even gotten to the point where you are doing
the
  invoke on the provider. It's something wrong in the router itself, and if
it
  really cracked getting the Reader, may the request is corrupt or
something.
  Or, you've got some code out of synch or something. I'm set up to do my
own
  builds, and that way I can get at the code, so maybe your right to go
ahead
  and get at the soap code itself.

  Anyway, sorry I don't have a better suggestion.

  Cory Isaacson wrote:

     Rich, I think you're right, and for sure the provider class is not
being entered (I have a print statement right at the top of my method). I
checked the deployment through the admin page, and it looks to be correct.
See the data below. I couldn't have made a simpler example (just returns a
string with no parameters and no serialization). I also hard-coded all of
the URL parameters, etc. to be sure they were correct. The rpcrouter is
definitely being called, and then gets stuck at the
IllegalArgumentException, which occurs from the following in the rpcrouter
(if the source I have matches the soap.jar I am using): Reader requestReader
= req.getReader (); This seems like a pretty harmless call, as its just
getting the reader from the Servlet request object, something I do all the
time with no problem. Unless you have any other ideas, the only think I can
think of is to do a build from the source and try to add more debug
statements. Thanks, Cory
       'urn:SurgeTest' Service Deployment Descriptor
          Property Details
          ID urn:SurgeTest
          Scope Application
          Provider Type java
          Provider Class sample.surgetest.SurgeTestProvider
          Use Static Class false
          Methods getTest
          Type Mappings

      ----- Original Message -----
      From: Rich Johns
      To: soap-user@xml.apache.org
      Sent: Saturday, August 19, 2000 3:58 PM
      Subject: Re: Configuration Problem
       Ok, so the router apparently finds the provider and invokes
      a method on it right? But the provider doesn't seem to be entered?
      Otherwise I assume we would get
      a much clearer error message. Have you brought up a browser
      and pointed it to http://localhost:8080/soap/admin to get the admin
      page and then do a list to see if your providers are in fact deployed.
      Then maybe look at the deployment details and make sure it all looks
right.
      I'm wondering if this isn't one of those cases (in light of a recent
release change)
      that there isn't something stale out there, or two versions and the
wrong one
      getting used thing. For example, the soap layer has a serialized file
that it
      stores deployment info so that when it starts up again it redeploys
what's
      already been deployed. That should probably be wacked, and then
redeploy.

      Also, back when we were using jdp for the router, a stale servlet
class
      (generated from the jsp) could screw you as well. Not sure if
Websphere
      stashes servlet classes any where.

      A few ideas.

      Cory Isaacson wrote:

         Rich, I wrote another simple set of classes, and you're correct --
they are not running. Any idea why? I checked the classpath on my server and
it seems to be OK, but the provider class doesn't get fired. I'm running
from soap.jar so its a little hard to debug anything in soap itself. Cory
          ----- Original Message -----
          From: Rich Johns
          To: soap-user@xml.apache.org
          Sent: Saturday, August 19, 2000 3:20 PM
          Subject: Re: Configuration Problem
           Not sure. Maybe try another demo.Since this is a new
          release (i'm still on the previous) just put up friday,
          it hasn't been used by a lot of people, so maybe you're
          up against a bug.
          Also, can you use some println's in your provider to see
          if you're reaching it? I assume the router found it and it's
          deployed properly, otherwise you'd have a different error.


          Cory Isaacson wrote:

             Rich, I got the TcpTunnelGui working fine now. I now see how it
works. The call looks good from the client, but the provider is returning:
java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
             at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)
The servlet runs for sure if I type the URL manually into my browser (I get
the error about not processing 'GET' requests). If the provider is not
running, how could I tell that? Thanks, Cory
              ----- Original Message -----
              From: Rich Johns
              To: soap-user@xml.apache.org
              Sent: Saturday, August 19, 2000 2:34 PM
              Subject: Re: Configuration Problem
               RPCRouterServlet is the right one. As far as the error, not
sure. I haven't pulled down
              2.0 yet.  I have seen this error when the router doesn't run
at all. The element that the
              provider was supposed to produce, is null and thus NOT
well-formed. If you're not getting to
              the router, then the provider isn't running. Just a thought.
              Cory Isaacson wrote:

                When running the new SOAP 2.0 I get the following error when
I try to run the RPC servlet: org.xml.sax.SAXParseException: The markup in
the document preceding the root element must be well-formed.
                 at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
                 at
org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocume
ntScanner.java:625)
                 at
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
LDocumentScanner.java:804)
                 at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
                 at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
                 at
org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
5)
                 at org.apache.soap.rpc.Call.invoke(Call.java:157)
                 at samples.stockquote.GetQuote.main(GetQuote.java:103) I
registered the RPCRouterServlet class as my servlet. Is this the correct
class? The only other one I see is the RPCRouter class, but I'm not sure if
that's a servlet. Thanks, Cory

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Seems screwy. That doesn't seem like code that would generate an Illega...tion.
By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.

So, it sounds like it's not even gotten to the point where you are doing the
invoke on the provider. It's something wrong in the router itself, and if it
really cracked getting the Reader, may the request is corrupt or something.
Or, you've got some code out of synch or something. I'm set up to do my own
builds, and that way I can get at the code, so maybe your right to go ahead
and get at the soap code itself.

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

>  Rich, I think you're right, and for sure the provider class is not being entered (I have a print
> statement right at the top of my method). I checked the deployment through the admin page, and it
> looks to be correct. See the data below. I couldn't have made a simpler example (just returns a
> string with no parameters and no serialization). I also hard-coded all of the URL parameters, etc.
> to be sure they were correct. The rpcrouter is definitely being called, and then gets stuck at the
> IllegalArgumentException, which occurs from the following in the rpcrouter (if the source I have
> matches the soap.jar I am using): Reader requestReader = req.getReader (); This seems like a
> pretty harmless call, as its just getting the reader from the Servlet request object, something I
> do all the time with no problem. Unless you have any other ideas, the only think I can think of is
> to do a build from the source and try to add more debug statements. Thanks, Cory
>

                             'urn:SurgeTest' Service Deployment Descriptor

              Property                                          Details
  ID                               urn:SurgeTest
  Scope                            Application
  Provider Type                    java
  Provider Class                   sample.surgetest.SurgeTestProvider
  Use Static Class                 false
  Methods                          getTest
  Type Mappings
>
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 3:58 PM
>      Subject: Re: Configuration Problem
>       Ok, so the router apparently finds the provider and invokes
>      a method on it right? But the provider doesn't seem to be entered?
>      Otherwise I assume we would get
>      a much clearer error message. Have you brought up a browser
>      and pointed it to http://localhost:8080/soap/admin to get the admin
>      page and then do a list to see if your providers are in fact deployed.
>      Then maybe look at the deployment details and make sure it all looks right.
>
>      I'm wondering if this isn't one of those cases (in light of a recent release change)
>      that there isn't something stale out there, or two versions and the wrong one
>      getting used thing. For example, the soap layer has a serialized file that it
>      stores deployment info so that when it starts up again it redeploys what's
>      already been deployed. That should probably be wacked, and then redeploy.
>
>      Also, back when we were using jdp for the router, a stale servlet class
>      (generated from the jsp) could screw you as well. Not sure if Websphere
>      stashes servlet classes any where.
>
>      A few ideas.
>
>      Cory Isaacson wrote:
>
>     >  Rich, I wrote another simple set of classes, and you're correct -- they are not
>     > running. Any idea why? I checked the classpath on my server and it seems to be OK, but
>     > the provider class doesn't get fired. I'm running from soap.jar so its a little hard
>     > to debug anything in soap itself. Cory
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 3:20 PM
>     >      Subject: Re: Configuration Problem
>     >       Not sure. Maybe try another demo.Since this is a new
>     >      release (i'm still on the previous) just put up friday,
>     >      it hasn't been used by a lot of people, so maybe you're
>     >      up against a bug.
>     >
>     >      Also, can you use some println's in your provider to see
>     >      if you're reaching it? I assume the router found it and it's
>     >      deployed properly, otherwise you'd have a different error.
>     >
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      >  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The
>     >      > call looks good from the client, but the provider is returning:
>     >      > java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
>     >      >  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet
>     >      > runs for sure if I type the URL manually into my browser (I get the error
>     >      > about not processing 'GET' requests). If the provider is not running, how
>     >      > could I tell that? Thanks, Cory
>     >      >
>     >      >      ----- Original Message -----
>     >      >      From: Rich Johns
>     >      >      To: soap-user@xml.apache.org
>     >      >      Sent: Saturday, August 19, 2000 2:34 PM
>     >      >      Subject: Re: Configuration Problem
>     >      >       RPCRouterServlet is the right one. As far as the error, not
>     >      >      sure. I haven't pulled down
>     >      >      2.0 yet.  I have seen this error when the router doesn't run at
>     >      >      all. The element that the
>     >      >      provider was supposed to produce, is null and thus NOT
>     >      >      well-formed. If you're not getting to
>     >      >      the router, then the provider isn't running. Just a thought.
>     >      >
>     >      >      Cory Isaacson wrote:
>     >      >
>     >      >     >  When running the new SOAP 2.0 I get the following error when I
>     >      >     >  try to run the RPC servlet: org.xml.sax.SAXParseException: The
>     >      >     >  markup in the document preceding the root element must be
>     >      >     >  well-formed.
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
>     >      >     >  Code)
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >     >
>     >      >     >   at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >     >   at samples.stockquote.GetQuote.main(GetQuote.java:103) I
>     >      >     >  registered the RPCRouterServlet class as my servlet. Is this
>     >      >     >  the correct class? The only other one I see is the RPCRouter
>     >      >     >  class, but I'm not sure if that's a servlet. Thanks, Cory
>     >      >

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Seems screwy. That doesn't seem like code that would generate an Illega...tion.
By the way, do you mean RPCRouterServlet? That's where I found the req.getReader() line.

So, it sounds like it's not even gotten to the point where you are doing the
invoke on the provider. It's something wrong in the router itself, and if it
really cracked getting the Reader, may the request is corrupt or something.
Or, you've got some code out of synch or something. I'm set up to do my own
builds, and that way I can get at the code, so maybe your right to go ahead
and get at the soap code itself.

Anyway, sorry I don't have a better suggestion.

Cory Isaacson wrote:

>  Rich, I think you're right, and for sure the provider class is not being entered (I have a print
> statement right at the top of my method). I checked the deployment through the admin page, and it
> looks to be correct. See the data below. I couldn't have made a simpler example (just returns a
> string with no parameters and no serialization). I also hard-coded all of the URL parameters, etc.
> to be sure they were correct. The rpcrouter is definitely being called, and then gets stuck at the
> IllegalArgumentException, which occurs from the following in the rpcrouter (if the source I have
> matches the soap.jar I am using): Reader requestReader = req.getReader (); This seems like a
> pretty harmless call, as its just getting the reader from the Servlet request object, something I
> do all the time with no problem. Unless you have any other ideas, the only think I can think of is
> to do a build from the source and try to add more debug statements. Thanks, Cory
>

                             'urn:SurgeTest' Service Deployment Descriptor

              Property                                          Details
  ID                               urn:SurgeTest
  Scope                            Application
  Provider Type                    java
  Provider Class                   sample.surgetest.SurgeTestProvider
  Use Static Class                 false
  Methods                          getTest
  Type Mappings
>
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 3:58 PM
>      Subject: Re: Configuration Problem
>       Ok, so the router apparently finds the provider and invokes
>      a method on it right? But the provider doesn't seem to be entered?
>      Otherwise I assume we would get
>      a much clearer error message. Have you brought up a browser
>      and pointed it to http://localhost:8080/soap/admin to get the admin
>      page and then do a list to see if your providers are in fact deployed.
>      Then maybe look at the deployment details and make sure it all looks right.
>
>      I'm wondering if this isn't one of those cases (in light of a recent release change)
>      that there isn't something stale out there, or two versions and the wrong one
>      getting used thing. For example, the soap layer has a serialized file that it
>      stores deployment info so that when it starts up again it redeploys what's
>      already been deployed. That should probably be wacked, and then redeploy.
>
>      Also, back when we were using jdp for the router, a stale servlet class
>      (generated from the jsp) could screw you as well. Not sure if Websphere
>      stashes servlet classes any where.
>
>      A few ideas.
>
>      Cory Isaacson wrote:
>
>     >  Rich, I wrote another simple set of classes, and you're correct -- they are not
>     > running. Any idea why? I checked the classpath on my server and it seems to be OK, but
>     > the provider class doesn't get fired. I'm running from soap.jar so its a little hard
>     > to debug anything in soap itself. Cory
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 3:20 PM
>     >      Subject: Re: Configuration Problem
>     >       Not sure. Maybe try another demo.Since this is a new
>     >      release (i'm still on the previous) just put up friday,
>     >      it hasn't been used by a lot of people, so maybe you're
>     >      up against a bug.
>     >
>     >      Also, can you use some println's in your provider to see
>     >      if you're reaching it? I assume the router found it and it's
>     >      deployed properly, otherwise you'd have a different error.
>     >
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      >  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The
>     >      > call looks good from the client, but the provider is returning:
>     >      > java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
>     >      >  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet
>     >      > runs for sure if I type the URL manually into my browser (I get the error
>     >      > about not processing 'GET' requests). If the provider is not running, how
>     >      > could I tell that? Thanks, Cory
>     >      >
>     >      >      ----- Original Message -----
>     >      >      From: Rich Johns
>     >      >      To: soap-user@xml.apache.org
>     >      >      Sent: Saturday, August 19, 2000 2:34 PM
>     >      >      Subject: Re: Configuration Problem
>     >      >       RPCRouterServlet is the right one. As far as the error, not
>     >      >      sure. I haven't pulled down
>     >      >      2.0 yet.  I have seen this error when the router doesn't run at
>     >      >      all. The element that the
>     >      >      provider was supposed to produce, is null and thus NOT
>     >      >      well-formed. If you're not getting to
>     >      >      the router, then the provider isn't running. Just a thought.
>     >      >
>     >      >      Cory Isaacson wrote:
>     >      >
>     >      >     >  When running the new SOAP 2.0 I get the following error when I
>     >      >     >  try to run the RPC servlet: org.xml.sax.SAXParseException: The
>     >      >     >  markup in the document preceding the root element must be
>     >      >     >  well-formed.
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
>     >      >     >  Code)
>     >      >     >   at
>     >      >     >  org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >     >
>     >      >     >   at
>     >      >     >  org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >     >
>     >      >     >   at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >     >   at samples.stockquote.GetQuote.main(GetQuote.java:103) I
>     >      >     >  registered the RPCRouterServlet class as my servlet. Is this
>     >      >     >  the correct class? The only other one I see is the RPCRouter
>     >      >     >  class, but I'm not sure if that's a servlet. Thanks, Cory
>     >      >

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I think you're right, and for sure the provider class is not being entered (I have a print statement right at the top of my method). I checked the deployment through the admin page, and it looks to be correct. See the data below. I couldn't have made a simpler example (just returns a string with no parameters and no serialization). I also hard-coded all of the URL parameters, etc. to be sure they were correct. The rpcrouter is definitely being called, and then gets stuck at the IllegalArgumentException, which occurs from the following in the rpcrouter (if the source I have matches the soap.jar I am using):

Reader requestReader = req.getReader ();

This seems like a pretty harmless call, as its just getting the reader from the Servlet request object, something I do all the time with no problem. Unless you have any other ideas, the only think I can think of is to do a build from the source and try to add more debug statements.

Thanks,

Cory

----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:58 PM
Subject: Re: Configuration Problem

Ok, so the router apparently finds the provider and invokes
a method on it right? But the provider doesn't seem to be entered?
Otherwise I assume we would get
a much clearer error message. Have you brought up a browser
and pointed it to http://localhost:8080/soap/admin to get the admin
page and then do a list to see if your providers are in fact deployed.
Then maybe look at the deployment details and make sure it all looks right.
I'm wondering if this isn't one of those cases (in light of a recent release change)
that there isn't something stale out there, or two versions and the wrong one
getting used thing. For example, the soap layer has a serialized file that it
stores deployment info so that when it starts up again it redeploys what's
already been deployed. That should probably be wacked, and then redeploy.

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

Reader requestReader = req.getReader ();

Thanks,

Cory

----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:58 PM
Subject: Re: Configuration Problem

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Ok, so the router apparently finds the provider and invokes
a method on it right? But the provider doesn't seem to be entered?
Otherwise I assume we would get
a much clearer error message. Have you brought up a browser
and pointed it to http://localhost:8080/soap/admin to get the admin
page and then do a list to see if your providers are in fact deployed.
Then maybe look at the deployment details and make sure it all looks right.

I'm wondering if this isn't one of those cases (in light of a recent release change)
that there isn't something stale out there, or two versions and the wrong one
getting used thing. For example, the soap layer has a serialized file that it
stores deployment info so that when it starts up again it redeploys what's
already been deployed. That should probably be wacked, and then redeploy.

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

>  Rich, I wrote another simple set of classes, and you're correct -- they are not running. Any idea
> why? I checked the classpath on my server and it seems to be OK, but the provider class doesn't
> get fired. I'm running from soap.jar so its a little hard to debug anything in soap itself. Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 3:20 PM
>      Subject: Re: Configuration Problem
>       Not sure. Maybe try another demo.Since this is a new
>      release (i'm still on the previous) just put up friday,
>      it hasn't been used by a lot of people, so maybe you're
>      up against a bug.
>
>      Also, can you use some println's in your provider to see
>      if you're reaching it? I assume the router found it and it's
>      deployed properly, otherwise you'd have a different error.
>
>
>      Cory Isaacson wrote:
>
>     >  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The call looks
>     > good from the client, but the provider is returning:
>     > java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
>     >  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet runs for
>     > sure if I type the URL manually into my browser (I get the error about not processing
>     > 'GET' requests). If the provider is not running, how could I tell that? Thanks, Cory
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 2:34 PM
>     >      Subject: Re: Configuration Problem
>     >       RPCRouterServlet is the right one. As far as the error, not sure. I haven't
>     >      pulled down
>     >      2.0 yet.  I have seen this error when the router doesn't run at all. The
>     >      element that the
>     >      provider was supposed to produce, is null and thus NOT well-formed. If
>     >      you're not getting to
>     >      the router, then the provider isn't running. Just a thought.
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      > When running the new SOAP 2.0 I get the following error when I try to run
>     >      > the RPC servlet: org.xml.sax.SAXParseException: The markup in the document
>     >      > preceding the root element must be well-formed.
>     >      >  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >  at
>     >      > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >
>     >      >  at
>     >      > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >
>     >      >  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>     >      >
>     >      >  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >  at
>     >      > org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >
>     >      >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the
>     >      > RPCRouterServlet class as my servlet. Is this the correct class? The only
>     >      > other one I see is the RPCRouter class, but I'm not sure if that's a
>     >      > servlet. Thanks, Cory
>     >

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Ok, so the router apparently finds the provider and invokes
a method on it right? But the provider doesn't seem to be entered?
Otherwise I assume we would get
a much clearer error message. Have you brought up a browser
and pointed it to http://localhost:8080/soap/admin to get the admin
page and then do a list to see if your providers are in fact deployed.
Then maybe look at the deployment details and make sure it all looks right.

I'm wondering if this isn't one of those cases (in light of a recent release change)
that there isn't something stale out there, or two versions and the wrong one
getting used thing. For example, the soap layer has a serialized file that it
stores deployment info so that when it starts up again it redeploys what's
already been deployed. That should probably be wacked, and then redeploy.

Also, back when we were using jdp for the router, a stale servlet class
(generated from the jsp) could screw you as well. Not sure if Websphere
stashes servlet classes any where.

A few ideas.

Cory Isaacson wrote:

>  Rich, I wrote another simple set of classes, and you're correct -- they are not running. Any idea
> why? I checked the classpath on my server and it seems to be OK, but the provider class doesn't
> get fired. I'm running from soap.jar so its a little hard to debug anything in soap itself. Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 3:20 PM
>      Subject: Re: Configuration Problem
>       Not sure. Maybe try another demo.Since this is a new
>      release (i'm still on the previous) just put up friday,
>      it hasn't been used by a lot of people, so maybe you're
>      up against a bug.
>
>      Also, can you use some println's in your provider to see
>      if you're reaching it? I assume the router found it and it's
>      deployed properly, otherwise you'd have a different error.
>
>
>      Cory Isaacson wrote:
>
>     >  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The call looks
>     > good from the client, but the provider is returning:
>     > java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
>     >  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet runs for
>     > sure if I type the URL manually into my browser (I get the error about not processing
>     > 'GET' requests). If the provider is not running, how could I tell that? Thanks, Cory
>     >
>     >      ----- Original Message -----
>     >      From: Rich Johns
>     >      To: soap-user@xml.apache.org
>     >      Sent: Saturday, August 19, 2000 2:34 PM
>     >      Subject: Re: Configuration Problem
>     >       RPCRouterServlet is the right one. As far as the error, not sure. I haven't
>     >      pulled down
>     >      2.0 yet.  I have seen this error when the router doesn't run at all. The
>     >      element that the
>     >      provider was supposed to produce, is null and thus NOT well-formed. If
>     >      you're not getting to
>     >      the router, then the provider isn't running. Just a thought.
>     >
>     >      Cory Isaacson wrote:
>     >
>     >      > When running the new SOAP 2.0 I get the following error when I try to run
>     >      > the RPC servlet: org.xml.sax.SAXParseException: The markup in the document
>     >      > preceding the root element must be well-formed.
>     >      >  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >      >  at
>     >      > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >      >
>     >      >  at
>     >      > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >      >
>     >      >  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>     >      >
>     >      >  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >      >  at
>     >      > org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >      >
>     >      >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >      >  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the
>     >      > RPCRouterServlet class as my servlet. Is this the correct class? The only
>     >      > other one I see is the RPCRouter class, but I'm not sure if that's a
>     >      > servlet. Thanks, Cory
>     >

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I wrote another simple set of classes, and you're correct -- they are not running. Any idea why? I checked the classpath on my server and it seems to be OK, but the provider class doesn't get fired. I'm running from soap.jar so its a little hard to debug anything in soap itself.

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:20 PM
Subject: Re: Configuration Problem

Not sure. Maybe try another demo.Since this is a new
release (i'm still on the previous) just put up friday,
it hasn't been used by a lot of people, so maybe you're
up against a bug.
Also, can you use some println's in your provider to see
if you're reaching it? I assume the router found it and it's
deployed properly, otherwise you'd have a different error.

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 3:20 PM
Subject: Re: Configuration Problem

Cory Isaacson wrote:

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Not sure. Maybe try another demo.Since this is a new
release (i'm still on the previous) just put up friday,
it hasn't been used by a lot of people, so maybe you're
up against a bug.

Also, can you use some println's in your provider to see
if you're reaching it? I assume the router found it and it's
deployed properly, otherwise you'd have a different error.


Cory Isaacson wrote:

>  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The call looks good from
> the client, but the provider is returning: java.lang.IllegalArgumentException:
> sun.io.ByteToCharUTF-8
>  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet runs for sure if I
> type the URL manually into my browser (I get the error about not processing 'GET' requests). If
> the provider is not running, how could I tell that? Thanks, Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 2:34 PM
>      Subject: Re: Configuration Problem
>       RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
>
>      2.0 yet.  I have seen this error when the router doesn't run at all. The element that
>      the
>      provider was supposed to produce, is null and thus NOT well-formed. If you're not
>      getting to
>      the router, then the provider isn't running. Just a thought.
>
>      Cory Isaacson wrote:
>
>     > When running the new SOAP 2.0 I get the following error when I try to run the RPC
>     > servlet: org.xml.sax.SAXParseException: The markup in the document preceding the root
>     > element must be well-formed.
>     >  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >  at
>     > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >
>     >  at
>     > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >
>     >  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>     >  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >  at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the
>     > RPCRouterServlet class as my servlet. Is this the correct class? The only other one I
>     > see is the RPCRouter class, but I'm not sure if that's a servlet. Thanks, Cory
>

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

Not sure. Maybe try another demo.Since this is a new
release (i'm still on the previous) just put up friday,
it hasn't been used by a lot of people, so maybe you're
up against a bug.

Also, can you use some println's in your provider to see
if you're reaching it? I assume the router found it and it's
deployed properly, otherwise you'd have a different error.


Cory Isaacson wrote:

>  Rich, I got the TcpTunnelGui working fine now. I now see how it works. The call looks good from
> the client, but the provider is returning: java.lang.IllegalArgumentException:
> sun.io.ByteToCharUTF-8
>  at sun.io.ByteToCharConverter.getConverterClass(Compiled Code) The servlet runs for sure if I
> type the URL manually into my browser (I get the error about not processing 'GET' requests). If
> the provider is not running, how could I tell that? Thanks, Cory
>
>      ----- Original Message -----
>      From: Rich Johns
>      To: soap-user@xml.apache.org
>      Sent: Saturday, August 19, 2000 2:34 PM
>      Subject: Re: Configuration Problem
>       RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
>
>      2.0 yet.  I have seen this error when the router doesn't run at all. The element that
>      the
>      provider was supposed to produce, is null and thus NOT well-formed. If you're not
>      getting to
>      the router, then the provider isn't running. Just a thought.
>
>      Cory Isaacson wrote:
>
>     > When running the new SOAP 2.0 I get the following error when I try to run the RPC
>     > servlet: org.xml.sax.SAXParseException: The markup in the document preceding the root
>     > element must be well-formed.
>     >  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>     >  at
>     > org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>     >
>     >  at
>     > org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>     >
>     >  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>     >  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>     >  at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>     >  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>     >  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the
>     > RPCRouterServlet class as my servlet. Is this the correct class? The only other one I
>     > see is the RPCRouter class, but I'm not sure if that's a servlet. Thanks, Cory
>

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I got the TcpTunnelGui working fine now. I now see how it works.

The call looks good from the client, but the provider is returning:

java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)

The servlet runs for sure if I type the URL manually into my browser (I get the error about not processing 'GET' requests). If the provider is not running, how could I tell that?

Thanks,

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 2:34 PM
Subject: Re: Configuration Problem

RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
2.0 yet. I have seen this error when the router doesn't run at all. The element that the
provider was supposed to produce, is null and thus NOT well-formed. If you're not getting to
the router, then the provider isn't running. Just a thought.
Cory Isaacson wrote:

Re: Configuration Problem

Posted by Cory Isaacson <ci...@capita2.com>.

Rich,

I got the TcpTunnelGui working fine now. I now see how it works.

The call looks good from the client, but the provider is returning:

java.lang.IllegalArgumentException: sun.io.ByteToCharUTF-8
at sun.io.ByteToCharConverter.getConverterClass(Compiled Code)

The servlet runs for sure if I type the URL manually into my browser (I get the error about not processing 'GET' requests). If the provider is not running, how could I tell that?

Thanks,

Cory
----- Original Message -----
From: Rich Johns
To: soap-user@xml.apache.org
Sent: Saturday, August 19, 2000 2:34 PM
Subject: Re: Configuration Problem

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
2.0 yet.  I have seen this error when the router doesn't run at all. The element that the
provider was supposed to produce, is null and thus NOT well-formed. If you're not getting to
the router, then the provider isn't running. Just a thought.

Cory Isaacson wrote:

> When running the new SOAP 2.0 I get the following error when I try to run the RPC
> servlet: org.xml.sax.SAXParseException: The markup in the document preceding the root element must
> be well-formed.
>  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>  at
> org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>  at
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>
>  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>  at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the RPCRouterServlet class as
> my servlet. Is this the correct class? The only other one I see is the RPCRouter class, but I'm
> not sure if that's a servlet. Thanks, Cory

Re: Configuration Problem

Posted by Rich Johns <rj...@vignette.com>.

RPCRouterServlet is the right one. As far as the error, not sure. I haven't pulled down
2.0 yet.  I have seen this error when the router doesn't run at all. The element that the
provider was supposed to produce, is null and thus NOT well-formed. If you're not getting to
the router, then the provider isn't running. Just a thought.

Cory Isaacson wrote:

> When running the new SOAP 2.0 I get the following error when I try to run the RPC
> servlet: org.xml.sax.SAXParseException: The markup in the document preceding the root element must
> be well-formed.
>  at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:969)
>  at
> org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:625)
>  at
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:804)
>
>  at org.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled Code)
>  at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:861)
>  at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:85)
>  at org.apache.soap.rpc.Call.invoke(Call.java:157)
>  at samples.stockquote.GetQuote.main(GetQuote.java:103) I registered the RPCRouterServlet class as
> my servlet. Is this the correct class? The only other one I see is the RPCRouter class, but I'm
> not sure if that's a servlet. Thanks, Cory