Mike, that was a good catch, but that difference was just a "typo" on
my part.  When I copied and pasted the messages into my post I just
missed including the "l" in Impl on one of the messages.  Actually
both are the same.

Now, I have scanned other posts on this same issue.  Most suggest it
is a classpath issue.  Okay, when I include "www" in the GWTShell
command, it I get the same results ... no improvement.

I think the question I have is, "How to deploy the server-side
compiled code into the embedded Tomcat?"  I do not see evidence that
Tomcat even knows about the service Impl.  As I understand it, I
should only have to run CSRapp-compile and CSRapp-shell for everything
to work.  Correct?  I have re-visited both the tutorial and the
developer's guide and I can find nothing that provides good guidance
on this issue.

On Feb 19, 4:59 am, "[email protected]" <[email protected]>
wrote:
> The first thing I noticed is that at one place in your message it's
> referred to as
> SelectionSearchServiceImp and in another it's
> SelectionSearchServiceImpl.
> That would indicate that your class is named one and is referenced in
> your
> Gwt.xml as the other.  Again, that's the first thing I noticed.....
>
> Good luck!
>
> Later,
> Shaffer
>
> On Feb 18, 8:15 pm, BobM <[email protected]> wrote:
>
> > More detail from this message which was presented in the GWT shell
> > when I made a GWT RPC call attempt:
> > java.lang.ClassNotFoundException:
> > org.bcs.server.SelectionSearchServiceImp
>
> > The message from caught.getMessage():
> > Unable to find/load mapped servlet class
> > 'org.bcs.server.SelectionSearchServiceImpl
>
> > The rpc.log (which to my surprise gets created upon gwt compile)
> > reports this:
> > Reachable types computed on: Wed Feb 18 20:29:40 CST 2009
> > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException
> >    Serialization status
> >       Instantiable
> >    Path
> >       Started from
> > 'com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException'
>
> > java.lang.Exception
> >    Serialization status
> >       Field serializable
> >    Path
> >       Started from
> > 'com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException'
>
> > java.lang.Object
> >    Serialization status
> >       Not serializable
> >    Path
> >       Started from 'java.lang.String'
>
> > java.lang.RuntimeException
> >    Serialization status
> >       Field serializable
> >    Path
> >       Started from
> > 'com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException'
>
> > java.lang.String
> >    Serialization status
> >       Instantiable
> >    Path
> >       Started from 'java.lang.String'
>
> > java.lang.String[]
> >    Serialization status
> >       Instantiable
> >    Path
> >       Type 'java.lang.String[]' is reachable from array type
> > 'java.lang.String[][]'
> >       Started from 'java.lang.String[][]'
>
> > java.lang.String[][]
> >    Serialization status
> >       Instantiable
> >    Path
> >       Started from 'java.lang.String[][]'
>
> > java.lang.Throwable
> >    Serialization status
> >       Field serializable
> >    Path
> >       Started from
> > 'com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException'
> > ===============
>
> > Is there something I have failed to do with regard to setup to run in
> > hosted mode?  What is the problem here?  Although I doubt I am yet
> > really able to decipher the log, I don't see anything in the log that
> > is an obvious problem although it reports this
> > "ImcompatibleRemoteServiceException", if that is the/a problem.
>
> > Anything else I need to look at or report to y'all to fully diagnose
> > this issue?
>
> > Thanks for help.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to