Thanks Anthony, that agent looks great. It's a great start for what
i'm going to do :)
But now i'm trying to use the fedone code in my project and i'm having
some troubles. For that purpose, i downloaded the source from the hg
repository and I built it using ant. The build went fine and I picked
the fedone-api-0.2.jar from the dist folder and added it to my project
(i'm using IDE Eclipse3.5).
The problem is that when i write the following line of code:
backend.createConversationWave(null);
the compiler says "The type
org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc
$ProtocolSubmitResponse cannot be resolved. It is indirectly
referenced from required .class files" (backend is a ClientBackend).
When I check the code from ClientBackend.java it says it can't resolve
the import
org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc.ProtocolSubmitResponse
and others from the same package/class (WaveClientRpc). That's because
it doesn't exist, what exists with this name is a buffer protocol file
(waveclient-rpc.proto).
Am i supposed to compile all the .proto files in fedone to java code?
I have tried this before and resolved the compilation errors, but then
when i tried to build it I was faced with quite a few errors around
the java files created, like:
[javac] C:\Users\Bernardo\WorkspaceWave\wave-protocol\src\org
\waveprotocol\wave\examples\fedone\waveserver\WaveClientRpc.java:203:
types
com.google.protobuf.GeneratedMessage.Builder<org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc.ProtocolOpenRequest.Builder>
and
com.google.protobuf.GeneratedMessage.Builder<org.waveprotocol.wave.examples.fedone.waveserver.WaveClientRpc.ProtocolOpenRequest.Builder>
are incompatible; both define mergeFrom
(com.google.protobuf.CodedInputStream), but with unrelated return
types
[javac] public static final class Builder extends
On 7 Jan, 12:28, Anthony Baxter <[email protected]> wrote:
> There is an agent framework already. It's pretty limited, it only
> supports reacting to events.
>
> You might like to look athttp://codereview.waveprotocol.org/32002/showwhich
> is an example of
> an agent that takes HTTP requests and triggers wave actions based on
> them.
>
> On Thu, Jan 7, 2010 at 21:07, Bernardo Ferreira
>
>
>
>
>
> <[email protected]> wrote:
> > On 6 Jan, 21:55, James Purser <[email protected]> wrote:
> >> Is your collaborative framework behind a firewall or is it directly
> >> internet facing? If it's internet facing then does it have an api that
> >> can be tapped into by the Robot itself?
>
> > Well, it does have an api but if I was to use it on the Robot, that
> > would make it (and Wave) a client of the framework, while the idea is
> > to have Wave as a new resource of the framework, and the robot making
> > the bridge between Wave (as resource) and the events coming from the
> > framework. Furthermore, I have full access to the framework's code
> > (though it wasn't developed by me) and can change/extend it at will.
>
> > --
> > 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
> > athttp://groups.google.com/group/wave-protocol?hl=en.
>
> --
> Anthony Baxter, [email protected]
--
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.
