Ah! thanks a lot. i kind of got that working. Now, I created a new
java class to extend and run the client console, and when i run it, it
seems to connect, but gives a lot of errors on the server:
Mar 30, 2010 6:56:48 PM
org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider$Connection
<init>
INFO: New Connection set up from
java.nio.channels.SocketChannel[connected local=/153.42.31.172:9876
remote=/153.42.160.242:49809]
Mar 30, 2010 6:56:48 PM
org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider$Connection
message
INFO: Cancelling open RPC 1
Mar 30, 2010 6:56:48 PM
org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpcImpl
open
WARNING: Unable to deserialise the long wave id: !indexwave. The wave
id need to look like <domain>!<id>
Mar 30, 2010 6:56:48 PM
org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider$Connection
$1 run
INFO: error = Unable to deserialise the long wave id: !indexwave. The
wave id need to look like <domain>!<id>
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:206)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:
236)
at
org.waveprotocol.wave.examples.fedone.rpc.SequencedProtoChannel
$1.run(SequencedProtoChannel.java:99)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Source code:
public class test extends ConsoleClient{
public test() throws IOException{
super();
String[] args={ userAtHost, host, port};
super.run(args);
}
I'm running this from Windows, in case that matters.
On Mar 29, 8:31 pm, "Aldon Hynes" <[email protected]>
wrote:
> To use the existing console client, all you need to do is copy the jar file
> to some other machine running java.
>
> In my case, I copied wave-protocol/dist/fedone-client-console-0.2.jar to my
> Nokia N900
>
> then, I ran
> java -jar fedone-client-console-0.2.jar [email protected]
> orient-lodge.com 9876
>
> This brought up the console client very nicely on my N900, which only has
> the client console jar.
>
> Aldon
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]]on Behalf Of Devon
> > Sent: Monday, March 29, 2010 7:13 PM
> > To: Wave Protocol
> > Subject: Re: Accessing Wave Server from a Remote Java Environment
>
> > I was able to connect from my server to yours, which is a good sign.
> > However, what i'd like to do is be able to connect from a computer
> > that doesn't have a server running on it. I was unable to get the
> > client-console running properly from my other machine which isn't
> > running a server. Do you have any tips for doing this?
>
> > On Mar 29, 5:40 pm, "Aldon Hynes" <[email protected]>
> > wrote:
> > > If I recall properly, you can use the existing consoleclient
> > from any server
> > > to connect to other servers. I have my server, running a fairly old
> > > codeset, open to the outside world. So, anyone with the
> > consoleclient code
> > > on their machine can start the code and then
>
> > > /connect [email protected] orient-lodge.com 9876
>
> > > to connect into my server. IIRC, I've run the consoleclient from other
> > > machines this way successfully, without any modifications. In addition,
> > > I've connected using the QWaveClient from several different
> > machines this
> > > way.
>
> > > Devon, if you want to test your java code against my server, go
> > ahead. It
> > > may help you isolate whether the problem is on your client side or your
> > > server side.
>
> > > Aldon
>
> > > > -----Original Message-----
> > > > From: [email protected]
> > > > [mailto:[email protected]]on Behalf Of Devon
> > > > Sent: Monday, March 29, 2010 1:51 PM
> > > > To: Wave Protocol
> > > > Subject: Accessing Wave Server from a Remote Java Environment
>
> > > > Hello,
>
> > > > I'm trying to create a Java program that can act like the console
> > > > client to access my wave server from a remote computer. My current
> > > > code, mostly taken from the ConsoleClient.java source, doesn't seem to
> > > > be connecting, and I'm not sure why.
>
> > > > Is it possible to use this same code to connect to a remove server, or
> > > > is there any way to do it at all?
>
> > > > It currently gets hung up when creating a new wave, it times out.
> > > > connect() doesn't throw any exceptions, but I can't tell if it's
> > > > actually connected or not.
>
> > > > Any help would be greatly appreciated.
>
> > > > --
> > > > You received this message because you are subscribed to the
> > > > Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
>
> > --
> > You received this message because you are subscribed to the
> > Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" 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/wave-protocol?hl=en.
